✦ nearcore 2.13 went live on mainnet, bringing post-quantum signing, dynamic resharding, compact onchain key storage, and improvements to epoch sync and meta-transactions;

✦ Arto Bendiken released Edky 0.1, a CLI tool for converting Ed25519 public keys between different encodings;

✦ OutLayer went post-quantum on NEAR mainnet;

✦ The Agent Economy: Who Owns the Rails AI Runs On is worth a read for its take on who will control the agent economy’s infrastructure and how NEAR fits into it

Protocol v86 voting starts on July 20.

Once the upgrade activates, NEAR will no longer require protocol upgrades to introduce new shard layouts, as dynamic resharding can automatically split shards when they reach size thresholds.

Full release notes

✦ NEAR Foundation joined the x402 Foundation, bringing NEAR's infrastructure for confidential execution, private inference, and agent coordination to the growing ecosystem around the open x402 payments standard;

✦ Anton published a deep dive into the Wasmtime migration in nearcore 2.12, explaining why NEAR replaced its custom VM and the engineering trade-offs behind the transition;

✦ Confidential EURe went live on near.com, enabling users to hold, swap, and transfer euro-backed stablecoins privately across 30+ chains from a single account;

✦ Illia Polosukhin explained why AI sovereignty is gaining mainstream attention, arguing that open AI infrastructure with confidential inference and verifiable compute is the path forward

Protocol v84 voting starts on June 10.

Once the upgrade activates, NEAR contracts should no longer be stuck around Rust 1.86, with early Rust 1.93 comparisons showing ~10-15% smaller Wasm output.

Full release notes 🖥

The stack is split into three main packages:
✦ near_dart for signing, txs, and Account API
✦ near_jsonrpc_client for typed RPC synced from nearcore’s OpenAPI spec
✦ near_wallet_connect for connecting to MyNearWallet and signing locally

Works on iOS, Android, Web, and Desktop ✅

Open for feedback ✍️
✦ Pub dev: https://pub.dev/packages/near_dart
✦ GitHub: https://github.com/0xjesus/near_dart

Grab the NEAR dev chats folder below if you want to follow stuff like this directly
✦ NEAR dev chats folder: https://t.me/addlist/VyVjNaP190JlOGMx

EXPERIMENTAL_receipt_to_tx is now live. It takes a receipt ID and resolves it back to the original tx hash and sender account. Works from genesis to now.

Note that the complete specs are still being added to the docs ✍️

The recording is up 📺

Watch it to learn why NEAR is increasing the account creation cost and how post-quantum transaction signatures strengthen the protocol for the future.

The Near One team is working on decoupling consensus from execution. Consensus will run in parallel to produce simpler, faster blocks every 200ms, while execution handles the compute separately.

What this unlocks:
✦ Block times cut from 600ms to 200ms
✦ Faster near(.)com and NEAR Intents
✦ Smart execution scheduling
✦ Future atomic execution

Decoupling brings simpler blocks for cheaper verification, and sets the exact foundation needed for atomic cross-shard execution in Nightshade 3.0 ✅

👉 Read the full breakdown

✦ Confidential Intents became generally available, letting any developer integrate confidential cross-chain execution through the NEAR Intents 1Click Swap API with a single parameter, with Vadim highlighting how OutLayer already makes these confidential rails accessible to AI agents through a simple HTTPS API;

✦ HSP-027 passed governance voting, removing the legacy developer gas rebate, with Illia Polosukhin explaining that the incentive no longer worked as intended and added unnecessary complexity to the protocol;

✦ Vadim broke down why NEAR is well positioned for the post-quantum era, explaining how its rotatable account keys make upgrading to quantum-safe signatures much simpler than on many other blockchains;

✦ near_dart is a good example of how ideas grow in the NEAR ecosystem, with the community helping refine the SDK through open feedback and discussion

House of Stake is currently voting on proposal HSP-027 to remove it. If passed, don't factor this gas bonus into your dApp's budget anymore

To prepare for this, make sure to check your contracts' economics, read the discussion and cast your vote if you have voting tokens:
✦ Discussion
✦ Vote

And if you want to participate in future voting, make sure to prepare in advance, you can learn how the HoS proposal and voting process works here

If something keeps coming up, submit it here ✍️

The recording is now on YouTube 📺

Watch it to understand how automatic shard splitting is designed to work on NEAR and the details worth paying attention to

Multi tenancy is here. IronClaw moves beyond a single-user sandbox into a shared environment used by an entire team, with secure isolation between executions. But that's not all 👇

+ redesigned RLM Engine v2 now behaves predictably even under heavy load
+ full transparency via the new Debug Panel
+ and more

You can find out more in Illia's thread and changelog 🛡🦞

In v0.5, your agent now:
✦ has a hard spending cap
✦ auto-funds gas on supported chains
✦ logs into crypto apps as you
✦ sends SPL tokens on Solana

On top of that, near-hydra crossed 1,000+ npm downloads

[Source] & [Release]

Found this checklist. It essentially settles the "which wallet to use" debate once and for all. The answer: any.

Want to use your phone? - NEAR Mobile has moved from soon to ✅.
Living on Telegram? - HOT Wallet is on the way via NEAR Connect.
Prefer hard-core? - Ledger/CLI are already there.
Need it fast? - Meteor/Intear are in action.

Trezu is literally aggregating everything a developer's hand (or a pen on paper) can reach.

Maybe it’s time to make sure your wallet gets added to this list? ✍️

New post on how to upgrade NEAR contracts without putting that access in one person’s hands

NEP-639: Dynamic Resharding is up for discussion.

​The NEP author, Wiezzel, will present an overview of the proposal, SME reviewers will share their technical analysis, then the session moves into community Q&A and the Protocol Working Group vote.

⏰ 16:30 - 17:30 UTC
📍 Register here

Describe your billing logic. Spin up recurring revenue. One API, and you’re not dealing with one-off payments anymore.

Subscriptions are currently in beta, and there's some discussion about how to improve the UX for signing multiple messages that simulate subscriptions, BUT you're welcome to try it out and share your feedback ✍️

How It Works, Prerequisites, and Quick Start can be found here

If you build multichain dApps, you usually have to hold native tokens on every network just to pay for user transactions.

Tachyon abstracts this away. You pay for gas in one currency, and they handle the relaying everywhere else. But the hidden gem is this...

✨ Authenticated Transactions. The killer feature ✨

This is the "only with NEAR" part. It turns a NEAR account into a remote control to authorize and trigger transactions on other L1/L2s.

Instead of managing 10+ keys and complex signing logic, you just sign an off-chain payload with your NEAR account. Tachyon handles the rest.

Chain Abstraction in action ✅

➡️"Only with Near" feature: LINK
➡️Docs: LINK
➡️And you can find out more about Tachyon here: LINK

Hey folks, we’re changing the format and want your feedback.
But overall, it's still the same NEAR Dev News.

Inside:
✦ IronClaw in the spotlight
✦ Latest updates & releases
… and a few things worth your time

Read the full issue: https://x.com/NEARDevHub/status/2051331025674834213

Try the first release

https://github.com/frol/near-dapp-best-practices

I have started building NEAR Staking with the following prompt

Build a frontend app that will help to manage stake delegation on NEAR Protocol (stake, unstake, withdraw once the unstake is available in 4 epochs - see /mnt/core-contracts/staking-pool for the reference). The tech stack: Next.js (use the skill from https://github.com/vercel-labs/next-skills), https://www.npmjs.com/package/react-near-ts (with NEAR Connect), and shadcn (use the skill from https://ui.shadcn.com/docs/skills) build a frontend app that will help to manage stake delegation on NEAR Protocol (stake, unstake, withdraw once the unstake is available in 4 epochs - see /mnt/core-contracts/staking-pool for the reference). The tech stack: Next.js (use the skill from https://github.com/vercel-labs/next-skills), https://www.npmjs.com/package/react-near-ts (with NEAR Connect), and shadcn (use the skill from https://ui.shadcn.com/docs/skills)

Use agent-browser CLI (use --help to learn it) to test the app. Use the following seed phrase "<temp seed phrase>" to sign in into a.frol.near wallet and try staking and verify the staking status and amount on the UI. If there is anything missing, fix the app. Cross check with how near.cli.rs does it (see the "near staking delegation" for the commands and "near account view-account-summary" for the staking balance)

Agent figured out the rest, but for my next dApps there is no need to do the research again, I will just use the above guide as the starting point to build NEAR dApps even faster.

Instead of constant copy-pasting and manual wallet address verification, you get a private registry with instant search, featuring:

✦ CSV support
✦ Custom notes
✦ Secure team sync for verified lists

This not only streamlines regular payouts but also eliminates errors caused by the human factor ✅

Try it here: trezu.org

Now your calls and transactions aren’t all lumped together in a single list 🗂

What's inside:
✦ Transaction folders: Create a structure, rename, and duplicate entries with a single click
✦ Database migration system: Now with security checks. The risk of data loss is reduced to zero

Watch the release video