Ethereum News
Account abstraction deployment hits 4.3 million as ERC-7702 activates

The October 2026 activation of ERC-7702 changes how users handle Ethereum accounts. This proposal introduces a new transaction type called SETCODETX_TYPE (0x04) to allow Externally Owned Accounts to temporarily delegate execution to smart contracts. Users provide an authorizationlist containing the chain_id, address, nonce, y_parity, r, and s values to authorize a proxy address. This delegation is reversible, as users can change or remove these delegations at will. I see this as a bridge between simple keys and programmable code. This mechanism lets users keep existing addresses and transaction histories while using features like gas abstraction or batched transactions.
In the Pectra upgrade, the authorizationlist field is a major change from the common 0x02 transaction type. Each element in the list is an authorization for an address proxy. The chain_id is used to prevent replay attacks, and the nonce is the same as the signer’s current nonce. Once the transaction hits the chain, the code field for the authority address is the Delegation Designation (DD) for the proxy address. This user experience is similar to an ERC-1167 proxy contract. Because the code field is a fixed prefix of 0xef0100, users cannot deploy this specific type of code through conventional contract deployment methods. They must use the 0x04 transaction.
EIP-3074 also adds new Ethereum opcodes like AUTH and AUTHCALL to give EOAs more power. AUTH uses a digital signature to verify that the user gives permission. AUTHCALL allows the authorized smart contract to perform transactions on behalf of the user. This reduces the exposure of private keys.
Architecture choices and usage shifts
Users face a choice between three distinct architectures. Externally Owned Accounts require only a single private key and cost nothing to create. Smart Wallets, driven by standards like ERC-4337, require onchain deployment costing 100,000 to 300,000 gas per account. EIP-7702 provides a middle path by allowing existing EOAs to act like smart contracts through delegation.
The 4.3 million smart contract wallet deployments this year have already surpassed the EOA user growth seen in MetaMask. While EOAs remain the choice for cold storage or low-complexity trades, smart wallets are the choice for the security needed for enterprise treasury management or automated DeFi strategies. You should recognize that a smart wallet provides higher complexity and potential attack surfaces compared to a simple key-pair.
| Feature | EOA | Smart Wallet (ERC-4337) | Smart EOA (EIP-7702) |
|---|---|---|---|
| Creation Cost | Free | 100,000-300,000 gas | Low (via delegation) |
| Control | Single Private Key | Contract Logic | Delegated Contract Logic |
| Gas Payment | Native Token Only | Any Token (Paymaster) | Any Token (via Delegation) |
| Key Management | Private Key | Multi-sig/Social Recovery | Delegated Smart Features |
| Address Portability | Universal | Requires Factory/Salt | Retains Original Address |
MetaMask smart accounts, available in version 12.17.1 and above, allow users to switch to a smart account in one click. This process points the existing account to a MetaMask Delegator smart contract, which performs additional functionality on your behalf without requiring you to migrate funds or change your address. This implementation uses ERC-7710 to allow redeeming permissions in a way compatible with other implementations. ERC-7715 also helps unify the format in which permissions are requested and granted between wallets and dapps.
Network activity and economic shifts
Ethereum network activity shows a large surge. On-chain data indicates an average of 327,100 new wallets are created every day, with a single-day record high of 393,600. This growth follows the Fusaka upgrade in December 2025, which made the network cheaper and easier to use. Stablecoin transfer volume reached $8 trillion in the last quarter of 2025. As more users adopt account abstraction, Standard Chartered forecasts ETH could reach $7,500 by the end of 2026.
The ability to batch transactions helps reduce the total gas spent. Instead of paying for separate transactions, a user can use a single signature to authorize an invoker. The invoker uses AUTHCALL to approve a protocol like Uniswap and then executes the swap. This saves gas, time, and effort. For developers, optimizing gas involves using keccak256 over other hash functions and using bytes32 over strings. Storing data in the bytecode instead of storage can reduce costs from 20,000 gas to 200 gas.
Whale interest also drives price action. A newly created wallet recently moved 2,400 ETH, valued at over $7.52 million, from the Binance exchange. This massive movement coincides with rising social trends in DeFi and Web3 games.
| Metric | Value |
|---|---|
| Daily New Wallet Average | 327,100 |
| Single Day Wallet Record | 393,600 |
| Q4 2025 Stablecoin Volume | $8,000,000,000,000 |
| Smart Contract Wallet Deployments | 4,300,000+ |
In late February 2026, the Ethereum Foundation launched the Defipunk initiative to focus on permissionless and private infrastructure. Mutuum Finance aligns with these standards, having raised $20.6 million and maintaining 19,000 holders. It uses a Peer-to-Contract (P2C) and Peer-to-Peer (P2P) model with mtTokens like mtETH or mtUSDT. Mutuum Finance uses decentralized oracles to provide real-time price data to calculate the Stability Factor of every loan. This Health Factor acts as a safety score. If it drops below a certain level due to market volatility, the automated systems step in to protect lender funds.
Security risks and delegation flaws
The new delegation model introduces a specific vulnerability. Race condition bots can monitor authorization transactions in the mempool and call the initialize function before the intended user. This allows an attacker to seize control of the contract wallet permissions. I find this flaw particularly dangerous for users who rely on newly deployed delegation contracts.
In full Smart Wallets, deployment and initialization are often packaged in a single transaction to avoid race conditions. In the EIP-7702 scenario, authorization signatures exist separately in the authorization_list. This separation creates the window for bots to intercept the initialization process.
Users must also verify that the target contract for delegation is open-source and has a third-party audit report. Malicious invokers could attempt unauthorized transactions if the integration lacks strict security checks. Phishing attacks will likely target users who receive prompts to upgrade their accounts outside of their standard wallet interface.
I advise caution when using EIP-7702 because the original EOA private key retains ultimate control and can override any delegation. This means smart EOAs do not eliminate the single-key risk that makes traditional accounts vulnerable. For use cases requiring true multi-signature security or irrevocable escrow arrangements, full Smart Wallets are the better choice.
Why do some users still prefer the single-key risk of a standard EOA?