DEV Community

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

Posted on Originally published at etherspot.io

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

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.

Vitalik Links EIP-8141 to Ethereum’s Scaling Roadmap

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

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

Top comments (0)