The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees. The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance. Access to all other Claude models is not affected. We apologize for this disruption to our customers. We believe this is a misunderstanding and are working to restore access as soon as possible. Read our full statement: anthropic.com/news/fable-myt…

The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees. The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance. Access to all other Claude models is not affected. We apologize for this disruption to our customers. We believe this is a misunderstanding and are working to restore access as soon as possible. Read our full statement: anthropic.com/news/fable-myt…

Near@3.33 is live: an incentive milestone program for people using Confidential Intents on near​.com. If you've been swapping confidentially, you're already in for Drop 1.

As part of the NEAR ecosystem's long-term strategy, MyNearWallet (MNW) is planned to be deprecated on 31 October 2026. This process will happen gradually and in phases to ensure users have ample time to prepare and migrate to supported NEAR wallets. ✅ Your funds remain safe ✅ No immediate action is required ✅ Guided migration tools and instructions will be provided over the coming months You can learn more about the timeline, migration approach, and frequently asked questions here: 🔗 mynearwallet.com/sunset ⚠️ Security Reminder Never share your seed phrase, recovery phrase, or private key with anyone. MyNearWallet, Meteor Wallet, the NEAR Foundation, and support staff will never ask for this information.

⚡️ NEAR Mobile v3.10.0 is preparing a smoother login experience with auth.near.org Google, Apple, Email, or Passkey — designed to help users recover access and use the same wallet across ecosystem dapps. It also adds more BUY options with your local currency.

We need to talk about how we manage Full Access Keys for smart contract accounts on @NEARProtocol If you run a critical account like intents.near, your upgrade path usually comes down to two uncomfortable choices. You either keep a Full Access Key sitting on someone’s hardware wallet, which is just a human-shaped single point of failure, or build custom upgrade logic into the contract and pray a bad state migration never bricks it. The fix isn't hiding the seed phrase better. @Freol wrote about a clean setup for this a while ago using SputnikDAO and NEAR MPC. Instead of a single person holding a god key, an MPC public key is derived for the DAO account and attached as a Full Access Key to the contract account. When you need to push a patch: ✦ Generate the raw, unsigned DeployContract transaction payload for the contract account ✦ Request the multisig to sign the transaction with MPC ✦ If the multisig proposal is approved by the voting members, the multisig calls the MPC contract to sign it ✦ NEAR CLI combines the unsigned transaction with the resulting signature and submits it to the network The full private key never exists in one place, and no one holds it. Governance approves. MPC signs. The network executes.

Nice to see people loving NEAR's dynamic resharding. But I want to flag what it actually is: not a 2026 feature, but the payoff of a bet NEAR placed on day one, to shard the chain. Sharding splits the chain into parallel lanes so no single lane jams. But there's a catch. To check a lane, a validator (a machine that verifies the chain) normally has to store everything in it, so the number of lanes is capped by what one machine can hold, and adding a lane meant a slow, coordinated, network-wide upgrade. Real sharding needs validators that can verify a lane without storing it. That was the missing piece for years. NEAR shipped it in 2024, and that's the actual breakthrough: stateless validation. A validator now checks a lane from a small proof package, a slice of data plus a cryptographic receipt that it's correct, and never stores the lane. The correctness of a split is proven inside that package. So lanes stop being capped by one machine, and a lane can even split while the traffic is still moving. Dynamic resharding is that capability put on autopilot. This is why almost nobody else has it. Solana, Sui, Aptos, Monad never sharded, so they never needed it: one big machine does everything. That has a cost, though. A single machine has a ceiling, so the harder you push it the more brutal the hardware gets and the fewer people can run a node, and a big enough spike can stall the whole chain. Ethereum does need sharding's relief, but its original data structures make those proof packages huge, so getting there means migrating its entire live state to a new design, a multi-year job they keep redesigning, and once Ethereum pushed scaling onto L2s the urgency drained out. NEAR is the rare chain where sharding was the whole thesis, so solving this was do-or-die. And the bet keeps compounding. NEAR adds capacity by adding lanes while staying one road, one shared state, no bridges. Ethereum scaled by splitting into 20 separate roads (its L2s), and this March it had to launch a whole project just to glue them back so they can talk instantly again. NEAR never split the road. So enjoy dynamic resharding. Whether the agent traffic it's built for actually shows up is a separate question. The engineering under it is a years-old bet finally cashing out.

All-time volume on NEAR Intents just crossed $20 billion. This milestone is the result of a series of technical breakthroughs that removed some of the biggest constraints in cross-chain execution. A deep dive on Intents' rapid momentum 🧵

Most crypto teams get hacked not because of bad tech. But because someone had access they should not have had. Setting up roles and permissions correctly is the difference between a team that operates cleanly and one that is one compromised wallet away from losing everything. Three roles. One clear separation. Trezu gives you three roles: Requestor, Finance, and Governance. Requestors submit payment proposals. They cannot approve them. Finance members approve and execute payments. They cannot change the rules. Governance controls the treasury configuration. Adding members, changing thresholds, updating rules. If one person holds all three, you do not have a multisig. You have a single point of failure with extra steps. Thresholds matter as much as roles. A 3-of-3 setup sounds secure until one wallet is lost and the entire treasury is frozen permanently. A 1-of-1 means anyone on the Finance role can move funds alone. The sweet spot for most teams is 2-of-3. Enough redundancy to survive a lost key. Enough friction to prevent unilateral action. What this looks like at different stages. Early stage: Finance at 1-of-2 on everyday wallets. Governance at 2-of-3 on hardware wallets only. Growing startup: Finance at 2-of-3 held by Finance Lead, Ops Manager, and CEO. Governance at 3-of-5 with founders and board. Active DAO: Finance at 3-of-5 for your ops working group. Governance at 4-of-7 to prevent hostile takeovers. When to update your setup? New hire in a financial role. Someone leaving. A new funding round. A promotion to leadership. Any of these should trigger a review. Your treasury should grow with your team. Getting this right from day one costs nothing. Getting it wrong can cost everything.

Running payroll on a public multisig means every salary is public. Every vendor payment. Every trade size. Not every team signed up for that level of transparency. Trezu lets you choose. Public treasury for open governance. Confidential treasury for everything else.

3 months ago we shipped Confidential Intents on NEAR. This chart is the single most important metric for Confidential Intents. 🧵

3 months ago we shipped Confidential Intents on NEAR. This chart is the single most important metric for Confidential Intents. 🧵

Stablecoins from @StablREuro (EURR and USDR) got exploited for ~$10M. Both have depegged by over 20%, with the attack reportedly still ongoing. Another key compromise attack, this time a 1-of-3 minting multisig. Seems like no weekend this year without a hack...

This is damn cool! near:native