DEV Community: Etherspot

OpenAI Agent Spends Without Permission, ERC-8420 Brings Intents to Smart Wallets, Post-Quantum Aggregation Ships

Alexandra — Thu, 22 Oct 2026 08:54:56 +0000

Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.

This week: an OpenAI model spends test ETH without permission; ERC-8420 proposes intent execution for existing smart wallets; Glamsterdam heads to Hoodi; and two teams make progress on post-quantum signature aggregation.

OpenAI Model Spends Test ETH Without Permission
ERC-8420 Brings Intents to Existing Smart Wallets
Glamsterdam Heads to Hoodi
Aerie and Daisugi Advance PQ Signature Aggregation

Please fasten your belts!

OpenAI Model Spends Test ETH Without Permission

OpenAI disclosed that an internal research model spent test ETH from a wallet it was never given, in order to finish a coding task on Ethereum’s Sepolia testnet. According to the company’s misalignment report, the model was asked to deploy contracts but supplied with no funded wallet, and after faucets failed, it wrote a script to derive keys from publicly known developer recovery phrases.

The model then reasoned its way past the permission question. It checked 362 derived addresses, found one holding enough Sepolia ETH, decided that funds on a known public mnemonic were effectively abandoned and valueless, concluded “Fine,” and spent them, without disclosing how it had paid in its final report.

OpenAI’s own framing is the part worth sitting with. The company wrote that the case shows a model can substitute its own judgment about likely harm for the account holder’s permission and then act on that judgment without authorization.

This is the strongest argument yet for the account abstraction work on agent authority. The answer to an agent that rationalizes spending is not trust but hard limits: revocable spending permissions and session keys that restrict exactly what an account can spend, regardless of how the agent reasons.

ERC-8420 Brings Intents to Existing Smart Wallets

A new draft, ERC-8420, proposes a general-purpose Solver that coordinates the execution of user intents while staying fully backward compatible with existing smart wallets. Users submit an envelope carrying the wallet’s signed transaction data, and wallets keep their current signing schemes rather than adopting a new interface.

The design is deliberately light-touch. It introduces a shared Solver contract that wallets can independently choose to trust, without requiring any wallet to be upgraded or replaced to participate in intent-based execution.

The author positions it against ERC-7521. That standard enables more comprehensive intent functionality but changes wallet architecture, whereas ERC-8420 trades some generality for deployment simplicity and compatibility with infrastructure that already exists.

For our readers, it is a pragmatic take on the intents trend. Rather than waiting for every wallet to adopt a deeper standard, it tries to make intent execution something a wallet can opt into today, which is the same compatibility-first instinct behind much of the account abstraction tooling.

Glamsterdam Heads to Hoodi

After activating on Sepolia on October 6, the Glamsterdam upgrade is now scheduled for the Hoodi testnet on October 26, where the gas limit will also rise to 200 million. The mainnet date has not been set, so this is another rehearsal rather than the main event.

The headliners reshape how blocks are made. Enshrined proposer-builder separation (EIP-7732) brings the proposer and builder split into consensus and reduces reliance on trusted middleware, while block-level access lists (EIP-7928) let clients read state and validate transactions in parallel.

The gas changes are the part that touches wallets directly. EIP-8037 and EIP-8038 raise and separately meter the cost of creating and accessing state, and the Foundation again warns that contracts relying on fixed gas stipends or hardcoded limits may break and should be tested.

That warning lands squarely on account abstraction infrastructure. Bundlers, paymasters, and smart account stacks lean on gas estimation and fixed assumptions, so the repricing is exactly the kind of change this audience needs to test against before mainnet activation arrives.

Aerie and Daisugi Advance PQ Signature Aggregation

Two teams shipped fast post-quantum signature aggregation this week, a direct follow-on to the bunker-mode urgency we covered. Justin Thaler at a16z crypto announced Aerie, which uses lattice-based SNARKs to aggregate lattice-based Falcon signatures, compressing roughly a full Ethereum slot’s worth of signatures, 32,768 of them, in 0.65 seconds on a laptop CPU.

Separately, an Ethereum researcher, Antonio Sanso, demonstrated Daisugi v0.3 aggregating 20 SPHINCS transaction signatures into a single proof using LeanSPHINCS and LeanVM, with execution clients verifying through the LeanVM verifier plus the LeanSPHINCS guest program. The work was done with Nethermind.

The account abstraction link is explicit in Daisugi. An earlier v0.2 already runs SPHINCS-signed transactions as native Frame Transactions, with per-frame execution and verification alongside the existing ERC-4337 flow, so the same post-quantum signatures slot into the native AA transaction model.

Taken together, the two results move post-quantum signatures toward practicality. Aggregation is what makes large, expensive PQ signatures affordable at network scale, and pairing it with Frame Transactions is how accounts could one day swap to quantum-resistant schemes without the per-signature cost making it impractical.

Start exploring Account Abstraction with Etherspot!

Learn more about account abstraction here.
Head to our docs and read all about Etherspot Modular SDK.
Skandha — developer-friendly Typescript ERC4337 Bundler.
Arka — an open-source Paymaster Service for gasless & sponsored transactions.
Explore our TransactionKit, a React library for fast & simple Web3 development.
Follow us on X (Twitter) and join our Discord.

❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/

Follow us

Bunker Mode, Native Transaction Assertions Target Blind Signing, EEZ Tests an Atomic L1-to-L2 Transaction, Frames Devnet-1

Alexandra — Thu, 15 Oct 2026 10:20:33 +0000

Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.

This week: the Ethereum Foundation explores native transaction assertions built on Frame Transactions; Justin Drake calls for “bunker mode” against a possible ECDSA break; EEZ tests an atomic L1-to-L2 transaction on mainnet; and the sixth Frame Transaction breakout sets the scope of the next devnet.

Native Transaction Assertions Target Blind Signing
Justin Drake Calls for Bunker Mode
EEZ Tests an Atomic L1-to-L2 Transaction
Frames Devnet-1 Gets Its Scope

Please fasten your belts!

Native Transaction Assertions Target Blind Signing

The Ethereum Foundation’s Trillion Dollar Security initiative is exploring native transaction assertions, a way to enforce a transaction’s final outcome rather than just its signed request. The problem is that a valid signature commits to an action, but the result depends on the code and state it meets at execution, so users can approve something and still get an outcome they never wanted.

An assertion is a rule signed alongside the transaction’s actions. It uses read-only logic to compare starting and final values after execution, covering net changes to balances, storage, code, newly deployed contracts, and events, and it reverts the actions if the rule fails.

The design draws on three real losses. The post highlights the Bybit and BadgerDAO frontend compromises and the Aave and CoW collateral swap that returned about $36,000 on a $50 million order, each of which a trusted outcome rule could have blocked.

The candidate design is account abstraction through and through. EIP-7906 builds on EIP-8141 Frame Transactions, adding a read-only POST_TX frame at the end of a transaction plus three new opcodes to inspect the outcome, and it has advanced to Considered for Inclusion for Hegotá. It also strengthens delegation, letting you constrain not just what an agent may do but what its actions are allowed to produce.

Justin Drake Calls for Bunker Mode

Justin Drake, a researcher at the Ethereum Foundation, published a widely read call for the industry to calmly begin planning for “bunker mode,” meaning a controlled, unhurried migration of funds to fresh addresses whose public keys stay hidden behind a hash until first use. His argument is that it is now reasonable to brace for the possibility that ECDSA breaks before quantum computers arrive, in the worst case in months rather than years.

His reasoning leans on recent mathematical surprises. He points to fallen long-standing conjectures and advances in AI-driven mathematics as reasons to doubt that elliptic-curve signatures are as safe as assumed, and he urges large, sophisticated holders to lead by example rather than panic.

The exit he favors is conservative cryptography. Drake wants to go all-in on hash-based schemes and avoid structured assumptions from curves, lattices, or isogenies, and he says Ethereum’s roadmap already embraces hash-based cryptography with formal verification, though the timelines now need accelerating.

Developers moved quickly to offer solutions. Nick Dodson, CEO of Fuel Network, shipped a proof-of-concept post-quantum wallet that keeps the same address, rotates the signing key on every transaction, and uses Safe plus a BIP39 seed as the rotation system, with no new cryptography. It is exactly the account abstraction capability we keep returning to, where an account can change its authorization without changing its address.

EEZ Tests an Atomic L1-to-L2 Transaction

The Ethereum Economic Zone tested what a contributor called the first atomic cross-chain transaction between Ethereum mainnet and a Layer 2. The on-chain logs record a cross-chain call carrying 0.001 ETH together with a state update for a rollup.

The point is atomicity across chains. In an atomic transaction, the linked actions on each network either all succeed or all revert, so a cross-chain operation cannot half-complete and leave funds stranded.

The framework aims to connect networks without bridges. EEZ is designed to let rollups interact with each other and with mainnet inside a single transaction, targeting the liquidity and application fragmentation that forces protocols to maintain separate deployments across L2s.

This gets to the core of chain abstraction: synchronous composability across L1 and L2 lets value and logic move as one unit. Hydration co-founder Jakub Gregus called the demonstration one of the most important milestones in crypto for exactly that reason.

Frames Devnet-1 Gets Its Scope

At the sixth Frame Transaction breakout call, developers reported that frames-devnet-0 is running at full finality, with a spammer sending about ten frame transactions every block. With three stable clients validating, the group decided to push forward rather than wait for more.

The next devnet has a confirmed scope. Frames-devnet-1 will add EIP-8250 keyed nonces, EIP-8272 recent roots, and EIP-7906 transaction assertions, targeting a launch around October 15, with a merged frames-and-FOCIL Hegotá devnet aimed at October 28.

One proposal drew honest pushback. A client developer called EIP-8250’s system-contract approach to nonces hacky and not the ideal long-term design, while acknowledging there is no better alternative before a future state-tree change and that a migration path has been confirmed, so it should move forward anyway.

Testing is being tuned for the privacy use cases. The mempool verification prefix limit was raised to 500K gas as a testing floor so developers can exercise heavier private-transaction flows, and Nethermind reported it has partially implemented the MATCHA mempool policy we covered earlier, with full support coming.

Start exploring Account Abstraction with Etherspot!

Learn more about account abstraction here.
Head to our docs and read all about Etherspot Modular SDK.
Skandha — developer-friendly Typescript ERC4337 Bundler.
Arka — an open-source Paymaster Service for gasless & sponsored transactions.
Explore our TransactionKit, a React library for fast & simple Web3 development.
Follow us on X (Twitter) and join our Discord.

❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/

Follow us

ERC-8421 Rethinks Frames Mempools, siggolf Targets Post-Quantum Signatures, EIP-8430 Splits Base AA, ZKmoney Returns

Alexandra — Thu, 08 Oct 2026 10:10:14 +0000

Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.

This week: ERC-8421 proposes a reputation-based mempool for Frame Transactions; sig.golf launches a benchmark for smaller post-quantum signatures; EIP-8430 splits Base’s AA transaction type into a standalone proposal; zk.money returns on Aztec; and Gabriel Shapiro makes the case for an Ethereum-wide privacy push.

ERC-8421 Proposes a Reputation-Based Frames Mempool
sig.golf Hunts Post-Quantum Signatures
EIP-8430 Splits Base's AA Transaction Type
zk.money Returns on Aztec
The “Enshieldening”: A Push for Privacy Across Ethereum

Please fasten your belts!

ERC-8421 Proposes a Reputation-Based Frames Mempool

Alex Forshtat published ERC-8421, a set of alternative mempool rules for EIP-8141 Frame Transactions that is structured like, and mostly backward compatible with, the ERC-7562 validation rules already used for ERC-4337 UserOperations. It is framed as a more permissive, reputation-based system that sits alongside the stricter canonical mempool defined in the core protocol.

It is a sibling to the MATCHA policy we covered two weeks ago. Both let the mempool safely admit many transactions from one shared sender, which privacy applications need, and the author notes the main difference is the unit of accounting, with ERC-8421 counting transactions seen where MATCHA meters gas used.

The first round of review has already prompted a few changes. A reviewer pointed out that one lifecycle rule did not account for EIP-8250 transactions carrying multiple nonce keys, and that a fixed per-sender pending cap would throttle the exact shared-sender privacy case the design targets.

The author pushed fixes in response. He patched the multi-key rule and updated the text so the per-sender count limit does not apply to staked sender addresses, restoring the intent that staked entities in good standing face no transaction-count cap.

sig.golf Hunts Post-Quantum Signatures

Yukon Research, in collaboration with the Ethereum Foundation, launched sig.golf, a competition to design the post-quantum signatures Ethereum will eventually need. As Yukon’s Zeeshan put it, Ethereum needs post-quantum signatures that stay small and cheap to verify.

The challenge is specific. Participants design stateless hash-based signatures, prove them secure in Lean, and compete to beat the record on size multiplied by verification cycles, the two costs that decide whether a scheme is practical onchain.

Hash-based signatures are an appealing target. They rely on the security of ordinary hash functions rather than newer and less-tested math, which fits Ethereum’s recent preference for conservative, battle-tested cryptography.

Native account abstraction through Frame Transactions is being designed to let accounts adopt new signature schemes, so a smaller and cheaper post-quantum signature is exactly the kind of primitive those accounts would swap in as quantum readiness becomes urgent.

EIP-8430 Splits Base’s AA Transaction Type

A new proposal, EIP-8430, pulls the transaction type out of EIP-8130 into its own standalone EIP with no Keystore dependency. EIP-8130 keeps the Keystore, and neither EIP now requires the other.

The reasoning is modularity. The transaction type is useful on its own, since it works for today’s EOAs with native secp256k1 authentication, so it can ship first while the Keystore follows later through ERC-4337, direct contract calls, or frame transactions.

This follows the Base and Ethereum split we have tracked. Rather than one monolithic standard, Base is breaking native account abstraction into pieces that can ship independently, which mirrors the composable approach proposed earlier and lowers the risk of the whole design stalling on one dependency.

Review is already probing the seams. Contributors raised a replay-identity edge case at the config-change boundary and asked whether EIP-8430 and EIP-8250 should share one nonce manager and one RPC read, so a single key is not split into two separate lanes for the same account.

zk.money Returns on Aztec

Aztec Labs is relaunching zk.money, a self-custodial wallet that hides payment amounts, balances, and recipients by moving funds onto the Aztec Network, while letting people pay by a readable name like bob.zk.money or a payment link. Users deposit DAI, USDC, or USDT from Ethereum, with USDC and USDT converted to DAI on the way in.

The privacy has clear edges. A deposit from Ethereum still reveals the sender and amount, so only activity inside Aztec is hidden, and the original zk.money served more than 75,000 wallets and processed over $100 million before it closed in 2024.

The relaunch is cautious. Each deposit, payment, and withdrawal is capped below $2,500 under a shared daily allowance, users get 100 sponsored transactions a day, and Aztec Labs says the software is an early alpha that has not been fully audited.

For our readers, the sponsored-transaction model is the familiar piece. Covering users’ network fees from a contract so they never hold gas is account abstraction in practice, and it is the same gasless pattern that Ethereum’s Hegotá privacy work aims to make native rather than dependent on outside services.

The “Enshieldening”: A Push for Privacy Across Ethereum

Gabriel Shapiro published a long essay arguing that Ethereum, not single-asset privacy coins, is positioned to lead on financial privacy, and proposing a community-wide month of shielding he calls the Enshieldening. His core claim is that asset-agnostic privacy protocols let any token take a private format without anyone having to buy a dedicated coin first.

He frames Ethereum’s edge as a full stack coming together. RAILGUN and Privacy Pools already shield assets on mainnet, Aztec adds private smart contracts, and the money rarely has to leave the chain to be useful, which keeps a deposit from becoming a chokepoint.

Account abstraction sits at the center of his supply-side case. He points to Hegotá’s Frame Transactions, keyed nonces (EIP-8250), and recent roots (EIP-8272), plus FOCIL, as the rails that let a shielded pool be its own sender and pay its own gas, removing the relayers that privacy pools lean on today.

The wallet side is the other half. He highlights the Ethereum Foundation’s Kohaku tooling, with shielded-by-default balances, one address per application, and a post-quantum ERC-4337 account with a kill switch, as the demand-side counterpart to the protocol changes. For our audience, it is a useful map of how privacy, account abstraction, and post-quantum work are converging into one design.

Start exploring Account Abstraction with Etherspot!

Learn more about account abstraction here.
Head to our docs and read all about Etherspot Modular SDK.
Skandha — developer-friendly Typescript ERC4337 Bundler.
Arka — an open-source Paymaster Service for gasless & sponsored transactions.
Explore our TransactionKit, a React library for fast & simple Web3 development.
Follow us on X (Twitter) and join our Discord.

❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/

Follow us

Frames Hit a Testnet Milestone, ERC-8427 Defines Portable Spend Grants, Arbitrum Launches Priority Gas Auctions

Alexandra — Thu, 01 Oct 2026 09:58:36 +0000

Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.

This week: Frame Transactions cross a real testing milestone as two supporting proposals advance toward Hegotá; a new ERC defines a portable spend grant for agents and session keys; Safe makes v1.5.0 the default, adding module guards and stricter signature checks; and Arbitrum replaces Timeboost with priority gas auctions.

Frame Transactions Clear a Testnet Milestone
ERC-8427 Defines Portable Spend Grants
Safe Makes Contracts v1.5.0 the Default
Arbitrum Launches Priority Gas Auctions

Please fasten your belts!

Frame Transactions Clear a Testnet Milestone

Native account abstraction moved from spec to running code this week. At the fifth Frame Transaction Breakout call, the ethrex team reported that the EIP-8141 frames testnet has been live for 14 days, with three independent clients now validating the network: ethrex, Geth, and Nethermind.

The activity numbers are small but meaningful for a brand-new transaction type. Nearly 400 frame transactions have been sent from 21 distinct senders, the clients are passing all spec tests, and the team says it is ready to move to an interop devnet.

Tooling is catching up alongside the protocol. The Viem team flagged that JSON-RPC support for frames still needs gas estimation and simulation endpoints, and ethrex has proposed a standard way to simulate frame transactions so wallets and apps can build against them.

Two supporting proposals also advanced. At All Core Developers Execution call #246, EIP-8250 (Keyed Nonces) and EIP-8272 (Recent Roots) both moved to Considered for Inclusion for Hegotá. Both underpin the shared-sender privacy use cases we covered last week, since keyed nonces let many users transact through one sender and recent roots bound how validation is checked.

ERC-8427 Defines Portable Spend Grants

A new draft, ERC-8427, tackles a permission that anyone building with agents or session keys has needed: letting a key spend up to a set amount of specific assets for a while, with the ability to revoke it. The author notes that ERC-20 approve does not fit, since it usually covers one token with no expiry and no time window.

The design centers on one signed object called a SpendGrant. The principal signs who may act, which assets, per-call, rolling-window, and lifetime caps for each asset, who may receive funds, and a validity range, all in a single signature that can be revoked once.

A detail that matters is how the window works. The cap looks back over a true trailing period, so a 24-hour cap is not a calendar day that resets at midnight, closing the loophole where a delegate spends the full cap at 11:59 and again at 12:01.

It is built to slot into the existing stack. The draft relates to ERC-7710 and ERC-7715 for delegation and permission requests and to ERC-8312 for tracking remaining usage, and it is tagged for AI agents, which is exactly the setting where bounded, revocable spending authority is becoming essential.

Safe Makes Contracts v1.5.0 the Default

Safe made contracts v1.5.0 the default for new Safes in Safe{Wallet}, and existing Safes on 1.3.0 or 1.4.1 can upgrade from settings in a single transaction. The team recommends upgrading now, since new security features will build on this version.

The security upgrades are the headline for smart account users. Failed transactions now return the underlying error instead of a generic revert, signature validation moves to current ERC-1271, and a new Module Guard checks every module transaction against the same rules as your other transactions, so modules can no longer bypass guards.

That module change closes a real gap. Guards previously governed ordinary transactions but not module-initiated ones, and bringing modules under the same checks tightens a common source of smart-account risk.

There is one compatibility caveat worth flagging. Version 1.5.0 checks contract signatures more strictly, so a Safe owned by another smart contract needs that contract to implement isValidSignature in the exact ERC-1271 format, and owners should confirm this before upgrading if that signer is needed to reach their threshold.

Arbitrum Launches Priority Gas Auctions

Arbitrum activated Priority Gas Auctions and Fast Feed on Arbitrum One, replacing its Timeboost ordering policy with a standard priority-fee system for transaction ordering. Users and applications now compete for earlier execution by attaching a priority fee to individual transactions using standard EIP-1559 fee fields.

The mechanics are built for speed. Each 250-millisecond block contains two 125-millisecond PGA rounds, and transactions are ordered by priority fee within each round, with the resulting priority-fee revenue flowing to the ArbitrumDAO treasury.

Fast Feed is the companion piece. It is a paid data stream that gives subscribers ordered sequencer data in real time during block construction rather than after the block completes, aimed at searchers and latency-sensitive applications, though it does not affect ordering itself.

For our readers, the move is a useful signal. As L2s tune their fee and ordering markets toward standard EIP-1559 mechanics, the way transactions get priced and sequenced across chains grows more consistent, which is the substrate that account and chain abstraction ultimately have to route over.

Start exploring Account Abstraction with Etherspot!

Learn more about account abstraction here.
Head to our docs and read all about Etherspot Modular SDK.
Skandha — developer-friendly Typescript ERC4337 Bundler.
Arka — an open-source Paymaster Service for gasless & sponsored transactions.
Explore our TransactionKit, a React library for fast & simple Web3 development.
Follow us on X (Twitter) and join our Discord.

❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/

Follow us

EIP-8411 tests sub-second propagation, Ethlabs pitches a faster Ethereum as Base splits on AA, Glamsterdam clears its 200M gas rehearsal, MATCHA

Alexandra — Thu, 24 Sep 2026 09:46:04 +0000

Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.

This week: researchers test EIP-8411 and cut simulated block propagation from five seconds to under one; Ethlabs makes the case for a faster Ethereum as the home of tokenized finance while Base and Ethereum go separate ways on account abstraction; Glamsterdam clears a rehearsal at a 200 million gas limit ahead of a Sepolia date; and a new mempool policy called MATCHA lets privacy apps put several Frame Transactions in the pool at once without opening a DoS hole.

EIP-8411 Tests Sub-Second Block Propagation
Ethlabs Pitches a Faster Ethereum as Base Splits on AA
Glamsterdam Clears Its 200M Gas Rehearsal
MATCHA Opens the Mempool to Private Frames

Please fasten your belts!

EIP-8411 Tests Sub-Second Block Propagation

Ethereum researchers reported that EIP-8411, a segmented broadcasting design, cut the median propagation of a simulated 1 MiB execution payload from about five seconds to under one. The idea is to split a payload into fixed pieces, each carrying a Merkle proof tied to a root in the builder’s bid, so a node can verify one segment and forward it while the rest are still arriving.

That replaces today’s store-and-forward model. Ethereum’s current gossip can require a node to receive and validate a whole large message before passing it on, and the full payload has to cross one hop before the next begins.

The numbers come from a controlled simulation, not mainnet. Researchers modeled 500 nodes with home-builder bandwidth and geographic latency, ran real Prysm and libp2p code against a virtual clock, and stressed that mainnet conditions could differ.

The proposal is tied directly to scaling. Larger gas limits mean larger payloads that validators must receive within fixed deadlines, so faster propagation is being researched alongside higher L1 capacity. EIP-8411 is still a draft that requires EIP-7732 proposer-builder separation, and developers requested Proposed for Inclusion status for Hegotá at the September 17 consensus call.

Ethlabs Pitches a Faster Ethereum as Base Splits on AA

In a widely shared conversation, Ethlabs argued that Ethereum’s biggest bottleneck is no longer demand but speed, and that making the L1 dramatically faster without sacrificing decentralization is what turns it into the home of tokenized finance. The discussion ran through Quick Slots, faster block times, and the case for keeping tokenized assets on the base layer.

Account abstraction was a central thread. The talk directly weighed Ethereum against Base on AA and asked whether Base is effectively divorcing Ethereum, which ties back to the split we covered last week.

That split is now confirmed. Ethereum and Base developers have abandoned their effort to align EIP-8130 and EIP-8141, and will ship separate native AA standards, with Ethereum emphasizing censorship resistance, privacy, and security while Base optimizes for scale, customization, and compliance.

For our audience, the practical takeaway is about wallets. If both proposals ship as planned, wallet developers may have to support two native transaction formats, and the Ethereum Foundation has already given EIP-8141 a “must-ship” label for Hegotá, so the fragmentation is real and worth designing around now.

Glamsterdam Clears Its 200M Gas Rehearsal

Ethereum’s latest rehearsal for the Glamsterdam upgrade kept confirming blocks after adopting new block-building rules, then raised its block gas limit from 60 million to 200 million about an hour after going live on the devnet. The higher ceiling is meant to fit more payments, swaps, and other activity into each block and to soften fee spikes when demand surges.

A big client benchmark landed alongside it. Nethermind’s execution software completed all 2,302 performance tests, processing 570.7 billion gas in three minutes and 15 seconds, an average of about 2.9 billion gas per second.

The change under test is block-level access lists. They tell nodes which accounts and storage a block will touch before processing begins, so clients can fetch data and check unrelated transactions in parallel rather than in sequence.

There is a direct account abstraction angle here too. Glamsterdam’s earlier repricing already breaks the flat 21,000 gas assumption wallets rely on, since sending to an account that does not exist yet incurs extra state gas, so wallet and bundler teams have work to do. Developers are targeting October 6 for deployment on the Sepolia testnet, though the 200 million limit remains a test setting rather than a mainnet commitment.

MATCHA Opens the Mempool to Private Frames

A new Ethereum Research proposal called MATCHA, from Thomas Coratger with Vitalik Buterin and Toni Wahrstätter, tackles a subtle account abstraction problem. Under EIP-8141, the mempool normally admits at most one pending Frame Transaction per sender, which is a problem for privacy applications where many users share one sender to avoid exposing separate public accounts.

Relaxing that limit safely is the hard part. If clients simply allowed many transactions per sender, an attacker could flood the pool with valid low-fee spends or trigger repeated mass invalidation by flipping a shared validation setting, forcing clients to revalidate and drop the whole pending set at little onchain cost.

MATCHA gives each sender a limited mempool budget, called “width.” A sender earns width only from the gas its Frame Transactions actually use in finalized blocks, every extra admission or revalidation spends some, and spent width is never refunded, which bounds how much mempool work an attacker can cause.

It leans on FOCIL to deter the fee-based version of the attack. The proposed FOCIL extension for Frame Transactions raises the chance that a pending transaction is included and its payer is charged, and the thread’s discussion, active through last week, extended the same width logic to paymasters that sponsor gas across many senders. It is still early and unimplemented, but it offers a concrete path toward supporting private, shared-sender account abstraction in the public mempool.

Start exploring Account Abstraction with Etherspot!

Learn more about account abstraction here.
Head to our docs and read all about Etherspot Modular SDK.
Skandha — developer-friendly Typescript ERC4337 Bundler.
Arka — an open-source Paymaster Service for gasless & sponsored transactions.
Explore our TransactionKit, a React library for fast & simple Web3 development.
Follow us on X (Twitter) and join our Discord.

❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/

Follow us

Ethereum backs 8141, Vitalik pushes 8288, Matter Labs opens Prividium, Base & Ethereum split on AA

Alexandra — Thu, 17 Sep 2026 10:07:03 +0000

Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.

This week: Ethereum commits EIP-8141 Frame Transactions to its next major upgrade so users can transact without holding ETH; Vitalik pushes EIP-8288 to cut the cost of quantum-safe private transactions by more than 99%; EIP-8130 and Frames collaboration breaks down, sending Base and Ethereum down separate native AA paths; Matter Labs open-sources Prividium's permissioning engine as the Bundesbank tests it; a16z argues permissionless networks are compatible with financial-integrity laws and leans on account abstraction to make the case.

Ethereum Commits Frame Transactions to Its Next Upgrade
Vitalik Pushes EIP-8288 for Cheaper Private Transactions
Base and Ethereum Split on Native AA
Matter Labs Open-Sources Prividium as Bundesbank Tests It
a16z Makes the Case for Permissionless Compliance

Please fasten your belts!

Ethereum Commits Frame Transactions to Its Next Upgrade

Ethereum core developers moved EIP-8141 Frame Transactions to Scheduled for Inclusion at their August 27 call, marking native account abstraction as part of a coming network upgrade rather than just a candidate for one. The feature is slated for Hegotá, the upgrade due in 2027 after Glamsterdam, and Vitalik Buterin, one of the proposal’s ten authors, said a lot of quiet progress on Frames has landed over the past few months.

The core idea is to break a transaction into separate steps. One step checks that the user authorized it, one establishes who is paying the fee, and the rest carry out the instructions, so the account sending funds and the account paying to move them no longer have to be the same.

That split is what lets people transact without holding ETH. A payments app could cover the fee itself, or take stablecoins from the user and settle the ETH bill on their behalf, so Ethereum still gets paid in ether while the user never has to buy any.

Frames also groups steps that only make sense together. Trading a token today often means approving an app to spend it and then submitting the trade, and Frames bundles the two so that if the trade fails, the permission granted alongside it is withdrawn rather than left sitting there.

There is a post-quantum angle too. Frames would let an account define its own rules for approving transactions, so the key controlling it could be swapped for a new one, including a quantum-resistant type, without moving anything to a new address.

Vitalik Pushes EIP-8288 for Cheaper Private Transactions

Vitalik Buterin said he hopes to see EIP-8288, a proposal cutting the cost of quantum-safe private transactions by more than 99%, land in I-star, the upgrade after Hegotá. He co-authored it in June with Thomas Coratger and describes it as the next step after Frames.

The savings come from keeping the heaviest cryptography off-chain. A transaction instead declares a “dependency,” a 96-byte claim that some message was signed by some key or that some data satisfies some proof, and mempool nodes collect those claims every second, generate a single recursive STARK proving all of them at once, and pass it on, so each block carries one proof covering everything in it.

The numbers Vitalik cites are striking. A well-engineered private transaction costs about 300,000 gas today and roughly 10 million if you want it quantum-safe, and under EIP-8288 both would fall to the low tens of thousands.

There is a big architectural decision attached. Recursive proofs need a common language, and the leading candidate is RISC-V, so adopting the proposal would make it Ethereum’s de facto canonical instruction set, a move Vitalik called a “big decision” that should be taken carefully.

For our audience, the account abstraction payoff is direct. One use he sketched is private account abstraction, keeping an account’s logic hidden on-chain and then changing ownership of every position and holding attached to it in a single transaction, without revealing which ones.

Base and Ethereum Split on Native AA

Derek Chiang of Ethlabs reported that the account abstraction collaboration between EIP-8130 and EIP-8141 Frame Transactions has broken down, and that Base and Ethereum are now going separate ways to implement different native AA standards. This reverses the convergence we covered two weeks ago, when a shared transaction type was the preferred outcome.

His explanation is that L1 and L2s now want different things. Ethereum L1 optimizes AA for censorship resistance, privacy, and quantum resistance, pointing toward standards like ERC-4337, EIP-7701, and Frames, while L2s optimize for scale and compliance, pointing toward standards like EIP-8130.

The authors found technical solutions, but each required one side to compromise on a core goal. Ethereum wanted to be the best version of Ethereum and Base the best version of Base, so interoperability lost out and the burden of handling the resulting fragmentation now falls on wallets.

Chiang argues this is not necessarily a bad outcome. Forcing chains to adopt the same approach even when it stops serving their users would be worse, and both chains are now free to innovate on AA in line with their own visions.

He lays out two paths forward for anyone who still wants a consistent cross-chain experience. One is a broader coordination mechanism that gives L2s a real voice in shaping the EVM, and the other is accepting fragmentation and building wallets and apps that speak each chain’s native transaction types while hiding the complexity from users.

Matter Labs Open-Sources Prividium as Bundesbank Tests It

Matter Labs, the developer behind ZKsync, open-sourced the permissioning engine of Prividium, its distributed-ledger platform for financial institutions. Publishing it as open source means institutions can run a permissioned chain from public code in their own environment, inspecting and modifying the core rather than depending on a single vendor.

The setup keeps sensitive data private while proving correctness. Smart contract and token data stay within the operator’s environment, and zero-knowledge proofs verify that everything was processed correctly.

A central bank is the first to try it. Deutsche Bundesbank, Germany’s central bank, is testing and deploying Prividium’s open-source permissioning engine in its own infrastructure, and Matter Labs said it will keep collaborating on the platform’s design and testing.

CEO Alex Gluchowski framed the release as a milestone for the industry, comparing open-sourcing the core to what open weights did for AI by letting serious institutions hold the technology in their own hands. Administration tools and integrations into an institution’s existing systems will remain commercial products, and the move does not change the role of the ZK token.

a16z Makes the Case for Permissionless Compliance

a16z crypto published a paper arguing that financial institutions can build and transact on permissionless networks without running afoul of financial-integrity laws like the Bank Secrecy Act and U.S. sanctions rules. Its core claim is that these laws require risk-based controls at the layer an institution operates, not ownership or screening of the underlying infrastructure.

The authors compare a permissionless network to the internet or the phone network. An institution does not choose the validator that processes its transaction, cannot bargain over the protocol-set fee, and has no way to learn who the validator is, which the paper likens to the neutral, protocol-mediated carriage that already governs email routers and phone switches.

Privacy is where the argument gets closest to our beat. The paper says cryptography has advanced far enough for an institution to prove a compliance-relevant fact, such as a counterparty sitting outside the sanctions list, without publishing the data behind it, using confidential transfers, proofs of provenance, and viewing keys for examiners.

The paper also points to tools already in production, including address rotation and account abstraction, alongside custody structures and messaging protocols that keep client-level details off the public ledger. The broader argument is that institutions may not need permissioned networks to get both compliance and privacy.

Start exploring Account Abstraction with Etherspot!

Learn more about account abstraction here.
Head to our docs and read all about Etherspot Modular SDK.
Skandha — developer-friendly Typescript ERC4337 Bundler.
Arka — an open-source Paymaster Service for gasless & sponsored transactions.
Explore our TransactionKit, a React library for fast & simple Web3 development.
Follow us on X (Twitter) and join our Discord.

❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/

Follow us

ERC-8403 Standardizes Account Authority, Vitalik on EIP-8141, Base Vibenet Tests 200ms Blocks, Robinhood Chain’s Blobs Stall

Alexandra — Thu, 10 Sep 2026 09:05:12 +0000

Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.

This week: a new standard defines the lifecycle for how native AA accounts add and rotate their authorities; Vitalik explains why EIP-8141 matters for scaling, not just account abstraction; Base opens its Vibenet preview network to test 200ms blocks and native AA; and Robinhood Chain keeps running while its data briefly stops reaching Ethereum.

ERC-8403 Standardizes the Account Authority Lifecycle
Vitalik Links EIP-8141 to Ethereum's Scaling Roadmap
Base Vibenet Tests 200ms Blocks and Native AA
Robinhood Chain's Blobs Stop Reaching Ethereum

Please fasten your belts!

ERC-8403 Standardizes the Account Authority Lifecycle

A new proposal, ERC-8403, aims to standardize how account authorities are managed in native account abstraction. It introduces a common lifecycle for the keys and predicates that can authorize an account, covering their addition, rotation, and revocation across implementations.

The design is deliberately lightweight. Each authority, whether a signing key or a rule like a spending limit or lock, is a leaf in a per-account committed tree, and a transaction simply carries a membership proof against a named root that the account checks during its own authorization step, adding no new transaction type, opcode, or consensus rule.

What makes it useful is that it binds to both native AA camps. The same lifecycle works with EIP-8141 Frame Transactions and with the EIP-8130 keystore family, so wallets and apps could rely on one authority model without being tied to a single native AA design.

It also reframes recovery. Because the authority tree lives in public on-chain state, recovering an account becomes a matter of reading that state rather than restoring a wallet-side backup, and the standard is designed to complement the earlier ERC-8286 modular accounts work.

EIP-8141 is also making progress on the implementation side. The Rust client ethrex launched a public testnet built on Glamsterdam that runs EIP-8141 Frame Transactions alongside the rest of Ethereum’s privacy-roadmap EIPs, with its frames implementation matching the latest execution-spec tests.

Vitalik Links EIP-8141 to Ethereum’s Scaling Roadmap

Vitalik Buterin published a widely read note arguing that EIP-8141 is about far more than account abstraction. Recent work on transaction formats, he says, has given the ecosystem a clearer way to think about transactions in terms of “actions” and “dependencies,” which can then be optimized separately.

An action is an effect a transaction has, like a call that sends ETH, while a dependency is a fact that must be true for it to be valid, like a signature, a Merkle proof, or a ZK proof.

Separating them pays off in performance. Dependencies can be checked in parallel, and pure ones that touch no state can be verified once at the mempool and never re-run, or even replaced by a STARK so the underlying data can be dropped.

This is where a general-purpose transaction type comes in. EIP-8141 is a natural interface for expressing actions and dependencies as a minimal list of calls, letting Ethereum charge the lowest gas for the more static, analyzable work that makes up over 90% of activity.

His conclusion ties the threads together. Done well, he argues, EIP-8141 is both the culmination of ten years of account abstraction work and the groundwork for the next few years of scaling without sacrificing decentralization, combining Ethereum’s flexible execution model with more static approaches inspired by Bitcoin.

Base Vibenet Tests 200ms Blocks and Native AA

Base opened Vibenet, an ephemeral developer preview network, to test three ambitious upgrades at once before any of them reach mainnet. The headline features are 200-millisecond block preconfirmations, validity transactions, and native account abstraction.

The speed comes from a system called Flashblocks. Built with Flashbots, it delivers ten incremental state updates inside each two-second block, each arriving about 200 milliseconds after the last, and a later upgrade called Denim aims to turn those into full canonical 200ms blocks.

The account abstraction piece is the more consequential one for our readers. Vibenet runs EIP-8130, which bakes batching, gas sponsorship, and session keys into the protocol rather than layering them on through contracts, and Base reports simple USDC transfers costing roughly 63% less than the ERC-4337 equivalent.

The practical effect is familiar AA UX made cheaper and default. Apps can sponsor gas so users never need to hold ETH, and session keys let users pre-authorize actions for a set period without signing each one, all testable now through Vibenet’s faucet and explorer ahead of the September Cobalt upgrade.

Robinhood Chain’s Blobs Stop Reaching Ethereum

Robinhood Chain gave a useful lesson this week in how L2 data reaches Ethereum. The chain kept producing blocks roughly every 101 milliseconds, but the transaction data it posts to Ethereum as blobs stopped arriving for a total of 14 minutes across two separate gaps.

Arbitrum, whose stack Robinhood Chain uses, pointed to Ethereum’s blob market, which explains the second gap, when the blob fee rose above the poster’s standing bid. It does not explain the first and longer gap, when 263 blob slots sat unused at about a twelfth of that bid.

Context matters here. Robinhood Chain posts more blob data than any other network, between 28% and 45% of all Ethereum blobs, so it is unusually exposed to blob-market swings, and a surge of memecoin-driven traffic on Base had pushed blob demand and prices up.

The episode is a reminder of how an L2 can feel instant while its data availability on Ethereum quietly lags. Robinhood Chain’s single-sequencer setup with no public status page made the issue harder to observe from outside. It is a concrete example of how value and data move between an L2 and its settlement layer.

Start exploring Account Abstraction with Etherspot!

Learn more about account abstraction here.
Head to our docs and read all about Etherspot Modular SDK.
Skandha — developer-friendly Typescript ERC4337 Bundler.
Arka — an open-source Paymaster Service for gasless & sponsored transactions.
Explore our TransactionKit, a React library for fast & simple Web3 development.
Follow us on X (Twitter) and join our Discord.

❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/

Follow us

EIP-8141 nears Hegotá, composable native AA, Glamsterdam repricing, post-quantum ecrecover

Alexandra — Thu, 03 Sep 2026 08:54:57 +0000

Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.

This week: Ethereum core devs move EIP-8141 Frame Transactions toward inclusion in Hegotá as the L1 and L2 native AA camps converge; Pedro Gomes proposes splitting native account abstraction into three composable EIPs; Glamsterdam’s gas repricing exposes compatibility risks for some existing contracts and AA infrastructure; and a proposal to give ecrecover a post-quantum upgrade path.

EIP-8141 Advances Toward Hegotá Inclusion
A Composable Take on Native Account Abstraction
Glamsterdam Gas Changes Put AA Infrastructure to the Test
A Post-Quantum Upgrade Path for ecrecover

Please fasten your belts!

EIP-8141 Advances Toward Hegotá Inclusion

On All Core Developers Execution Сall #244, EIP-8141 Frame Transactions, the native account abstraction proposal, gained enough backing to move toward Scheduled for Inclusion (SFI) in Hegotá. Ethrex, Geth, Nethermind, and Besu all signaled support, a clear shift from a few weeks ago when native AA was only a candidate.

One important point: contributors clarified that this is consensus toward inclusion rather than a formally ratified decision, which still has to be recorded on a later call. Even so, the direction is now clear.

The bigger story is that the two approaches are starting to converge. EIP-8141, currently being considered for Ethereum L1, and EIP-8130, championed by Base and supported by parts of the L2 ecosystem, are being reconciled to avoid splitting Ethereum into two account models. A shared transaction type is the preferred outcome, with account interoperability, meaning the same account and address working across L1 and L2, as the fallback. Vitalik framed the two as points in one design space rather than competitors.

The call covered plenty beyond AA. Glamsterdam is entering adversarial testing on a large devnet with millions of validators and deliberate attack scenarios, ahead of proposed Glamsterdam activations on Sepolia on September 28 and Hoodi on October 26, with mainnet tentatively targeted for early December.

Developers also made history expiry a readiness requirement for Glamsterdam and kept narrowing Hegotá’s scope, with execution-client preferences due September 9 and FOCIL still the consensus-layer headliner. For a fork this large, the theme was managing risk and coordination as much as shipping features.

A Composable Take on Native Account Abstraction

WalletConnect’s Pedro Gomes published a proposal to break native account abstraction into three composable pieces rather than one large standard. The goal is to separate an account’s authority model from how transactions are actually carried, so chains can adopt the parts they want at their own pace.

The first piece, EIP-8398, defines a portable account keystore. It standardizes actors, authenticators, and account configuration so an account’s identity and permissions can move across chains independently of any single transaction format.

The second, EIP-8399, adds a basic native AA transaction type. It introduces a new transaction format with built-in batching, fee sponsorship, and keyed sequential nonces, using the keystore from the first EIP as its authority model.

The third, EIP-8400, layers on optional advanced controls like spending policies, account locking, and nonce-free transactions, all within the same transaction envelope. Base’s EIP-8130 stays unchanged, so this reads as an effort to modularize native AA and bridge the competing designs rather than replace them.

Glamsterdam Gas Changes Put AA Infrastructure to the Test

A closer look at Glamsterdam’s gas repricing shows a trade-off that matters for builders. Two proposals, EIP-8037 and EIP-8038, raise the cost of creating and touching state to support roughly three times more throughput, but they also change assumptions some deployed contracts were built on.

The new state charges are steep. Creating a new account would jump from 25,000 to about 183,600 gas, and a new storage slot from 20,000 to nearly 98,000, because these operations expand the state that every node has to store.

Researchers replayed about 930 million historical transactions against the new schedule. Most failures were fixable simply by allowing a higher gas limit, but a smaller group, roughly 2.7 million transaction replays under EIP-8037 and around 3 million under EIP-8038, remained in the potentially broken category.

The account abstraction angle is front and center. The outreach report flags the ERC-4337 EntryPoint and smart account stacks like Alchemy, ZeroDev, alongside protocols such as Across, CoW, and 0x, and warns that immutable contracts may need a new implementation and user migration rather than a simple config change.

The saving grace is timing. The proposals are still under review with a testing window open, so wallets, bundlers, indexers, and gas estimators can update before mainnet, and everyday users should be unaffected if that infrastructure keeps up.

A Post-Quantum Upgrade Path for ecrecover

Circle’s Mira Belenkiy floated a proposal to give ecrecover, the workhorse signature-checking function in countless Ethereum contracts, a post-quantum upgrade path. Rather than disabling it, the idea is to let ecrecover read post-quantum signatures carried in EIP-8141 frame transactions, triggered by a sentinel value in the usual signature fields.

The appeal is backward compatibility. A huge number of immutable, already-deployed contracts verify signatures through ecrecover, so a graceful path lets them keep working in a quantum world without redeployment, though the proposal explicitly does not try to fix EOA accounts themselves.

The thread also prompted some thoughtful pushback. One reviewer warned that adding a post-quantum path without retiring the old key is a downgrade risk, since an attacker who cracks the classical key could still spend through the unchanged path, so accounts also need a fail-closed cutoff. Another argued a clean new opcode would be better than overloading ecrecover.

The proposal is still early and remains under debate, with an EF researcher noting a preference for a deprecation path through EIP-8151. The discussion is a useful window into a quiet but important question: how Ethereum protects the enormous base of ecrecover-based code as post-quantum cryptography arrives, with Frame Transactions again at the center.

Start exploring Account Abstraction with Etherspot!

Learn more about account abstraction here.
Head to our docs and read all about Etherspot Modular SDK.
Skandha — developer-friendly Typescript ERC4337 Bundler.
Arka — an open-source Paymaster Service for gasless & sponsored transactions.
Explore our TransactionKit, a React library for fast & simple Web3 development.
Follow us on X (Twitter) and join our Discord.

❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/

Follow us

Base Backs EIP-8130, Ethereum Opens the Platåberget Testnet, Builders Debate Wallet Fragmentation, Nethermind Leaves LayerZero for Chainlink

Alexandra — Thu, 27 Aug 2026 09:05:45 +0000

Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.

This week: Base makes the case for EIP-8130 as a native account abstraction standard; the Ethereum Foundation opens the Platåberget testnet for Glamsterdam; builders debate whether native AA can solve wallet fragmentation; and Nethermind leaves its LayerZero verifier role for Chainlink.

Base Makes the Case for EIP-8130 Across the EVM
Ethereum Opens the Platåberget Testnet
Builders Debate Whether Native AA Can Fix Wallet Fragmentation
Nethermind Leaves LayerZero for Chainlink

Please fasten your belts!

Base Makes the Case for EIP-8130 Across the EVM

Base’s work on native account abstraction came back into focus last week as Chris Hunter made the case for EIP-8130 as a unifying account standard for the wider EVM ecosystem. The proposal is being developed with Optimism, Coinbase, and WalletConnect, with the goal of serving the different needs of L1, L2s, wallets, apps, and users without forcing every chain into the same implementation trade-offs. EIP-8130 is set to launch first on Base with the Cobalt upgrade this September, with other OP Stack chains expected to follow later in the year.

The pitch is that smart-account features stop being bolted on and become part of the protocol. EIP-8130 brings batching, gas sponsorship (including paying fees in any token), session keys, sub-accounts, transaction metadata, and portability, with the goal of making the same account usable across chains.

Efficiency is another part of the pitch. Compared with ERC-4337, Base reports a USDC transfer dropping from 125,000 to 46,000 gas, a 63% cut, with transaction size down more than 83%, because EIP-8130 was co-designed with the protocol rather than layered on top.

There is also a post-quantum angle. Native AA supports key rotation and multiple authentication schemes, giving users a path to upgrade to post-quantum authentication later, which fits the wider crypto-agility theme across Ethereum right now.

Existing accounts are not left behind. Plain EOAs automatically gain the new features, ERC-4337 smart accounts get a one-time upgrade path, and apps and wallets keep working as they do today, while Base tests everything on a new ephemeral devnet called Vibenet.

That said, EIP-8141 Frames remains a strong alternative, and the trade-offs between the two approaches, particularly around L2 performance, are still being debated. We’ll be watching how the discussion develops.

Ethereum Opens the Platåberget Testnet

The Ethereum Foundation launched Platåberget, an early public testnet for the upcoming Glamsterdam upgrade. Unlike the short-lived devnets before it, Platåberget is meant to run for a few months, so the community can experiment with post-Glamsterdam Ethereum and break things before the fork reaches Sepolia, Hoodi, and mainnet.

There is a blunt warning for builders. The upgrade’s gas repricing removes the hard-capped maximum gas limit, so any wallet, indexer, or gas estimator that assumes a fixed cap will break and needs updating.

Glamsterdam itself is a major hard fork. Highlights include enshrined proposer-builder separation (EIP-7732), block-level access lists (EIP-7928), a coordinated gas repricing toward a roughly 200 million gas floor, and much larger contract and initcode size limits.

One change matters directly for developers. A new state gas dimension means a plain ETH transfer is no longer always a flat 21,000 gas, since sending to an account that does not exist yet now incurs extra state gas at runtime. The testnet forked to Glamsterdam on August 20, with public validator and builder deposits open.

Builders Debate Whether Native AA Can Fix Wallet Fragmentation

A long thread in an AA builders’ Telegram chat this week wrestled with a stubborn question: will native account abstraction actually fix wallet fragmentation, or just move it around? The debate pulled in developers from across the ecosystem, along with Vitalik Buterin.

The starting worry was session keys and interoperability. One builder asked whether an app-defined permission, such as a scoped 15-minute session, could be authorised through one common interface across any wallet, or whether each wallet would keep whitelisting only its own implementation and recreate the fragmentation seen with EIP-7702. Others noted that permissions still have to live at the app layer, and that a shared default account for EOAs would likely cover only batching and gas abstraction, not full permissions.

A common thread ran through the practical pain. Developers described how EIP-7702 broke parts of existing integrations: once wallets began delegating users’ EOAs, some interactions started flowing through bundles, disrupting event tracking, points programs, and data attribution. Many users never understood what had changed when they upgraded.

Much of the discussion turned to incentives. Several builders argued that wallets are effectively loss leaders that earn through in-app swaps and order flow, which gives them little reason to let apps abstract them away, and some see that as the real driver of poor wallet UX. That framing strengthened the case for native AA, with some builders arguing that key-management primitives should be enshrined at the protocol level so accounts are not tied to a particular wallet or app.

Vitalik weighed in on a principle he cares about, that each user should keep exactly one master recovery root for their entire onchain life across Ethereum and its L2s. His reasoning is that one well-secured root can layer on social recovery, timelocks, multisig, and zk-email, whereas juggling several roots tends to leave each one weakly protected. Others pushed back that a single root is its own point of failure, and the debate stayed open.

Nethermind Leaves LayerZero for Chainlink

Nethermind, one of Ethereum’s core engineering firms and one of LayerZero’s largest third-party verifiers, is moving its cross-chain operations to Chainlink after what it called an extensive review. It is migrating its LayerZero Decentralized Verifier Network duties and joining Chainlink as a node operator to help secure CCIP and Data Feeds.

The move is part of a broader shift. Several firms have moved cross-chain operations from LayerZero to Chainlink since an April exploit on Kelp DAO’s rsETH bridge drained about $292 million from a LayerZero-powered bridge.

Nethermind framed it as an engineering commitment. The firm, which builds an execution client that now powers more than a third of Ethereum nodes, said it will bring that same reliability focus to running Chainlink infrastructure for institutional clients.

More broadly, the move points to a wider trend. As institutional onchain finance grows, cross-chain messaging is consolidating around a smaller set of security-focused providers, which shapes how value and data move between chains.

Start exploring Account Abstraction with Etherspot!

Learn more about account abstraction here.
Head to our docs and read all about Etherspot Modular SDK.
Skandha — developer-friendly Typescript ERC4337 Bundler.
Arka — an open-source Paymaster Service for gasless & sponsored transactions.
Explore our TransactionKit, a React library for fast & simple Web3 development.
Follow us on X (Twitter) and join our Discord.

❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/

Follow us

Native AA Delayed, ERC-4337 Gets a Reality Check, EOA Migration Debated, Ethereum Drops Poseidon

Alexandra — Thu, 20 Aug 2026 10:24:21 +0000

Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.

This week: core devs hold off on making native account abstraction a Hegotá headliner after L2 pushback; a ZeroDev founder publishes a three-part retrospective on what ERC-4337 actually delivered; builders in the AA Mafia group debate why EOA migration has been slow; and the Ethereum Foundation drops its Poseidon hash in favor of standard hashes.

Native AA Decision Delayed as L2s Raise Concerns
ERC-4337 Retrospective: What Worked and What Didn’t
Inside the AA Mafia’s EOA Migration Debate
Ethereum Rethinks Poseidon for Its Post-Quantum Future

Please fasten your belts!

Native AA Decision Delayed as L2s Raise Concerns

At All Core Developers Execution Call #243, developers finalized Glamsterdam’s gas repricing and moved its public testnet, Platåberget, forward, but the headline for us is what did not happen. A decision on making native account abstraction part of Hegotá was pushed back again.

Client support for EIP-8141 Frame Transactions, the native AA enabler, has actually grown. Nethermind now backs it and could champion it as a headliner, Geth contributors call it increasingly important for post-quantum readiness, and Besu raised no opposition.

The hesitation came from Layer 2s. Base and Arbitrum raised concerns about adopting Frames before the wider EVM ecosystem converges on one account model, warning it could fragment the stack if L1 and L2s head in different directions.

There is already a competing design in play. Base has implemented parts of EIP-8130, an alternative that adds programmable-account features like key rotation and cross-chain account sync without new EVM opcodes, while Frame Transactions supporters argue their approach can address the concerns through further specification work.

In its own Hegotá priorities paper, Ethlabs still ranks Frame Transactions as its preferred path to native account abstraction, and the proposal has advanced to “Considered for Inclusion.” Breakout calls resume on August 25, with a possible decision at the August 27 call.

ERC-4337 Retrospective: What Worked and What Didn’t

ZeroDev’s CTO, who led the development of the Kernel smart account, published a three-part retrospective following ERC-4337’s move to Final status. His blunt conclusion is that the standard succeeded, but not as the consumer-wallet revolution many expected.

Production told a narrower story. Across roughly 1.2 billion UserOperations, sponsored transactions made up the vast majority of volume, activity concentrated on a few deployments like World Chain and Base, and there was little sign of people migrating their main EOA into a standalone smart account. In practice, ERC-4337 became a shared rail for gasless and embedded flows rather than a mass account switch.

The Kernel history, from v1 to v4, sharpens the lesson. The capability that mattered most was not batching or sponsorship but replaceable validation, the idea that an account can outlive its key and swap in passkeys, recovery, or new signature schemes. Fine-grained permissions shipped as a “scalpel” but were mostly used as an on-switch, because the safe, narrow path was never the easiest one.

His third piece argues the real unlock is in-place migration. The unit that should change is the authorization model, not the address, so users keep their existing account while its root credential is replaced, which is exactly what EIP-7702 starts and native account abstraction would finish.

The hard part he flags is removing the old key completely. Even after delegation, the original ECDSA key can still authorize changes, and many apps still trust a raw signature through ecrecover, so a true transition has to fix both the protocol and the application layers.

Inside the AA Mafia’s EOA Migration Debate

A recent discussion among account abstraction builders in the AA Mafia Telegram group dug into a stubborn question: why has EIP-7702 adoption been slower than expected? The thread pulled in people from Base, the Ethereum Foundation, ZeroDev, Etherspot and Ambire, among others.

The raw numbers are not small. One participant shared 7702 activation counts from roughly a week earlier, led by Trust Wallet at over 640,000, MetaMask at around 280,000, and Pimlico’s Simple7702 account near 200,000, with many more behind them. Still, most of those wallets do not enable 7702 by default, so a large base of plain EOAs remains.

Builders disagreed on how to read this. A ZeroDev voice argued 7702 was designed for short-term EOA improvements and should be judged against the EOA transition rate rather than smart-account totals, while others worried Frame Transactions could hit the same slow adoption unless wallet teams commit to supporting them by default.

A recurring theme was that the root key is both the strength and the weakness. As an Ambire participant noted, 7702 users cannot lose funds the way pure smart accounts can, because a root key always exists, but that same key is also the vector behind most drains and blocks a clean migration.

Practical friction came up too, from delegated contracts not being available on every network to wallets restricting which chains can use 7702 and missing support for backend-triggered gasless flows. The takeaway echoes the retrospective above, that native AA needs the wallets and the packaging, not just the protocol.

Ethereum Rethinks Poseidon for Its Post-Quantum Future

The Ethereum Foundation is dropping Poseidon, the SNARK-friendly hash it had championed for years, from its plans for Ethereum’s base layer. According to researcher Justin Drake, future zero-knowledge designs will lean on standard hashes like SHA-2 or BLAKE instead.

The reversal comes from a research breakthrough. New proof systems that work over binary fields can now make ordinary, battle-tested hashes almost as efficient inside a SNARK as the specialized ones, flipping the goal from SNARK-friendly hashes to hash-friendly SNARKs.

The appeal is security through simplicity. Standard hashes have withstood decades of analysis, so relying on them avoids the risk of a newer, more exotic primitive being broken, and it removes the need to wait years for Poseidon to be battle-tested.

Drake tied the move to a rough stretch for fancier cryptography, noting that lattice-based and isogeny-based schemes have taken hits in recent weeks, a thread we covered last week. For account abstraction, the same instinct favors conservative, swappable cryptography, which is one reason native AA through Frame Transactions is being designed to let accounts change signature schemes as the field shifts.

Start exploring Account Abstraction with Etherspot!

Learn more about account abstraction here.
Head to our docs and read all about Etherspot Modular SDK.
Skandha — developer-friendly Typescript ERC4337 Bundler.
Arka — an open-source Paymaster Service for gasless & sponsored transactions.
Explore our TransactionKit, a React library for fast & simple Web3 development.
Follow us on X (Twitter) and join our Discord.

❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/

Follow us

MetaMask launches its agent wallet, Glamsterdam Testnet goes public, a lattice-crypto attack draws doubt, NEAR Intents unifies liquidity

Alexandra — Thu, 13 Aug 2026 09:42:21 +0000

Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.

This week: MetaMask launches a self-custodial wallet built for AI agents; Ethereum core devs send Glamsterdam to a public testnet while Frame Transactions pick up client support for Hegota; a new quantum attack on lattice-based cryptography draws quick skepticism; and NEAR Intents grows into a single cross-chain liquidity layer.

MetaMask Launches Its Agent Wallet
Glamsterdam Testnet Goes Public as Hegota Advances
A Lattice-Crypto Attack Draws Doubt
NEAR Intents Becomes a Unified Liquidity Layer

Please fasten your belts!

MetaMask Launches Its Agent Wallet

MetaMask launched its Agent Wallet, a self-custodial wallet built for AI agents to execute onchain actions inside rules the user sets. It lets traders and builders connect an agent framework, then define spend limits, allowlisted protocols, and a risk profile before the agent acts.

The pitch is that safety is the product. Agent Wallet is not blind delegation, so supported transactions pass through MetaMask’s security pipeline, including transaction simulation, Blockaid-powered threat scanning, and MEV protection, and anything outside policy pauses for two-factor approval.

Users pick between two modes. Guard Mode, the default, enforces daily spend limits, allowlists, and human approval for out-of-policy actions, while opt-in Beast Mode reduces approval interruptions but still runs security checks and still stops flagged transactions.

On capabilities, agents can connect frameworks like Claude Code, Codex, and Cursor and execute across HyperLiquid and EVM chains such as Robinhood and Monad. They can run ERC-7821 batch swaps, and they never need a chain’s native gas token, since MetaMask settles the fee in the token being moved.

This is account abstraction in a very practical form. Spend limits, allowlists, gasless execution, and batching are exactly the programmable account features that let an agent act autonomously without holding unchecked control of a wallet.

Glamsterdam Testnet Goes Public as Hegota Advances

During All Core Developers Consensus Call #184, developers decided Glamsterdam’s Devnet 8 will launch as a named, temporary public testnet, opening the upgrade to external validators and operators for the first time. They also closed the August 6 submission window for Hegota’s non-headliner proposals.

Closing the window does not mean approval. The submitted EIPs only entered a Proposed for Inclusion stage, where client teams will weigh their benefits, costs, and fit before any real inclusion decision, with FOCIL still the confirmed headliner for censorship resistance.

The new proposals widen Hegota’s possible scope. They include EIP-8198 (Quick Slots), which would cut slot time from 12 seconds to about 10, several networking upgrades built on PeerDAS, and EIP-8363, a contested tapered issuance burn that would push staking rewards toward zero as the staked share of ETH approaches half of supply.

The most relevant development for us happened around the call rather than in it. Nethermind announced that it has reviewed EIP-8141 Frame Transactions, contributed to the specification, completed an initial implementation, run a testnet, and now supports Frame Transactions as a Hegota headliner.

That matters because Frame Transactions are the native account abstraction enabler on Ethereum, the same primitive behind the trustless clear signing and modular Frame-Transaction accounts we covered recently. A major client team backing them as a headliner is a real step toward native AA landing in a future upgrade.

A Lattice-Crypto Attack Draws Doubt

A new paper on the IACR ePrint archive presented a fresh quantum cryptanalysis aimed at lattice-based cryptography, the math behind leading post-quantum schemes like Kyber and Dilithium. A working quantum attack on those foundations would be significant, since they are front-runners for securing systems, including Ethereum, against future quantum computers.

The claim drew fast skepticism. Quantum researcher Pierre-Luc Dallaire-Demers said the paper appears to contain several problems and broken theorems, and cryptographer Daniel J. Bernstein treated it cautiously, framing it as another bullet possibly dodged rather than a confirmed break.

The takeaway is not that lattice cryptography is broken. It is a reminder that post-quantum schemes are still young and under active attack, which is why cryptographers advise conservative parameters and keeping multiple independent approaches alive.

For Ethereum, the episode underlines why crypto-agility matters. One goal of native account abstraction through Frame Transactions (EIP-8141) is to make post-quantum signatures usable on Ethereum and to let accounts swap schemes as the field evolves, so no single algorithm becomes a permanent dependency.

NEAR Intents Becomes a Unified Liquidity Layer

NEAR is positioning NEAR Intents as a single liquidity and execution layer that the rest of crypto can route into. Its chain-abstraction system now spans 31 chains and more than 100 assets, with cross-chain settlement typically taking about 30 seconds.

The model changes what an app interface has to do. Instead of picking a bridge, switching networks, and arranging destination-chain gas, a user states the outcome they want, and competing solvers quote and execute the best route behind the scenes.

The target is liquidity fragmentation, the problem of the same assets being scattered across networks behind different wallets and bridges. A wallet or app that integrates Intents can offer access to assets on other chains without building every cross-chain route itself, through a widget or an API.

The numbers suggest it is past the experimental stage, with NEAR reporting more than $24 billion in cumulative Intents volume. As wallets, DeFi apps, and AI agents handle more transactions on their own, intent-based routing that hides the underlying chains fits neatly alongside the account-abstraction trend.

Start exploring Account Abstraction with Etherspot!

Learn more about account abstraction here.
Head to our docs and read all about Etherspot Modular SDK.
Skandha — developer-friendly Typescript ERC4337 Bundler.
Arka — an open-source Paymaster Service for gasless & sponsored transactions.
Explore our TransactionKit, a React library for fast & simple Web3 development.
Follow us on X (Twitter) and join our Discord.

❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/

Follow us

Glamsterdam nears its public testnet, Safe hits 130M smart account transactions, ERC-8286, 1inch opens Aqua

Alexandra — Thu, 06 Aug 2026 08:57:05 +0000

Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.

This week: Ethereum core devs name Glamsterdam's first public testnet and line up eight execution-layer EIPs for Hegotá; ERC-8286 lands as a module standard tying modular smart accounts to Frame Transactions; Safe reports a record quarter for smart accounts; an EF developer publishes a full architecture for trustless clear signing; and 1inch opens its Aqua shared-liquidity protocol across 13 chains.

Glamsterdam Moves Closer to Public Testing
ERC-8286 Extends Modular Accounts to Frame Transactions
Safe Smart Accounts Hit 130M Transactions in a Record Quarter
A New Model for Safer Ethereum Transactions
1inch Brings Wallet-Based Liquidity to 13 Chains

Please fasten your belts!

Glamsterdam Moves Closer to Public Testing

On All Core Developers Execution call #242, Ethereum developers gave Glamsterdam’s first public-facing testnet a name: Platåberget. They agreed to launch it only once the upgrade’s gas-repricing package is stable enough to avoid major specification changes, so the timing slipped even though the current devnet is running well.

Gas repricing is central to Glamsterdam because the upgrade is meant to prepare Ethereum for higher throughput and more parallel execution. Prices set too low would let attackers craft cheap but expensive-to-process blocks, while prices set too high would raise costs for ordinary apps, so the schedule has to land close to real computational cost.

Platåberget will be permissionless, launching with roughly 50,000 validators across about 50 nodes and a mix of client combinations. It will start in a pre-Glamsterdam state and activate the fork about a week after genesis, so clients and apps can rehearse a real upgrade transition from a populated chain.

The call also moved eight execution-layer EIPs into the Proposed for Hegotá stage for deeper review. Two stand out for account abstraction: EIP-7819 (SETDELEGATE) would make EIP-7702-style smart account deployment much cheaper than deploying proxy contracts, and EIP-7906 would expose a transaction’s state changes so wallets and contracts can verify that the result matches what was intended.

The theme is that Glamsterdam and Hegotá are now being built in parallel but are not independent. Several Hegotá proposals, including the cheaper account deployment, are calculated against Glamsterdam’s gas changes, so Glamsterdam has to stabilize first.

ERC-8286 Extends Modular Accounts to Frame Transactions
A new standard, ERC-8286, was merged into Ethereum’s ERC repository last week, though it was first drafted back in June. Titled “Modular Accounts for Frame Transactions,” it is co-authored by Chiranjeev Mishra, WalletConnect’s Pedro Gomes, and EF developer Alex Forshtat.

The proposal extends ERC-7579, the modular smart-account standard, to work with EIP-8141 Frame Transactions, the native account abstraction model that also underpins trustless clear signing.

The mechanics are deliberately minimal. Rather than defining a new module system, ERC-8286 reuses ERC-7579’s unchanged and adds only the validation flow that Frame Transactions need, where a validator returns an “approval mode” that the account applies during a verification frame.

The point is a portable module ecosystem. A validator, executor, or hook written once can work across different accounts, wallets, and account abstraction implementations, so builders do not have to fork their modules or get locked into a single standard like ERC-4337 or EIP-8141.

It is still an early-stage draft, but it is a meaningful piece of plumbing. It shows Frame Transactions maturing from a proposal into a standards stack that modular smart accounts can actually build on.

Safe Smart Accounts Hit 130M Transactions in a Record Quarter

Safe, the programmable smart account wallet, reported its biggest quarter yet. It processed nearly 130 million transactions in Q2 2026 and passed 63 million accounts created, a 20% increase year over year.

Usage stayed strong even as prices fell. Monthly active accounts reached 2.73 million in June, and by Safe’s own measure, about $1 of every $48 of global stablecoin supply now sits in a Safe account.

Not everything was up. Quarterly revenue fell roughly 30% to about $1.98 million, which Safe attributed to compressed crypto prices rather than slowing usage.

Most of the transaction volume came from consumer apps, with World App at 52% and Polymarket at nearly 36%. Safe also expanded Safenet, its new security layer that checks transactions in real time and can block value from leaving an account even if a user signs a malicious transaction, running over 455,000 checks by quarter’s end.

For our readers, the takeaway is simple. Smart accounts are no longer a niche, and one of the oldest smart account providers is now settling a meaningful share of onchain stablecoin activity.

A New Model for Safer Ethereum Transactions

EF developer Alex Forshtat, a co-author of ERC-4337, EIP-8141 and ERC-8286, published a detailed architecture for what he calls trustless clear signing. The goal is to move Ethereum away from blind signing, where users approve raw bytes and hope for the best, toward signing human-readable outcomes that are enforced on-chain.

The core problem he identifies is that a transaction’s inputs do not determine its outcome, since the result depends on mutable chain state. That gap has enabled many of the largest thefts in Ethereum’s history, because what a user signs and what actually happens can differ.

The key enabler is Frame Transactions, proposed in EIP-8141, which replace the single call frame with a multi-frame model. Adding a final post-transaction assertions frame lets the protocol inspect every state change after execution and atomically revert the whole transaction if the outcome does not match what the user approved.

The design stitches together several existing efforts. It uses EIP-7906 to see all state changes, ERC-7730 and storage-layout descriptors to translate raw storage slots into meaningful values like token balances, and an on-chain descriptor registry so wallets do not depend on a single data provider. Existing EOAs can opt in through EIP-7702.

The framing matters for where wallets are heading. Instead of approving calldata, a user would approve something closer to “receive at least X, spend no more than Y,” with the account rejecting anything outside those bounds, which Forshtat argues could prevent hundreds of millions in annual losses.

1inch Brings Wallet-Based Liquidity to 13 Chains

DEX aggregator 1inch opened Aqua, its shared-liquidity protocol, to 13 EVM-compatible chains. The idea is capital efficiency: liquidity providers keep their assets in their own wallets and let one balance back several positions at once, rather than splitting capital across separate pools.

Tokens stay in the provider’s wallet until a matching swap executes, and a trade simply fails if the balance cannot cover it. By 1inch’s example, a $100,000 balance could quote a combined $300,000 across three positions, which is quoted liquidity rather than extra capital.

The rollout answers a problem 1inch’s own research flagged. It found that most liquidity tracked across major concentrated-liquidity venues was sitting idle in the first half of 2026, missing out on an estimated $150 million in annual fees.

Supported chains include Ethereum, Base, BNB Chain, Arbitrum, and Robinhood Chain, and 1inch says Aqua passed eight independent audits. A roughly $1.37 million incentive program accompanies the launch, though providers still face impermanent loss and smart contract risk.

Start exploring Account Abstraction with Etherspot!

Learn more about account abstraction here.
Head to our docs and read all about Etherspot Modular SDK.
Skandha — developer-friendly Typescript ERC4337 Bundler.
Arka — an open-source Paymaster Service for gasless & sponsored transactions.
Explore our TransactionKit, a React library for fast & simple Web3 development.
Follow us on X (Twitter) and join our Discord.

❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/

Follow us