Why is Vitalik in a hurry to propose the new account abstraction proposal EIP-7002?
TechFlow Selected TechFlow Selected
Why is Vitalik in a hurry to propose the new account abstraction proposal EIP-7002?
This is a solution between ERC-4337 and EIP-3074.
Navigating Web3 tides with focused insightsAuthor: 0XNATALIE
EIP-3074 was included in Ethereum's next hard fork plan in April this year. This proposal aims to improve user experience by allowing externally owned accounts (EOAs) to delegate transaction privileges to smart contracts. However, this functionality has raised concerns within the community, as many worry that misuse of signatures could expose entire account funds to risk and create opportunities for phishing attacks. To further enhance security, Vitalik Buterin recently proposed EIP-7702 as an alternative to EIP-3074, sparking widespread discussion.
EIP-7702 introduces a new transaction type to enhance account abstraction capabilities. This new transaction type allows externally owned accounts (EOAs) to temporarily adopt smart contract functionalities during a transaction, then revert back to their original state afterward. So what exactly differentiates these three account abstraction proposals—ERC-4337, EIP-3074, and EIP-7702?
ERC-4337: Application-Layer Account Abstraction Standard
ERC-4337: Implements account abstraction using an alternative mempool (Alt Mempool). Proposed by Vitalik, ERC-4337 is an application-layer standard whose primary goal is to enable smart contract accounts to initiate transactions proactively like EOAs. It introduces a smart contract called EntryPoint, enabling smart contracts to function as user accounts—meaning users can manage assets and transactions through contract-like accounts. This allows for complex logic such as multi-signature setups and automatic transaction execution.
Key Features:
-
No Hard Fork Required: ERC-4337 does not require a hard fork or any changes to the Ethereum protocol.
-
Compatibility: This approach is compatible with the existing EOA system, enabling a smoother transition.
-
Objective: Achieve account abstraction so that smart contracts can handle and validate transactions like accounts.
-
Nature: Enables smart contract accounts to initiate transactions proactively like EOAs.
EIP-3074: Authorization and Proxy Execution
EIP-3074: Introduces the AUTH and AUTHCALL opcodes. Proposed by Ethereum researchers including Sam Wilson and Go Ethereum developer Matt Garnett—with no involvement from Vitalik in drafting—the proposal enables EOAs to delegate privileges to smart contracts. It introduces two new opcodes: AUTH and AUTHCALL, allowing smart contracts to perform actions on behalf of EOAs, such as batch processing transactions or sponsoring gas fees. This represents a significant change to Ethereum’s virtual machine.
Key Features:
-
Delegation Mechanism: An EOA can authorize a smart contract via the AUTH opcode, then use AUTHCALL to let the contract act on its behalf.
-
Security Risks: The delegation mechanism may lead to security issues—if authorization is granted to a malicious contract, it could result in fund theft.
-
Objective: Enhance EOA functionality by allowing temporary delegation of privileges to smart contracts.
-
Nature: Upgrades the EVM by adding two new opcodes.
EIP-7702: Temporarily Smart Contract-Enabled EOAs
EIP-7702: Sets contract code for an EOA within a single transaction. First-authored by Vitalik and newly published on May 7, EIP-7702 serves as an alternative to EIP-3074. It introduces a mechanism allowing EOAs to temporarily gain smart contract capabilities during a transaction. With this method, an EOA can transform into a smart contract wallet for the duration of one transaction and revert to its normal state afterward. Moreover, since EIP-7702 already provides a framework for temporarily modifying EOA code, implementing EIP-5003 (which allows EOAs to permanently become smart contract accounts) becomes relatively straightforward—by simply not clearing the code after the transaction, permanent conversion from EOA to smart contract is achievable.
Key Features:
-
Temporary Conversion: During a transaction, an EOA is temporarily endowed with smart contract code to perform specific operations.
-
High Compatibility: EIP-7702 is highly compatible with ERC-4337 smart contract wallet code. It can directly reuse existing smart contract code written and deployed for ERC-4337, enabling reuse of current account abstraction efforts and avoiding fragmentation of the account ecosystem.
-
No New Opcodes Required: Unlike EIP-3074, although EIP-7702 is also a protocol-level standard, it applies smart contract code temporarily within transactions without requiring permanent changes to the Ethereum Virtual Machine.
-
Objective: Combine advantages of EIP-3074 and ERC-4337 to provide a more flexible and compatible account abstraction solution.
-
Nature: Temporarily applies smart contract code.
EIP-7702 offers a way to achieve EIP-3074-like functionality without introducing new opcodes, while better preparing for the endgame of account abstraction. The "endgame of account abstraction" refers to a future vision where all accounts on Ethereum use smart contract wallets to manage assets and transactions, eliminating reliance on traditional EOAs. This universal adoption of smart contract wallets is known as the "endgame" of account abstraction. EIP-7702 not only addresses current challenges but also ensures long-term effectiveness and practicality through compatibility with potential future account models.
Join TechFlow official community to stay tuned
Telegram:https://t.me/TechFlowDaily
X (Twitter):https://x.com/TechFlowPost
X (Twitter) EN:https://x.com/BlockFlow_News
@ChainFeedsxyz
