Distinguish possibilities from implemented features
Ethereum’s account abstraction guide describes possibilities such as transaction batching, sponsored gas and recovery rules. EIP-7702 defines code delegation for externally owned accounts and discusses motivations including batching and sponsorship. Actual features depend on the wallet and service implementation.
Start with what the user can do today. Explain conditions that depend on the network, wallet and account state, rather than putting a new standard’s name ahead of the experience.
Sources: Ethereum.org — Account abstractionEIP-7702 — Set Code for EOAs
Simpler journeys still need clear consent
Combining several steps can reduce clicks, but users still need to understand what happens within them. Present a summary of the actions and permissions before execution, with access to further detail.
Avoid presenting account changes or delegation as ordinary sign-in. EIP-7702 discusses the broad access of delegated code and the need to verify it. Technical teams must review implementation security; design should help users understand the action accurately.
Sources: EIP-7702 — Set Code for EOAs
Explain sponsorship and recovery in product language
When gas is sponsored, show eligible actions, limits and what happens when a limit is reached. Explain who pays the cost so that ‘free’ is not read as a promise covering every transaction.
Recovery needs an explanation of prerequisites and procedures. Tell users when to register a recovery method, which steps follow and where to get help. The experience continues beyond the sign-up screen.