ERC-4337 vs. ICP Native Account Abstraction: Why ICP Never Needed a Wallet Upgrade
The Ethereum community spent years trying to solve the poor user experience of seed phrases, gas management, and private key losses through ERC-4337. Meanwhile, the Internet Computer was architected from day one with native account abstraction. Here is a deep technical look at why.
1. The Ethereum Problem: The EOA Legacy
In Ethereum, accounts are split into Externally Owned Accounts (EOAs) and Contract Accounts. EOAs can initiate transactions but cannot execute logic, recovery rules, or sponsorship without complex relays. ERC-4337 introduces an "alt-mempool" with:
- UserOperations: Pseudo-transactions submitted to separate relays.
- Bundlers: Specialized MEV actors who package UserOperations.
- Paymasters: Custom contracts that sponsor gas fees.
2. How ICP Solved It at Genesis
On the Internet Computer, there are no EOAs:
Every caller is a cryptographic Principal. The protocol natively supports WebAuthn (FIDO2) signatures without requiring extra gas-heavy smart contract verifier libraries.
Every canister pays its own cycles. There is no need for complex "Paymaster" contracts or secondary mempools.
