Account abstraction is easy… unless you care about censorship resistance
summary
ERC 4337 implements account abstraction but adds concrete, nonobvious rules to keep relayer networks censorship resistant: it splits each request into validation vs execution, enforces a small validation gas limit, bans environment opcodes that break determinism, restricts validation storage access so validators can’t be mass‑invalidated, and requires bundlers to pass compatibility tests, reference implementation and fuzzing. Paymasters use staking with an unstake delay to raise the cost of griefing. The result is a permissionless bundler/mempool design that protects liveness and economic incentives.
AI-written summary · about
chapters (9)
- 0:00Account abstraction basics
- 1:29Centralized relayer problems
- 4:15Gas Station Network limits
- 7:28ERC 4337 censorship resistance
- 8:55ERC 4337 design challenges
- 13:32Global DoS risks
- 15:23Bundler rule enforcement
- 17:32Multi-client robustness
- 18:56Conclusion
related talks
19mBeyond the Blacklist, The Compliant Way To Do Private Transactions
21mDEX Aggregation Is Harder Than You Think
28mPaying for Privacy Preserving Messaging
21mPrivacy and Compliance - A pragmatic approach
01h 24mPseudonymity, Automation, and Responsibility on Public, Permissionless Blockchains under the GDPR
31mPrivacy-preserving smart contracts
58mBlockchains and Publicly-Verifiable Lotteries
20mArbitrum: Scalable, private smart contracts