Tools: Account Abstraction In The Era Of Eip-7702: Cases Where 4337 Is...

Posted on Jan 30

• Originally published at blog.tumf.dev

Originally published on 2026-01-30 Original article (Japanese): EIP-7702時代のAccount Abstraction: 4337が必要なケース

When creating dApps (decentralized applications) on Ethereum, users are often asked to "set up a wallet," "buy ETH," and "pay for gas." This presents a barrier to widespread adoption.

Account Abstraction is a mechanism designed to break down this barrier. There are two specifications: EIP-4337 and EIP-7702.

In short, the introduction of EIP-7702 has significantly reduced the need for 4337. Batch execution for single users and permission management can be achieved solely with 7702. The necessity for 4337 is limited to two cases: "permissionless gas sponsors" and "multiple user aggregation."

In this article, we will first clarify "why Account Abstraction is necessary" and then illustrate the specific use cases for 7702 and 4337.

Most users utilize EOAs, but they come with strict limitations:

Account Abstraction addresses these issues by making "the behavior of accounts programmable":

In essence, Account Abstraction "compensates for the inconveniences of EOAs with the flexibility of contracts."

There is not just one way to achieve Account Abstraction. EIP-4337 and EIP-7702 aim for the same goal through different approaches.

Source: Dev.to