In case you missed 🚨
🔐 near-multisig-sdk 🔓
This repository was shared in the NEAR Tools chat💬
It implements multisig on NEAR using a contract-controlled account. A contract collects approvals from multiple participants and executes a transaction once the threshold is met.
A simple example of how multisig can be built by the community directly on top of NEAR accounts, without off-chain coordination✅
🧗 Repository
Feedback from anyone who has worked with multisig is welcome✍️
🟦 Channel | Chat | LinkTree
🔐 near-multisig-sdk 🔓
This repository was shared in the NEAR Tools chat
It implements multisig on NEAR using a contract-controlled account. A contract collects approvals from multiple participants and executes a transaction once the threshold is met.
A simple example of how multisig can be built by the community directly on top of NEAR accounts, without off-chain coordination
Feedback from anyone who has worked with multisig is welcome
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥4❤2👀1
What does “NEAR is the BOS” actually mean today?
Join the Innovation Sandbox workshop to explore how the NEAR tech stack has evolved and why it’s suited for building decentralized apps. Live walkthrough, build, and deployment included
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥3❤1👀1
Confidential email implemented on NEAR
near.email is an email service built around NEAR. Visually, it looks like a regular email client and uses standard SMTP. The difference is privacy.
What changes:
➡️ access and message decryption are tied to the NEAR account
➡️ there are no provider-held credentials
➡️ messages are processed inside a TEE
➡️ emails are stored encrypted, so the service can’t read them
Email is not stored or processed on-chain. The NEAR account is used for identity and access control, while email remains fully off-chain and compatible with existing infrastructure.
This is a working implementation you can test today (early access).
We’re sharing 5 invite codes to get started: 1 / 2 / 3 / 4 / 5
Each activated account receives 3 more codes.
As a result, NEAR Email can be seen alongside NEAR AI, NEAR Web4, and NEAR DNS as a practical example of applications built around NEAR accounts. Docs🖥
🟦 Channel | Chat | LinkTree
near.email is an email service built around NEAR. Visually, it looks like a regular email client and uses standard SMTP. The difference is privacy.
What changes:
Email is not stored or processed on-chain. The NEAR account is used for identity and access control, while email remains fully off-chain and compatible with existing infrastructure.
This is a working implementation you can test today (early access).
We’re sharing 5 invite codes to get started: 1 / 2 / 3 / 4 / 5
Each activated account receives 3 more codes.
As a result, NEAR Email can be seen alongside NEAR AI, NEAR Web4, and NEAR DNS as a practical example of applications built around NEAR accounts. Docs
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥12❤2
How does NOVA approach privacy-first, decentralized file sharing?
Join Innovation Sandbox [Workshop 2]: Building with NOVA for a deep dive into the NOVA tech stack and how it’s designed for encrypted data persistence in dApps
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥4
OpenClaw is now available on NEAR AI Cloud 🦞 🛡
OpenClaw is a personal agent that actually works. It connects to email and services, keeps context, and runs 24/7. It feels more like a quiet coworker than a chatbot.
Until now, running it meant an awkward trade-off.
1️⃣ Either keep everything on local hardware.
2️⃣ Or run it on a standard cloud VM and accept that memory, keys, and context live in an untrusted environment.
There’s now a third option.
3️⃣ OpenClaw can run on NEAR AI Cloud inside a TEE.
What this changes:
✦ memory and data are encrypted at the hardware level
✦ only verified code is allowed to run
✦ the infrastructure has no visibility into the agent, even from NEAR AI
The agent can keep long-term memory and work with real tools while staying inside an encrypted execution environment🛡
If you’ve wanted to run OpenClaw without managing your own hardware or trusting a regular cloud VM, NEAR AI Cloud makes that possible.
Apply for early access✍️
🟦 Channel | Chat | LinkTree
OpenClaw is a personal agent that actually works. It connects to email and services, keeps context, and runs 24/7. It feels more like a quiet coworker than a chatbot.
Until now, running it meant an awkward trade-off.
There’s now a third option.
What this changes:
✦ memory and data are encrypted at the hardware level
✦ only verified code is allowed to run
✦ the infrastructure has no visibility into the agent, even from NEAR AI
The agent can keep long-term memory and work with real tools while staying inside an encrypted execution environment
If you’ve wanted to run OpenClaw without managing your own hardware or trusting a regular cloud VM, NEAR AI Cloud makes that possible.
Apply for early access
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥8👍4
From enterprise AI to developer tooling and ecosystem momentum, here’s what shaped NEAR in January.
Here’s the rundown:
… and more inside the full issue.
Please open Telegram to view this post
VIEW IN TELEGRAM
❤8
How do you stream NEAR data in real time without traditional indexing?
Join Innovation Sandbox [Workshop 3]: Streaming NEAR Data with Goldsky to go under the hood of Goldsky Mirror and see how NEAR data can be streamed directly into your database.
Please open Telegram to view this post
VIEW IN TELEGRAM
NEAR skills + AI agents = agents that actually do things 👨💻
An agent does not know everything by default. Like a human, it is shaped by its skills.
The difference is that agent skills are modular and reusable capabilities that work across different agent platforms and workflows, such as OpenClaw, Claude Code, and Codex.
NEAR has its own set of these skills.
These are the skills your AI agent will brag about on the forum:
➡️ near-ai
➡️ near-api-js
➡️ near-connect
➡️ near-connect-hooks
➡️ near-kit
➡️ near-intents
➡️ near-smart-contracts
They are available here🧗
With these skills, your agent will be valued not only on Moltbook, but also on Agent Market. On that note...
... this is a good moment not just to launch your onchain AI agent, but to start exploring its first paid tasks.
Be among the first to try it🖥
🟦 Channel | Chat | LinkTree
An agent does not know everything by default. Like a human, it is shaped by its skills.
The difference is that agent skills are modular and reusable capabilities that work across different agent platforms and workflows, such as OpenClaw, Claude Code, and Codex.
NEAR has its own set of these skills.
These are the skills your AI agent will brag about on the forum:
They are available here
With these skills, your agent will be valued not only on Moltbook, but also on Agent Market. On that note...
... this is a good moment not just to launch your onchain AI agent, but to start exploring its first paid tasks.
Be among the first to try it
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥8
How does PingPay approach payment orchestration across assets?
Join Innovation Sandbox [Workshop 4]: Exploring PingPay for a walkthrough of the PingPay tech stack and how it’s used for payment scenarios powered by NEAR Intents
Please open Telegram to view this post
VIEW IN TELEGRAM
👍5❤1😍1
The Unified Commerce Layer by Illia Polosukhin
In his latest Substack piece, Illia writes that “commerce” is the world’s value-movement layer, and AI is about to automate it end-to-end.
He connects that shift to NEAR Intents as neutral infrastructure that routes intents to execution, and points to Agent Market as an early example: agents hiring agents, with work settled through escrow.
🔖 Read the full piece & subscribe
🟦 Channel | Chat | LinkTree
In his latest Substack piece, Illia writes that “commerce” is the world’s value-movement layer, and AI is about to automate it end-to-end.
He connects that shift to NEAR Intents as neutral infrastructure that routes intents to execution, and points to Agent Market as an early example: agents hiring agents, with work settled through escrow.
Please open Telegram to view this post
VIEW IN TELEGRAM
❤6👍2
Vadim Zavodil announced an on-demand oracle on NEAR
✨ TEE-Secured Price Oracle ✨
It fetches fresh data inside Intel TDX and returns it to your contract via callback, without the usual “keep updating the feed” loop.
Here’s what it actually gives you in practice:
➡️ Prices are always “warm” in TEE
➡️ Zero trust execution inside Intel TDX
➡️ 9+ price sources with median aggregation
➡️ Pyth-compatible API for easy migration
➡️ Custom data fetching from any HTTP API
➡️ Subsidized calls when the contract is funded
Powered by OutLayer✅
🧗 For details, see the full thread
🧗 Try it here
🟦 Channel | Chat | LinkTree
It fetches fresh data inside Intel TDX and returns it to your contract via callback, without the usual “keep updating the feed” loop.
Here’s what it actually gives you in practice:
Powered by OutLayer
Please open Telegram to view this post
VIEW IN TELEGRAM
👍6
The PL_Genesis: Frontiers of Collaboration hackathon is live
If you started something in NEARCON Innovation Sandbox, this is a good place to continue. If not, you can start fresh and ship before the deadline.
🏆 Compete for the NEAR prize and a share of the $100K+ prize pool. Select teams may be invited to join the Founders Forge Accelerator.
Details and registration here👈
🟦 Channel | Chat | LinkTree
If you started something in NEARCON Innovation Sandbox, this is a good place to continue. If not, you can start fresh and ship before the deadline.
Details and registration here
Please open Telegram to view this post
VIEW IN TELEGRAM
👍6❤3
How do you start building on NEAR without local setup or CLI headaches?
Join Innovation Sandbox [Workshop 5]: Zero-Setup NEAR Development with NEAR Playground for a hands-on walkthrough of building a dApp directly in the browser using NEAR’s online IDE
Please open Telegram to view this post
VIEW IN TELEGRAM
👍5❤3
Are you safe, son? 🦞
If your agent runs without constraints, no. With IronClaw, you don’t have to worry about your agent going off-script and leaking sensitive data.
The agent executes tools in isolation, with access controlled by permissions. Outbound HTTP can be restricted to an allowlist of endpoints.
If you’re building an always-on agent with integrations and keys, IronClaw is a good example of building security into the system from day one instead of bolting it on at the end, even though it’s still a work in progress✅
🧗 Repository
🟦 Channel | Chat | LinkTree
If your agent runs without constraints, no. With IronClaw, you don’t have to worry about your agent going off-script and leaking sensitive data.
The agent executes tools in isolation, with access controlled by permissions. Outbound HTTP can be restricted to an allowlist of endpoints.
If you’re building an always-on agent with integrations and keys, IronClaw is a good example of building security into the system from day one instead of bolting it on at the end, even though it’s still a work in progress
Please open Telegram to view this post
VIEW IN TELEGRAM
👍8❤3
How can users from any chain interact with NEAR dApps seamlessly?
Join Innovation Sandbox [Workshop 6]: Universal Accounts Smart Contract Wallet for NEAR Intents and beyond.
Templar Protocol will walk through how Universal Accounts use meta transactions, global contracts, and NEAR Intents to unlock effortless multichain experiences
Please open Telegram to view this post
VIEW IN TELEGRAM
❤3
What comes after NEARCON Innovation Sandbox?
Join the Opening Ceremony for PL_Genesis Frontiers of Collaboration to see how Sandbox projects can be continued and how teams can compete for the Best New or Continued Project prize.
Please open Telegram to view this post
VIEW IN TELEGRAM
👀3🔥2❤1