Compare
Four documents, the same five questions.
No throughput league table and no yield. The cells are what this library is willing to say about the text.
| Question | Account Abstraction Using Alt Mempool |
|---|---|
| What the text proposes | Smart-contract accounts that propose UserOperations, bundled by a separate mempool, without a change to Ethereum's consensus. Paymasters can sponsor gas. The validation rule lives in the account, which is the point and the risk. |
| Who may write | Vitalik Buterin, Yoav Weiss, Dror Tirosh, Shahaf Nacson, Alex Forshtat, Kristof Gazso and Tjaden Hess |
| What is settled | A UserOperation carries the sender, the call, and the signature-like data the account expects. |
| Load-bearing assumption | This is not consensus account abstraction. A node does not have to understand UserOperations. |
| What this library says afterwards | A paymaster can refuse, censor, or be empty. Sponsored gas is not a right. |
| Rights | Official external source only |