- Batch multiple actions into one atomic call (e.g. deposit → call user wallet → mint NFT)
- Delegate tx execution to the user, preserving
msg.senderon the destination chain - Sponsor gas or use ERC-20s for fee payments
- Route logic across chains, bridging into EOAs that execute contract logic without a separate deployment
ERC-4337
Relay uses ERC-4337 to support complex smart account flows. Key features include:- Sponsored transactions using paymasters
- Arbitrary smart account validation logic
- Bundled execution: approve → swap → send, all in one tx
EIP-7702
Relay uses EIP-7702 to enable EOAs to become smart accounts. We support 7702 to:- Execute logic on destination chains where the user is
msg.sender
Useful for apps where the final contract cares about the actual sender (e.g. NFT mints, purchases) - Preserve intent and gas delegation across chains
Solvers can deliver ETH or tokens to the user’s EOA, and the EOA can act as a smart wallet - Avoid smart account setup on destination: the user’s EOA behaves like a contract temporarily, powered by an
authorizationListsignature
Why Smart Accounts Matter for Relay
Smart accounts help your app preserve user identity, batch calls, and manage gas across chains:
For example, when someone uses ETH on Chain A to buy an NFT on Chain B:
- A solver delivers ETH to their EOA on Chain B
- That EOA uses a signed 7702 tx to batch logic on Chain B: approve → mint
msg.sender= the user, not the solver
🔗 Explore the Guides
- ERC-4337 Guide – Learn how Relay uses UserOperations and bundlers
- EIP-7702 Guide – See how Relay turns EOAs into smart wallets with
authorizationList
The Relay platform supports both ERC-4337 and EIP-7702 for gas sponsorship, batching, and user-authorized execution. Let us know what you’re building.