Loading prices…
🩸BEARISH

Ethereum L1 and Base Split Over Account Abstraction

The break could fragment EVM transaction standards and wallet UX as L1 security and privacy priorities diverge from L2 scalability and compliance goals.

Efforts to align EIP-8130 with EIP-8141's Frame Transactions broke down last week, Ethlabs researcher Derek Chiang said. Ethereum L1 and Base are now pursuing different account abstraction standards, although both target gasless transactions and passkeys.

Why it matters

The split reflects competing design priorities. Ethereum L1 places greater emphasis on censorship resistance, privacy and security. Base and other L2s prioritize scalability, configurability and compliance, creating different trade-offs for the same account abstraction goals.

Market impact

Chiang warned that the divergence could fragment EVM transaction standards and wallet UX. Developers and users could face different account flows across Ethereum and Base. Wallets and applications may eventually abstract away those differences, but that would leave separate standards beneath a simpler interface.

Related tokens
$ETH

Frequently asked questions

  1. What do EIP-8130 and EIP-8141 aim to enable?

    Both account abstraction standards aim to support gasless transactions and passkeys.

  2. How do Ethereum L1 and Base differ on priorities?

    Ethereum L1 emphasizes censorship resistance, privacy and security, while Base and other L2s prioritize scalability, configurability and compliance.

  3. What fragmentation risk did Derek Chiang identify?

    Chiang warned that separate paths could fragment EVM transaction standards and wallet UX.

  4. How could the split affect users on Ethereum and Base?

    Users could face different account flows and wallet experiences across the two chains, although wallets and applications may eventually abstract away the differences.

  5. Can wallets and applications hide the standards gap?

    They may eventually abstract away the differences across chains, but Ethereum L1 and Base would still be using separate account abstraction standards.

Source attribution
Aggregated from WuBlockchain · Verified · Last refreshed 1h ago
Open original →