Account Abstraction
Live on-chain usage, the proposal family, native-AA work, and related calls
Account Abstraction by Account Configuration
EIP-8130 is Base's native account-abstraction design and the L2 counterpart to EIP-8141. Instead of building AA into L1 consensus, it uses an account-configuration model with deterministic authenticators, needs no EVM changes, and is cross-chain portable. Core Devs set the default path as 8130 on L2s (Base, OP Stack, Arbitrum) and 8141 on L1, with convergence work ongoing, so the two are complementary layers rather than rivals.
How the model works
Account configuration model
A singleton account-config contract defines how an account authenticates, rather than deploying code to the account itself.
Deterministic authenticators
Native support for K1, P256, and passkey authenticators, declared top-level in the transaction so dependencies are inspectable without tracing.
2D & nonceless nonces
Two-dimensional nonces plus nonceless transactions for parallel and out-of-order flows.
No EVM changes
EOAs work out of the box, no protocol EVM changes required, and the model is cross-chain portable.
Adoption status
L2 path · Base, OP Stack, ArbitrumJul 2026
Base announces EIP-8130 (Account Abstraction by Account Configuration)
Aug 27, 2026
ACDE #244: default path set, 8130 proceeds on L2s and 8141 on L1
Late Sep 2026
Launch on Base; OP Stack and Arbitrum also committing
Ongoing
Timeboxed 8141 ↔ 8130 convergence; shared ERC-1979 key lifecycle
8130 and 8141: two layers, one goal
EIP-8130 · L2
Account-configuration model, no EVM changes, launching on Base and other rollups. Thesis: no capability gap versus 8141 at lower cost; authenticators declared top-level for inspectability.
EIP-8141 · L1
In-protocol Frames, SFI'd as the Hegota headliner. Coupled account model is the main point of debate; the two efforts share the ERC-1979 key-lifecycle standard and are attempting convergence.
Discussion & research
EIP-8130 ↔ ERC-1271 timelock PoC (lucadonnoh)
Community PoC exploring direct dispatch versus a locked ERC-1271 wallet, the kind of edge case the design discussion is working through.
Codeless-account constraints (CH / @_chunter)
Discussion of how default code for codeless accounts interacts with the ~65M existing smart accounts, passkey-only accounts, and custom-code accounts.
Links are community discussion and research, shared for context, not endorsements or security disclosures.
AI Disclaimer: Some content or metadata on EIPsInsight may be AI-inferred or automatically compiled. If you find any discrepancy, please contact us at dev@avarch.org.