My Publication
From EOAs to Smart Accounts EIP-7702 represents a major step toward widespread account abstraction, enabling users to enhance their Externally Owned Accounts (EOAs) with smart contract functionality. This hybrid approach combines the simplicity of EOAs with the programmability of contract-based accounts. In practice, it enables: Transaction batching, where multiple operations execute atomically within a single transaction. No more separate transactions for "approve" and "swap"! Gas sponsorship, which allows others to pay for transaction fees. This is especially useful when wanting to transact from an account that doesn't have ETH in it. Alternative authentication, which means many hardware security modules (HSMs) in phones today can be used to authorize operations for the account via technologies like passkeys. Spending controls, which can limit how many tokens a specific application can spend, or cap daily outflows from a wallet, improving security. Recovery mechanisms, which provide different options for users to safeguard their assets, without migrating to a new account. To use EIP-7702, an EOA signs an authorization pointing to a specific delegation address whose code it wants to execute. Once set, the account gains the new code’s capabilities (e.g., batching, sponsorship, authentication logic, etc.). Because choosing a delegation target hands over a great deal of control, EIP-7702 enforces several safety checks: Chain-specific delegations: by default, a delegation is only valid on a specific chain ID, preventing the same authorization from being used on different networks. Nonce-bound delegations: authorizations can be tied to the account's current nonce, automatically invalidating them once the nonce increases. Revocability: the owner of the EOA can always create another EIP-7702 authorization that revokes or replaces the existing delegation code, preventing a permanent lock-in if something goes wrong. For a deeper dive into how this all works, see @lightclient's Devcon talk on the topic.
My Publication
From EOAs to Smart Accounts EIP-7702 represents a major step toward widespread account abstraction, enabling users to enhance their Externally Owned Accounts (EOAs) with smart contract functionality. This hybrid approach combines the simplicity of EOAs with the programmability of contract-based accounts. In practice, it enables: Transaction batching, where multiple operations execute atomically within a single transaction. No more separate transactions for "approve" and "swap"! Gas sponsorship, which allows others to pay for transaction fees. This is especially useful when wanting to transact from an account that doesn't have ETH in it. Alternative authentication, which means many hardware security modules (HSMs) in phones today can be used to authorize operations for the account via technologies like passkeys. Spending controls, which can limit how many tokens a specific application can spend, or cap daily outflows from a wallet, improving security. Recovery mechanisms, which provide different options for users to safeguard their assets, without migrating to a new account. To use EIP-7702, an EOA signs an authorization pointing to a specific delegation address whose code it wants to execute. Once set, the account gains the new code’s capabilities (e.g., batching, sponsorship, authentication logic, etc.). Because choosing a delegation target hands over a great deal of control, EIP-7702 enforces several safety checks: Chain-specific delegations: by default, a delegation is only valid on a specific chain ID, preventing the same authorization from being used on different networks. Nonce-bound delegations: authorizations can be tied to the account's current nonce, automatically invalidating them once the nonce increases. Revocability: the owner of the EOA can always create another EIP-7702 authorization that revokes or replaces the existing delegation code, preventing a permanent lock-in if something goes wrong. For a deeper dive into how this all works, see @lightclient's Devcon talk on the topic.
