Only Available on Some Wallets: As of now, installing the authorization on the EOA is only available for users of Embedded Wallets - such as Privy, Dynamic, Turnkey, … If your users are using External wallets, such as MetaMask, Rabby, etc… - then you need to use the Fusion Mode
1
Set Up Wallet Client
2
Sign Authorization
Note for Embedded Wallets: Privy, Dynamic, and other embedded wallets may expose their own
signAuthorization()
helper with the same parameters. In that case you can’t use the viem
signAuthorization
method as it’ll throw an error. Our docs have integration guides for every type of embedded wallet. You can follow them.3
Initialize Nexus Account
4
Connect to MEE Relayer
5
Quote Orchestration
Passing Authorizations: We recommend passing authorizations manually as it gives you more control over signing for different chains and wallet providers. However, if you’d just like our SDK to automatically prompt users to sign authorizations, you can omit the
authorizations
field and just set delegate: true
6
Execute Orchestration
Notes
delegate: true
is mandatory.authorization
must be passed. You can pass it manually (recommended) or allow the SDK to prompt the user to sign.accountAddress
must be explicitly overridden to the EOA address to signal EIP-7702 usage.- The Nexus smart account logic will be executed directly on the EOA address.