Read the proposal: ethereum-magicians.org/t/erc…

Etherspot explains: ERC-8421 Frame Transaction Alternative Mempools EIP-8141 Frame Transactions need mempool rules that protect the network from spam while supporting different types of accounts and applications. ERC-8421 proposes a more permissive, reputation-based alternative to the stricter canonical mempool defined in the core protocol. Its rules follow the structure of ERC-7562, already used for ERC-4337 UserOperations, and are mostly backward compatible with them. The proposal allows staked senders in good standing to submit transactions without a per-sender transaction-count cap. This matters for privacy applications, where many users can share one sender address and a fixed cap could limit activity across all of them. It also accounts for EIP-8250 transactions carrying multiple nonce keys, so the mempool rules can handle transactions that use more than one key. ERC-8421 takes a similar approach to MATCHA, another reputation-based mempool proposal. The main difference is how activity is measured: ERC-8421 counts transactions seen, while MATCHA measures gas used. Together, these rules aim to give applications more flexibility in how their transactions enter the network, while retaining reputation-based protections against abuse.

Native transaction assertions add an outcome check to the transaction. If the final state doesn’t match the user’s conditions, the transaction reverts. Read more 👇

This week's highlights: - Native transaction assertions target blind signing - @drakefjustin calls for “bunker mode” - EEZ tests an atomic L1-to-L2 transaction - Frames Devnet-1 expands its scope Read the full digest👇 go.etherspot.io/R3lg8E6

For teams building on ERC-4337, Skandha covers the practical pieces: EIP-7702, latest EntryPoint versions, Shared Mempool, built-in MEV protection, and multi-chain support.

ERC-8421 proposes reputation-based rules for Frame Transactions, enabling more flexible shared-sender flows than the canonical mempool currently allows. Read more in the latest AA digest 👇

This week's highlights: - ERC-8421 alternative mempools for Frames @forshtat - Post-quantum signature challenge by @YukonResearch @ethereumfndn - @zk_money returns on @aztecnetwork - @lex_node on an Ethereum privacy push Read more👇go.etherspot.io/bJLcOre

A lot of the smart account experience depends on infrastructure users will never see. Bundlers are a good example: they stay behind the scenes, but their reliability affects the transaction experience. Explore Skandha, our open-source ERC-4337 bundler trusted by builders across the ecosystem 👇go.etherspot.io/bzv6DVY

Frame Transactions are moving from design to implementation. The testnet now runs across three clients, while supporting EIPs advance for Hegotá. Read more in the latest digest 👇

This week's highlights: - Frame Transactions clear a testnet milestone - ERC-8427 defines portable spend grants - @safeLabs_ makes contracts v1.5.0 the default - @Arbitrum launches Priority Gas Auctions Read the full digest👇go.etherspot.io/Sr4ekUN

A new transaction model is only part of native account abstraction. ERC-8403 looks at another piece: how account authorities are managed 👇

MATCHA looks at how native account abstraction can support more flexible transactions while keeping mempool risks in check. Read more in the latest AA digest 👇

This week's highlights: - EIP-8411 tests sub-second block propagation - @ethlabs_org pitches a faster Ethereum as Base Splits on AA - Glamsterdam clears its 200M gas rehearsal - MATCHA explores private frames in the public mempool Read more👇go.etherspot.io/xBpGgTy

Learn more: ethereum-magicians.org/t/erc…

Etherspot explains: ERC-8403 Account Authority Lifecycle Native account abstraction needs a common way to manage the authorities that can act on behalf of an account. ERC-8403 introduces a common lifecycle for account authorities, including signing keys and rules like spending limits or locks. It covers how they can be added, rotated, and revoked. Each account keeps a verifiable set of approved keys and rules. A transaction includes proof that the authority it uses belongs to that set, and the account checks it before authorizing the action. The proposal is designed to work with both EIP-8141 Frame Transactions and the EIP-8130 keystore approach, giving wallets and apps one authority model across different native AA implementations. It can also make recovery more portable, since authority data can be reconstructed from on-chain state instead of relying only on wallet-side backups. ERC-8403 complements ERC-8286, which focuses on modular account validation.

Ethereum and Base tried to align their native account abstraction approaches. Now they’re moving forward separately. More in this week’s digest 👇

This week's highlights: - Ethereum commits to EIP-8141 for Hegotá - Base and Ethereum split on native AA, says @decentrek - @the_matter_labs’s Prividium is tested by the Bundesbank - @a16zcrypto makes the case for permissionless compliance Read more 👇 go.etherspot.io/5sba2eZ

Good Web3 UX means users shouldn’t have to think about infrastructure details like gas with every action. Arka helps keep that complexity in the background 👇

EIP-8141 may end up mattering for much more than account abstraction. Vitalik argues that separating transaction actions from dependencies could open up more parallel processing and help Ethereum scale more efficiently. More in this week’s AA digest 👇

This week's highlights: - ERC-8403 standardizes the account authority lifecycle - Vitalik links EIP-8141 to Ethereum's scaling roadmap - @Base Vibenet tests 200ms blocks and native AA - @RobinhoodCrypto blobs stop reaching Ethereum Read the full digest👇go.etherspot.io/xY3x8CD