mode: 'eoa-7702' for embedded wallet users (Privy, Dynamic, Turnkey) that support EIP-7702 delegation. This gives you smart account capabilities without deploying a separate contract.
How EIP-7702 Mode Works
EIP-7702 lets an EOA temporarily delegate to smart contract code. This means:- No separate smart account deployment
- Single signature like smart accounts
- No
fundingTokensrequired - Native gas abstraction
1
First-time setup
User signs an authorization to delegate their EOA (once per chain)
2
Get quote
API returns a simple payload to sign
3
User signs
One signature for any operation
4
MEE executes
Transaction includes delegation + operations atomically
Basic Request
Required Parameters
No
fundingTokens needed—7702 mode works like smart accounts but uses the EOA directly.Handling First-Time Authorization
If the user hasn’t delegated their EOA yet, the API returns a 412 error with authorization data:412 Response Structure
Complete Authorization Flow
Quote Response
After authorization (or if already authorized), you get a normal quote:Signing the Payload
EIP-7702 mode uses simple message signing:Complete Example
Wallet Support
EIP-7702 requires wallet support forsignAuthorization. Currently supported by:
Privy
Full support
Dynamic
Full support
Turnkey
Full support
When to Use EIP-7702 Mode
Best For
- Embedded wallets (Privy, Dynamic, Turnkey)
- Backend systems with private key access
- Apps wanting smart account UX without deployment
- Single-signature flows
Not For
- MetaMask/Rabby users (use
eoamode) - Wallets without 7702 support
- Users who need persistent smart accounts
Comparison with Other Modes
Next Steps
Sign Payload
Signing details for all modes
Execute
Submit and track