<p>The Ethereum Account Abstraction roadmap kicked off in 2023 and has since become a prominent subject, especially with the recent <a href="https://twitter.com/TimBeiko/status/1778497101988835715?ref=bankless.ghost.io">announcement</a> of EIP-3074's inclusion in the upcoming Ethereum Hard fork (Pectra).</p><p>&nbsp;</p><p>This article explores how the Pectra upgrade aims to improve Ethereum wallet functionality and enhance the user experience, focusing on its major contributing EIPs: EIP-3074 and EIP-7702.</p><h1>What is Pectra Upgrade?</h1><p>The Ethereum Pectra upgrade, expected to be implemented in early 2025, is the next major improvement to the Ethereum Network. The main goals include increasing the maximum stake for validators, improving Ethereum Virtual Machine (EVM) efficiency, and potentially introducing user experience enhancements for wallets.</p><p>As a web3 enthusiast, you may have heard a lot about <a href="https://www.buildbear.io/resources/guides-and-tutorials/Simplifying_Account_Abstraction">Account Abstraction</a>. Let’s explore how this concept is set to improve wallet functionality.</p><h1>Understanding Account Abstraction</h1><p>Most of the time, account abstraction simply means smart contracts that can do more than traditional Externally Owned Accounts. EOAs on Ethereum are controlled by private keys and can initiate transactions by signing them.</p><p>However, as our needs evolved, we required a system to handle complex transactions, which isn't possible with normal wallets. With problems come great solutions, right? This led to the development of Smart Contract Accounts (SCAs), which are programmatically controlled accounts within the Ethereum network that execute actions based on predefined logic.</p><p>&nbsp;</p><figure class="image image_resized" style="width:50%;"><img src="https://strapi.buildbear.io/uploads/account_286fb8e09c.jpg" alt="account.jpg" srcset="https://strapi.buildbear.io/uploads/thumbnail_account_286fb8e09c.jpg 224w,https://strapi.buildbear.io/uploads/small_account_286fb8e09c.jpg 500w,https://strapi.buildbear.io/uploads/medium_account_286fb8e09c.jpg 750w,https://strapi.buildbear.io/uploads/large_account_286fb8e09c.jpg 1000w," sizes="100vw"></figure><p>&nbsp;</p><p>Here is a quick comparison between Externally Owned Accounts (EOA) and Smart Contract Accounts (SCA) in Ethereum:</p><p>&nbsp;</p><figure class="table"><table><thead><tr><th>Feature</th><th>EOA</th><th>SCA</th></tr></thead><tbody><tr><td><strong>Control Mechanism</strong></td><td>Controlled by private keys</td><td>Governed by smart contract code</td></tr><tr><td><strong>Transaction Initiation</strong></td><td>Signing with a private key</td><td>Executes actions in response to messages or calls</td></tr><tr><td><strong>Flexibility</strong></td><td>Limited to basic transactions</td><td>Programmable flexibility enabling dynamic behaviors and updates</td></tr><tr><td><strong>Security</strong></td><td>Security relies on private key management</td><td>Requires careful contract design and testing to avoid vulnerabilities</td></tr><tr><td><strong>Meta Transactions</strong></td><td>Not natively supported</td><td>Can support meta-transactions, allowing gas fees to be paid by a third-party</td></tr><tr><td><strong>Functionality</strong></td><td>Direct control, limited in functionality</td><td>Capable of batching multiple actions into a single transaction</td></tr><tr><td><strong>Use Cases</strong></td><td>Ideal for individual ownership and basic transactions</td><td>Essential for complex decentralized applications and automated processes</td></tr></tbody></table></figure><p>&nbsp;</p><p><strong>So, what exactly is Account Abstraction? </strong>It aims to integrate the functionalities of both EOAs and SCAs, allowing for easier interaction in web3.</p><p>&nbsp;</p><p><strong>What are the Benefits of Account Abstraction?</strong></p><ul><li>Simplifies the interaction process, making it more user-friendly, especially for newcomers.</li><li>Allows smart contracts to initiate and control transactions on behalf of EOAs without exposing or managing private keys.</li><li>Minimizes risks associated with key management and enables advanced transaction types and conditional logic.</li></ul><p>&nbsp;</p><p>There were multiple attempts to achieve Account Abstraction and a significant adoption rate as shown below. Let us analyze the EIPs related to AA and how far they have succeeded.</p><p>&nbsp;</p><figure class="image image_resized" style="width:75%;"><img src="https://strapi.buildbear.io/uploads/Untitled_11_10c97a8dec.png" alt="Untitled (11).png" srcset="https://strapi.buildbear.io/uploads/thumbnail_Untitled_11_10c97a8dec.png 245w,https://strapi.buildbear.io/uploads/small_Untitled_11_10c97a8dec.png 500w,https://strapi.buildbear.io/uploads/medium_Untitled_11_10c97a8dec.png 750w,https://strapi.buildbear.io/uploads/large_Untitled_11_10c97a8dec.png 1000w," sizes="100vw"><figcaption><strong>Account abstraction in numbers </strong>Source: <a href="https://dune.com/niftytable/account-abstraction?ref=blog.quicknode.com"><code>Dune Analytics</code></a></figcaption></figure><h1>Future of Account Abstraction: ERC-4337 and Beyond</h1><p><a href="https://eips.ethereum.org/EIPS/eip-4337">ERC-4337</a> supports a wide range of features typically unavailable to EOAs, such as paying gas fees in tokens other than ETH, complex account recovery mechanisms, and more advanced transaction batching and scheduling functionalities. This indeed had numerous user experience improvements.</p><p>&nbsp;</p><p>However, EOAs are still the most commonly used type of account used via Metamask Wallets. Most 4337 smart contract accounts are controlled by a single EOA signer due to the lack of a way to convert EOA to a smart contract account and the lack of native support by web3 apps to connect smart contract accounts.</p><p>&nbsp;</p><p>These issues are addressed by EIP-3074, which aims to give EOAs more power by allowing them to delegate control of their EOA to a smart contract. This is a step towards moving existing users from EOAs to smart contract accounts. Additionally, <a href="https://eips.ethereum.org/EIPS/eip-5003?ref=bankless.ghost.io">EIP-5003</a> proposes a method for permanently transitioning from an EOA to an SCA. This would allow EOAs to delegate transaction execution authority to SCAs permanently.</p><h1>What is EIP-3074: Contributions to Account Abstraction</h1><p><a href="https://github.com/ethereum/EIPs/blob/master/EIPS/eip-3074.md">EIP-3074</a> introduces new Ethereum opcodes and functionalities that empower smart contracts to interact with EOAs securely and controlled.</p><p>It primarily solves the limitations of traditional wallets like Trust Wallet. How? Traditional wallets, which are externally owned accounts (EOAs), are integrated with smart contracts using&nbsp;account abstraction&nbsp;for a smoother user experience.</p><p>&nbsp;</p><h2>How does EIP-3074 work?</h2><p>The <strong>EIP-3074</strong> adds new opcodes to the Ethereum Virtual Machine:&nbsp;<code>AUTH</code>&nbsp;and&nbsp;<code>AUTHCALL</code>.</p><p>&nbsp;</p><ul style="list-style-type:disc;"><li><strong>AUTH</strong>: This command lets users authorize a smart contract to act on their behalf. It uses a special digital signature (ECDSA) to verify that the user has given permission. Once verified, the user’s address is stored in a special variable.</li><li><strong>AUTHCALL</strong>: This command allows the authorized smart contract to perform transactions on behalf of the user. It can send transactions to other addresses, specify amounts, and include data, just like a regular transaction.</li></ul><p>&nbsp;</p><figure class="image image_resized" style="width:75%;"><img src="https://strapi.buildbear.io/uploads/Untitled_12_bd94f7ebd4.png" alt="Untitled (12).png" srcset="https://strapi.buildbear.io/uploads/thumbnail_Untitled_12_bd94f7ebd4.png 245w,https://strapi.buildbear.io/uploads/small_Untitled_12_bd94f7ebd4.png 500w,https://strapi.buildbear.io/uploads/medium_Untitled_12_bd94f7ebd4.png 750w,https://strapi.buildbear.io/uploads/large_Untitled_12_bd94f7ebd4.png 1000w," sizes="100vw"><figcaption>Image from <a href="https://x.com/jarrodWattsDev/status/1788119063325290711/photo/1"><code>https://x.com/jarrodWattsDev/status/1788119063325290711/photo/1</code></a></figcaption></figure><p>&nbsp;</p><p>Imagine you want to swap 10 DAI for ETH. Instead of signing multiple transactions, you authorize(AUTH) the Invoker with one signature. The invoker will:</p><ul><li>Uses <strong>AUTHCALL</strong> to approve Uniswap to spend your DAI.</li><li>Immediately uses <strong>AUTHCALL</strong> again to execute the swap of DAI for ETH.</li></ul><h1>Key Benefits with EIP-3074</h1><h2>EOA Control Delegation</h2><p>The new opcodes effectively delegate control of an EOA to a smart contract, expanding its capabilities without the need for deploying additional contracts. By delegating transaction execution to SCAs, EIP-3074 reduces the exposure of private keys. Malicious invokers are prevented from directly accessing EOAs' funds, mitigating the risk of unauthorized transactions.</p><h2>Impact on Sponsored Transactions</h2><p>The third-party sponsor can provide the necessary gas fees and submit the transaction to the Ethereum network on behalf of the user. So the user only needs to sign the transaction without needing to pay the required gas fees on their end.</p><h2>User Experience Improvements</h2><p>Users can now interact with decentralized applications (dApps) more efficiently, with EOAs gaining capabilities of smart contract wallets. This simplifies transaction processes and reduces the complexity associated with blockchain transaction execution.</p><h2>Batch Transaction</h2><p>EIP-3074 allows for batching transactions by grouping all individual transactions and executing them using smart contracts with a single signing. This feature saves gas fees, time, and effort.</p><h1>Challenges and Considerations</h1><p>While EIP-3074 brings significant advancements to Ethereum's Account Abstraction capabilities, it also presents challenges:</p><ul><li><strong>Malicious Invoker Risks:</strong> Delegation of EOA control to SCAs introduces risks of malicious invokers attempting unauthorized transactions.</li><li><strong>Temporary Delegation:</strong> AUTH requires the nonce in the message to be equal to the signer's current nonce, invalidating outstanding authorizations with a single EOA transaction.</li><li><strong>Ether Spending Limitations:</strong> EOAs under EIP-3074's control may have limitations on spending Ether directly.</li><li><strong>Self-Sponsoring Impact:</strong> Self-sponsoring transactions by SCAs could potentially circumvent certain security measures, such as flash loan protections.</li></ul><p>&nbsp;</p><h1>The Emergence of EIP-7702</h1><p>Vitalik Buterin proposes an advanced version of EIP3074 called <a href="https://ethereum-magicians.org/t/eip-7702-set-eoa-account-code-for-one-transaction/19923">EIP-7702</a>, adding a new transaction type that accepts both a <code>contract_code</code> and a <code>signature</code> field. This allows for the temporary delegation of an EOA to a smart contract during a transaction.</p><h2>How EIP-7702 Works:</h2><p>EIP-7702 lets an Externally Owned Account (EOA) temporarily act like a smart contract for a single transaction:</p><p>&nbsp;</p><ol style="list-style-type:lower-roman;"><li><strong>contract_code</strong>: The smart contract logic to be temporarily assigned to the EOA for the transaction.</li><li><strong>signature</strong>: The ECDSA signature authorizing the use of the smart contract code.</li></ol><p>&nbsp;</p><p>For example, if you want to perform a token swap and stake the resulting tokens in a single transaction, EIP-7702 allows your EOA to include the smart contract logic in the <code>contract_code</code> field and an ECDSA signature in the transaction. Once validated, the network temporarily treats the EOA as a smart contract, executing the provided <code>contract_code</code> to perform the swap and stake actions in one go.</p><h1>Key Benefits of EIP-7702</h1><h2>Trustless Execution</h2><p>EIP-7702 eliminates the need for a trusted invoker, reducing the risk of malicious actions. No need for a central party to carry out transactions, reducing security risks associated with external invokers.</p><h2>Simplified Complex Transactions</h2><p>Users can perform complex transactions in a single step, like token swaps and staking, in one transaction, enhancing user experience by reducing complexity.</p><h2>Future-Proof Compatibility</h2><p>Fully compatible with ERC-4337 and future Account Abstraction proposals, ensuring smooth integration and adaptability to upcoming changes in the Ethereum ecosystem.</p><p>To wrap it up here is a brief comparison of these EIPs of AA.</p><p>&nbsp;</p><figure class="table"><table><thead><tr><th>EIP-3074</th><th>EIP-7702</th></tr></thead><tbody><tr><td>Introduces two new opcodes, AUTH and AUTHCALL.</td><td>Introduces a new transaction type named user_operation.</td></tr><tr><td>Not compatible with account abstraction’s future.</td><td>Compatible with future implementations of AA.</td></tr><tr><td>Assigns EOA’s control to the smart contract code.</td><td>Smart contract code is added to the EOA address.</td></tr><tr><td>Reduces private key exposure but needs invoker</td><td>Completely trustless, no central point of trust</td></tr></tbody></table></figure><p>&nbsp;</p><h1>Conclusion</h1><p>Account Abstraction is about making the blockchain more accessible and versatile by taking away the complexity involved in transaction initiation and execution. EIP-3074, along with EIP-7702, represents significant advancements in Account Abstraction, potentially transforming how users interact with web3 applications and enhancing the overall user experience in the web3 ecosystem.</p><h1 style="margin-left:0px;">About BuildBear:</h1><p style="margin-left:0px;"><a href="https://www.buildbear.io/">BuildBear</a>&nbsp;is a platform tailored for DApp development and testing. Developers gain the freedom to construct a personalized Private Testnet sandbox across a variety of blockchain networks. The liberty to mint unlimited Native and ERC20 tokens, coupled with rapid transaction times on BuildBear (under 3 seconds!), enhances the DApp development lifecycle manifold. The platform comes equipped with tools and plugins designed for real-time testing and debugging, ensuring developers can keep tabs on intricate blockchain transactions with unparalleled ease.</p><p style="margin-left:0px;"><strong>Connect with us on</strong>&nbsp;<a href="https://twitter.com/_BuildBear">Twitter</a>&nbsp;|&nbsp;<a href="https://www.linkedin.com/company/build-bear/">LinkedIn</a>&nbsp;|&nbsp;<a href="https://t.me/Web3_dApp_Developers">Telegram</a>&nbsp;|&nbsp;<a href="https://github.com/BuildBearLabs">GitHub</a></p><p style="margin-left:0px;"><strong>Author</strong>: <a href="https://www.linkedin.com/in/sanamummer/">Sana</a></p>

Screenshot from 2024-07-26 10-40-21.png

The Ethereum Account Abstraction roadmap kicked off in 2023 and has since become a prominent subject, especially with the recent announcement of EIP-3074's inclusion in the upcoming Ethereum Hard fork (Pectra).

This article explores how the Pectra upgrade aims to improve Ethereum wallet functionality and enhance the user experience, focusing on its major contributing EIPs: EIP-3074 and EIP-7702.

EIP-3074 and EIP-7702: A New Era to Account Abstraction

BUILDBEAR // BLOGS

EIP-3074 and EIP-7702: A New Era to Account Abstraction

Let’s get started then, Shall we?

Let’s get started then, Shall we?

Test DApps at Scale.