Smart contract wallet

A smart contract wallet, often called a smart wallet, is a crypto account run by code on the blockchain instead of by a single private key, so its rules can require several approvals, allow recovery after a lost key, bundle steps such as an approval and a swap, or let someone else pay the network fee. On Ethereum these accounts work through the ERC-4337 standard or, since the Pectra upgrade of May 7, 2025, through EIP-7702, which lets an ordinary key-based account point to contract code.

Counted on Ethereum, November 12, 2026

How much are smart wallets used? On Ethereum the answer sits in the logs of the EntryPoint contracts, through which ERC-4337 accounts send what the standard calls UserOperations, bundled into ordinary transactions by operators known as bundlers. A public node was asked for those logs across blocks 26,396,221 to 26,397,220, mined between 03:37:59 and 06:59:23 UTC on November 12, 2026.

EntryPoint contract User operations Distinct accounts
0x0000000071727De22E5E9d8BAf0edAc6f37da032 2,044 1,426
0x4337084d9e255ff0702461cf8895ce9e3b5ff108 (version 0.8) 585 457

Both contracts carry the name EntryPoint and verified code on explorer Blockscout, and the reference implementation’s README gives the second address for version 0.8. Of the 2,629 operations, 2,616 succeeded.

A second route opened with the Pectra upgrade, which ethereum.org’s fork history dates to May 7, 2025, block 22,431,084. EIP-7702 adds transaction type 4, which sets contract code on an ordinary account. In the last 200 blocks of the same window, 821 of 50,769 transactions were of that type, carrying 1,011 authorizations between them.

What changes compared with a key

An ordinary Ethereum account, which Safe’s documentation calls an EOA, answers to one private key, and anyone who gets hold of that key gains “complete control of the account.” In a smart account, the same page says, “no single private key is used to verify transactions,” and the contract’s code sets who may approve what.

The ethereum.org account abstraction page lists what that allows, from recovering an account after losing the keys to having someone else pay your gas and batching an approval with a swap.

Where you see it

An address alone will not tell you, since Safe’s documentation says it is “impossible to tell them apart from EOAs by looking at an Ethereum address.” The account’s code does. One account, 0xd52573f6d4f68d8e7f8fe2ed50a1023c5f6fe82a, sent a type 4 transaction in block 26,397,220, and the node then reported its code as 0xef0100 followed by a 20-byte address, the delegation marker EIP-7702 defines.

The mistake: signing away the account

An EIP-7702 authorization is a decision about who runs your account. The proposal’s security section warns that “a poorly implemented delegate can allow a malicious actor to take near complete control over a signer’s EOA.” The delegate in the transaction above appeared on Blockscout with no verified source code, so what it does could not be read there.

Before you approve an upgrade prompt in a wallet, check which contract it delegates to, whether that contract’s code is published and verified, and who can change it.

Where it comes up