Account abstraction EIP-3074 has become a point of contention in the Ethereum community! Buterin throws out a new improvement plan EIP-7702

This site (120bTC.coM): Recently, there has been a lot of controversy in the Ethereum community regarding the account abstraction proposal EIP-3074 that will be included in Pectra upgrades in the future, including Vitalik and others. The opposition believes that it has doubts about future compatibility, so yesterday Vitalik directly proposed a new plan-EIP-7702.

Account Abstraction: Improving the blockchain user experience

Account Abstraction (AA) is Ethereum’s direction for improving the user experience in the blockchain interaction process. Account abstraction is It refers to optimizing the way users interact with the blockchain to make operations easier and more practical, hoping to usher in large-scale adoption.

How does account abstraction improve user experience? For example:

• Batch transaction: allows the same user to perform multiple operations in one atomic transaction. For example, on a decentralized exchange, users can complete approvals and transactions at the same time.

• Sponsored transaction: The third-party account can pay the transaction fuel fee on behalf of the transaction account, and can be used to subsidize the project for users.

• Permission management: Users can sign sub-keys and grant specific permissions. For example, users can give access to an ERC-20 token but not ETH, a maximum daily spending amount, or limit interaction with specific applications.

As important issues such as Ethereum network security and decentralization are gradually resolved, user experience proposals have gradually been put on the table for discussion recently. Proposals including EIP-2938, EIP-3074, EIP-4337, etc. are all key proposals.

ERC-4337 is regarded as the end game but has a long development cycle

EIP-4337 introduces the concept of User Operations, allowing smart contract wallets to customize transaction functions, such as sponsored transactions Or batch transactions.

User Operations will enter the alternative memory pool (alt mempool), which is a new memory pool created by EIP-4337, separated from the original general transaction and memory pool.

EIP-4337 Operational Structure

However, to implement ERC-4337 even to the point where it can be adopted on a large scale, a lot of effort is needed, including basic The design of the facility, manual updates of user wallets, and more.

EIP-3074's floating and sinking

EIP-3074 is expected to add two new opcodes (opcode): AUTH and AUTHCALL, allowing EOA to authorize contracts through these two opcodes (Invokers) call other external contracts and interactions on their behalf. That is to say, the current EOA has the function of smart contract.

Although EIP-3074 was proposed three years ago, the "final" perfect solution of EIP-4337 later appeared, making the former disappear from the community's view.

Recently, the importance of user experience has gradually increased, and competition from other public chains has gradually accelerated. However, a lot of development work is still required to implement EIP-4337 and operate it smoothly on the Ethereum main network. and resources. The Ethereum community believes that EIP-3074 should be implemented first.

EIP-3074 enables externally owned accounts (EOA) to operate like smart contract wallets. The process does not require the deployment of additional contracts and users do not need to manually upgrade. Therefore, the Ethereum community will include it in the next Hard fork upgrade in progress.

EIP-3074 continues to be controversial

Although it has been arranged to be upgraded to Pectra, the controversy over EIP-3074 is actually not small, and even Vitalik publicly opposed it.

EIP-3074 Dispute

Vitalik pointed out that EIP-3074 has compatibility issues with future updates:

• The two opcodes AUTH and AUTHCALL believes in Vitalik that the final account abstraction proposal EIP-4337 does not exist and is not needed.

• EIP-3074 The development of the caller contract ecosystem may become separate from the smart contract wallet ecosystem, resulting in technology fragmentation.

• In addition, community member Yoav Weiss pointed out that EIP-3074 requires full trust in the invokers contract, which increases trust risks and also requires the delay of the censorship-resistant Inclusion Lists mechanism.

Vitalik believes that EIP-3074 can be regarded as an expansion of EOA but not necessary. If it has a negative impact on the future development of Ethereum, then simply don’t do it.

The party supporting EIP-3074 said: "People who postpone or delete EIP-3074 often think that although the Ethereum user experience is not ideal, it is currently good." If there is no way to have it in the next Pectra update Significantly improving the user experience of Ethereum may lag behind other competitors.

The biggest controversial point of EIP-3074 is actually "Is EIP-4337 the most suitable ending for Ethereum?" If the answer is yes, then EIP-3074 should be opposed; if the answer is no, then it should be support.

However, the above discussion is too narrow and cannot resolve the community's dispute. Vitalik understands this truth and does not just talk about it but also directly implements new solutions. This allows the controversy of EIP-3074 to continue. Let the discussion continue.

Vitalik proposed that EIP-7702 is to replace EIP-3074

The design of EIP-7702 will replace the two operation codes AUTH and AUTHCALL required by EIP-3074 by calling EOA:

• AUTH will be replaced by calling verify, setting authorized[msg.sender,…]

• AUTH will be replaced by calling execute , verify authorized[msg.sender,…] and execute.

The content of the proposal indicates that these two small changes will avoid the potential negative impact of EIP-3074 on subsequent updates to the protocol.

The purpose of EIP-7702 is to implement all use cases of EIP-3074 without these two opcodes that may cause problems.

The future development of Ethereum may include EIP-7702?

Now there is a third solution besides simply supporting and opposing EIP-3074 - EIP-7702. If it can indeed solve "Ethereum needs a fast and effective user experience solution" and "do not affect the future" at the same time, The development process of EIP-4337 and other protocols may become a direction that the community has a consensus on.

The proposal is still under discussion, and you may be able to look forward to the next Ethereum ACDE meeting to get the latest progress.

But no matter what, the Ethereum community is still trying to progress in the best way, there is no doubt about this.

The above is the detailed content of Account abstraction EIP-3074 has become a point of contention in the Ethereum community! Buterin throws out a new improvement plan EIP-7702. For more information, please follow other related articles on the PHP Chinese website!