Skip to main content
Choose EIP-7702 when you control an EOA and want it to act as a Nexus smart account without changing its address or moving its assets.

​
Choose EIP-7702 when

  • An embedded or local EOA already has assets or onchain history.
  • The account must keep the same address.
  • You need supported smart account capabilities without creating a separate account.
EIP-7702 adoption uses Nexus in the EVM configuration. The EOA must sign both the Nexus initialization data and EIP-7702 authorizations.

​
Consider the tradeoffs

  • The EOA remains the root authority, so losing or compromising its key compromises the account.
  • The root EOA prevents a true multisig or key-rotation security model.
  • External wallets may not let your app choose and authorize the required delegation target. Use a plain EOA or a separate smart account for those users.
Choose a new smart account when you can use a separate address and need stronger ownership or recovery options.

Configure EIP-7702

Create the account, sign its initialization data, and collect delegation proofs during transaction signing.