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.

Press enter or click to view image in full size

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.

🛠️ Builder note: Etherspot

AA infra should make development easier, not harder.

• One RPC endpoint across chains
• Pay-as-you-go pricing on mainnet
• No markup on gas fees
• API key controls with built-in security

👉 Learn more

Start exploring Account Abstraction with Etherspot!

• Learn more about account abstraction here.
• Head to our docs and read all about Etherspot Prime.
• 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 and join our Discord.

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

Follow us

Website | X | Discord | Telegram | Github | Developer Portal

Powered by Etherspot

TransactionKit | Pillar Wallet | Case Studies