Apps
Apps themselves don't need to adopt EIP-7702 directly, but they can now offer smart account capabilities to all user accounts (as long as they are EIP-7702 enabled, or using smart contract wallets).
Apps can do this in several ways:
| Method | Description | Providers |
|---|---|---|
| EIP-5792 | New sendCalls endpoint for making onchain transactions, supporting batch transactions and capabilities like paymasters (EIP-7677) | Viem, thirdweb |
| EIP-4337 | Alt mempool for account abstraction | Biconomy, Pimlico, Alchemy, Candide |
| Other EIPs | Integrating ERC-7710 (Smart Contract Delegation) and ERC-7821 (Minimal Batch Executor Interface) and others | Viem Experimental |
| Product-based | As well as standard-based approaches, some platforms offer custom smart account functionality |
The lowest-hanging fruit for app developers are situations where a user has to make multiple transactions, such as approving ERC20 tokens before making a swap or other action - with smart accounts, these separate calls can be batched in one transaction.
In all cases, apps need to decide how they will handle users without smart accounts (because their wallet does not yet support them, or because they opt out). This might mean not supporting those users, or providing graceful alternative flows. These might look like existing experiences (for example "approve / swap"), but backwards compatibility is also offered by (for example) the new experimental_fallback parameter for Viem's sendCalls method (PR).
The following are some apps which have integrated EIP-5792 to support batched calls and other wallet capabilities for their users: