【English】Discussing the impact of EIP-3074 inclusion and potential alternatives

Chainfeeds Introduction:

Previously, EIP-3074 was confirmed to be included in the Prague upgrade to improve user experience. However, EIP-3074 has certain security risks and is relatively lacking in forward compatibility with the account abstraction roadmap. This article lists some of these weaknesses.

Article Source:

https://notes.ethereum.org/@yoav/3074-implications

Article author:

yoav.eth

View:

yoav.eth: Potential centralization issues brought by EIP-3074: Centralized infrastructure: Even for simple use cases like batching, it is difficult to use 3074 without a relayer. It requires two signatures, one for AUTH and one for transactions, which is a poor user experience, so many use cases use relayers. Users and developers usually choose the path of least resistance, which is centralized relayers in 3074. Permissioned innovation: Due to the lack of permission separation, any use case requires full account access to be granted to the caller. Due to this security design, wallets must whitelist callers and do not allow users to choose. When dapps want to use 3074-related user experience improvements, they will think that wallets can implement the whitelist function of popular wallets, which will allow popular wallets to control innovation. Censorship resistance and inclusion in the list: Due to the current way block construction works, Ethereum's censorship cost is lower than people realize. The remedy should be inclusion in the list. Censorship resistance is one of the core values and is more urgent than account abstraction or 3074. 3074 is incompatible with the inclusion list and causes EIP-7547 to be excluded from the next fork. [Original text in English]

yoav.eth: Possible alternatives: RIP-7560 adds a new transaction type (4), equivalent to ERC-4337 UserOp. It specifies things like paymaster to enable account-independent gas abstraction, deploying the account's initcode in the first transaction, etc. EOA support in TransactionType4 enables similar functionality to 3074 (such as gas abstraction, batching, delegation), and has certain advantages over other EOA improvement proposals: consistent with the native AA roadmap, wallets do not need to support two standards; enables EOA to use existing paymasters; requires less trust than 3074 for most common use cases; no relayers or 4337 callers are required. EOA will use the AA memory pool; allow EOA to be migrated to AA using a paymaster; enable EOA signature aggregation, which can save a lot of rollup network fees; and will not introduce more technical debt when moving to quantum-resistant signatures. [Original text in English]