All field notes

Architecture · Retrospective

EIP-7702 and the onboarding problem we worked around with email

A plain address card with a blue gear clipped on, beside an envelope.
Concept illustration · AI-generated

On 7 May Ethereum activated the Pectra upgrade, and with it EIP-7702. It lets an ordinary address, the kind a seed phrase controls, point to a contract and run that contract's code as if it were its own. I have been reading it against a problem I know well from Playermon: getting someone into a blockchain game before they are ready to manage a wallet.

The workaround we used

For a new player in a web3 game, the wallet is usually the first thing to get past. At Playermon we tried to move it further back. In April 2023 the team shipped a task list that let a player earn up to three free starter Playermons, and from August 2023 a new account could unlock three starters by verifying an email address. The idea was that people could start playing first and meet the wallet later.

Email covered the start. Trading did not go away, though. Buying on the marketplace still meant holding an address, holding the chain's native token for gas, and signing each step as a separate transaction. In 2024 the team moved some of that into our own contracts: Marketplace V3 let a player list or buy several NFTs in one transaction. That helped, but every application had to build its own version of it.

What 7702 changes

EIP-7702 adds a new transaction type that carries a list of authorisations. Each one is signed by the account's key and names a chain ID, a contract address and a nonce. Once it is processed, the account's code becomes a short pointer to that contract, and calls to the account run the contract's code with the account's own balance and storage. The delegation stays in place until the owner signs a new one, and signing one for the zero address clears it.

For onboarding, three things follow:

  • Batching. An approval and a purchase can go in one transaction, without every marketplace writing its own batch function.
  • Sponsored gas. The delegated code can accept a transaction that someone else relays and pays for, so a new player does not have to buy the native token before their first move.
  • Narrower permissions. Delegated code can support session keys or spending limits, so a game client can act within set bounds without asking for a signature every time.

The part that matters most for games is that the address does not change. Smart-contract accounts were already possible, but they gave the player a new contract address, and anything the player already held had to be moved there. With 7702 the address that already holds a player's items gains the new behaviour.

What it does not change is just as important. A player who has only an email address still has no key. 7702 upgrades accounts that already exist; it does not create one or decide who holds it. And it is an Ethereum change. Playermon's NFTs were minted on Polygon, and any other EVM chain has to adopt the change in its own upgrade before games there can rely on it.

The new risks

Delegation moves risk around, and some of it lands in new places.

  • The delegate has full access. The EIP says the delegated code has unrestricted access to the account. A buggy or malicious delegate can move everything the address holds, NFTs included. Choosing a delegate is choosing who controls the account.
  • One signature is enough. An authorisation is a single signed message, which makes it a prize for phishing sites. The EIP says wallets must not offer applications an interface to request these signatures, because there is no safe way to provide one. A game should never ask for one.
  • Chain ID zero means every chain. An authorisation signed with a chain ID of zero is valid on any chain that supports 7702.
  • The key still rules. Delegation does not reduce what the seed phrase can do. Whoever holds it can still sign anything, including a new delegation. Session keys reduce how often a player is asked to sign; they do not reduce the stakes of losing the main key.
  • Switching delegates is delicate. Two delegate contracts can read the same storage differently, so moving from one to another needs care. Contracts that used tx.origin == msg.sender to mean "a person signed this directly" can no longer rely on it.

How I would use it

If I were designing onboarding for a game today, I would keep email first. A player should be able to try the game before anything on-chain is involved. The wallet would arrive when the player first wants to own or trade something, and that is where 7702 helps: sponsored first transactions, batched approvals, and session keys with tight limits.

The choice of delegate code would belong to the wallet, from well-reviewed and widely used implementations, never to the game. A game that asks players to sign a delegation to the game's own contract is asking for the whole account, and players should be taught to refuse.

7702 makes it easier to give a new player a good first hour on-chain. It does not remove the need to explain what they are signing, and it raises the cost of getting that explanation wrong.