NewsCryptoEIP-7702 Lets Ethereum Accounts Gain New Functions While Keeping the Same Address

EIP-7702 Lets Ethereum Accounts Gain New Functions While Keeping the Same Address

Author: The Market Periodical·

Key Takeaways

  • •Ethereum's Pectra upgrade introduced EIP-7702 in May 2025, allowing private-key-controlled accounts to run smart contract code without moving to a new address.
  • •Delegation requires an authorization signed with the account's original private key and remains active until it is replaced or reverted.
  • •An account can hold only one delegation target at a time, and a later delegation replaces any earlier one regardless of which wallet is used.
  • •Wallet software and standards such as ERC-5792 shape how delegated functions reach users, with MetaMask using a separate update step and Ambire triggering delegation through account activity.
  • •The original private key keeps ultimate authority over the account, including the power to authorize a replacement delegation or clear it entirely.
EIP-7702 Lets Ethereum Accounts Gain New Functions While Keeping the Same Address

Ethereum's Pectra upgrade, activated on May 7, 2025, changed what an existing account can do without requiring it to move to a new address. One component of that upgrade, EIP-7702, allows a conventional account controlled by a private key to make use of smart contract code. Capabilities such as grouping multiple operations into a single batch can therefore be offered through an account that already exists, meaning the address stays familiar while the account gains programmable behavior.

The distinction is set out in the Ethereum Foundation's May 2026 explanation of how EIP-7702 changes the account model. It describes a mechanism for connecting an account to deployed code while preserving both its address and its original key authority. Understanding the mechanism requires separating the account recorded on Ethereum from the wallet software used to interact with it. A network upgrade establishes what the protocol permits, while software determines how that capability reaches users.

An Address Is Separate from the Wallet Interface

An Ethereum address identifies an account, while a wallet supplies the interface for interacting with it. Account upgrades now appearing across blockchain coverage can add functions at an address already in use. The wallet presents the controls for those functions, while the account's configuration determines which code it executes. An interface update and a change to an account's execution capabilities are distinct developments, even when they arrive as part of the same release. In practice, that means a wallet can look new while the account behaves exactly as before, and an account can gain new behavior while the wallet interface stays the same.

Ethereum has long distinguished between externally owned accounts, which are controlled by a private key, and contract accounts, which execute deployed code. EIP-7702 allows an existing key-controlled account to use contract logic without being replaced by a separate contract account. The interface through which the owner sees those functions remains a different piece of software.

An account page can display both the account address and the implementation address. Etherscan's June 2025 guide to EIP-7702 accounts describes a delegated-address field alongside the account's details. The account address identifies the user's account, while that field identifies its code implementation. Displaying both addresses records a relationship between them; it does not mean the owner has migrated from one account to another. The field also gives observers a way to see, directly on an explorer, which implementation an account is currently using.

Delegated Code Supplies Account Functions

For an externally owned account (EOA), delegation begins with an authorization signed with its private key. That authorization specifies a delegation target: the address of code already deployed on Ethereum. The network then records a pointer to that code in the existing account. When the code runs through this delegation, it operates as that account. Its deployment address identifies the implementation, while the user keeps the account address through which the functions operate.

Delegation remains active until it is changed or reverted. It is not a temporary setting that disappears once the transaction establishing it has finished. That persistence makes delegation part of the account's ongoing configuration, distinct from the individual operations subsequently performed through it. Anyone reviewing an account can therefore treat its delegation as a standing attribute to check, rather than a detail of a single past transaction.

Batching illustrates what programmable behavior contributes. Multiple operations can be organized for execution within a single transaction, with the delegated implementation providing the logic. In an atomic batch, every operation succeeds or none does. The network's delegation mechanism and the code's batching function perform different jobs: the first establishes which code is executed, while the second determines the behavior that is supported.

The same Etherscan guide documents Ambire's batching implementation and explains that its batched actions appear under one transaction hash in the block explorer. Individual actions remain visible within that record. A single transaction can therefore contain several operations, meaning that counting transactions and counting actions describe different things. Batching changes how work is grouped without requiring a new account address, and a multi-step sequence can be recorded once while each underlying action stays individually reviewable.

An account can hold only one delegation target at a time. A later delegation replaces the earlier one, including when the same address is used across supporting wallets. Opening the account through another wallet does not give that application an independent delegation slot. Whatever wallet is used, the functions available at the address are those of the single implementation it currently points to.

Wallet Software Determines Which Functions Appear

Protocol support does not specify an entire wallet product. Developers supply the delegated implementation, connect supported functions to the interface, and determine how applications request them. The same underlying standard can therefore support different experiences without changing the basic account model.

The Foundation's guide identifies ERC-5792 as an interface for applications to request a batch of calls from a wallet. Calls are requests to execute code. The wallet decides which account system handles the request, which can include EIP-7702. An application can therefore request a function without prescribing how the wallet implements it.

EIP-7702 creates room for programmable account functions, but the particular code and the surrounding software establish which functions are actually available. Recovery options, alternative authentication, and other account features each require their own implementation. They do not appear automatically simply because the network recognizes delegation. Checking which implementation a wallet delegates to is therefore the practical way to see what an upgraded account can and cannot do.

In its June 2025 description, Etherscan recorded a separate account-update step in MetaMask and automatic delegation triggered by activity in Ambire. Both used EIP-7702, but their activation flows differed. The difference appeared in how the software arranged access to the capability, without changing the underlying requirement for an account authorization.

The Original Key Retains Control

The original private key retains ultimate authority over the EOA, including the ability to authorize a replacement delegation or clear it. Delegated code can still define how its supported operations are authorized. An additional authentication method belongs to that implementation; it does not erase the original key or make its control irrelevant. Custody of that key therefore continues to determine who ultimately controls the account, independent of any features the delegated code provides.

The power to change the delegation is separate from the rules governing individual operations. A wallet can expose a new way to authorize an action while the original key still controls which implementation the account uses. The visible experience can change substantially without requiring the owner to establish another address.

Source: The Market Periodical