EIP-7702 Cross-Chain Delegation EIP-7702 support is now live in production. This enables bundling of delegation, cross-chain bridging, and contract execution into single transactions.

​
🚀 What’s New

​
Single-Transaction Capabilities

EIP-7702 enables bundling of multiple operations:
  • Delegation - Transform EOAs into smart accounts
  • Cross-chain bridging - Automatic routing between chains
  • Contract execution - Swaps, deposits, arbitrary calls
  • Single transaction - All operations bundled together

​
Technical Scope

Single-transaction execution works for:
  • Destination + ≤1 source chain - Covers majority of scenarios
  • All EVM chains - Live on all supported networks
  • Kernel v3.3 - ZeroDev implementation
  • Fallback available - 3-step pattern for complex routing

Multi-Step Flow

  • Enable delegation (transaction 1)
  • Execute bridge/swap (transaction 2)
  • Perform final action (transaction 3)
Risk: Funds stranded if interrupted

Single-Transaction Flow

  • All operations bundled
  • Single user signature
  • No intermediate states
Benefit: No stuck funds possible

​
Technical Implementation

​
Account Configuration

Configure your account for EIP-7702 delegation: 
{
  "account": {
    "type": "kernel-v3.3-ecdsa", 
    "deploymentType": "EIP7702",
    "signerAddress": "0x5Cb2369421F8a00Ef556d662D6E97C1419B1d37c",
    "accountAddress": "0x5Cb2369421F8a00Ef556d662D6E97C1419B1d37c"
  }
}

​
Flow Detection Logic

Implement automatic routing between single-transaction and fallback patterns: 
function shouldUseSingleTransaction(sourceChains: Chain[], dest: Chain): boolean {
  const additionalChains = sourceChains.filter(c => c.id !== dest.id);
  return additionalChains.length <= 1; // Destination + max 1 source
}

// Route to appropriate flow
if (shouldUseSingleTransaction(sourceChains, destinationChain)) {
  return executeSingleTransaction(); // Single transaction
} else {
  return executeThreeStep(); // Manual delegation + execution
}

​
Use Cases

Common EIP-7702 implementations:
  • Cross-chain aggregation - Combine assets from multiple chains
  • DeFi interactions - Lending, staking, DEX operations
  • Contract calls - Any arbitrary smart contract execution
  • Address preservation - Keep existing EOA addresses

​
Getting Started

1

Update Account Type

Set deploymentType: "EIP7702" in your account configuration.
2

Implement Signing

Add delegation signing using signAuthorization method.
3

Handle Fallbacks

Implement 3-step pattern for complex multi-chain scenarios.

​
Coverage & Limitations

​
✅ Single-Transaction Execution Works

  • Single source chain + destination (e.g., Optimism → Arbitrum)
  • Source + destination same (e.g., USDC on Arbitrum → contract on Arbitrum)
  • Two chains total (e.g., Optimism + Arbitrum → action on Arbitrum)
See supported networks for all available chains.

​
⚠️ Requires Manual Delegation Fallback

  • Multiple source chains (e.g., Optimism + Base + Polygon → Arbitrum)
  • We provide complete workaround documentation and code examples

​
🚧 Current Constraints

Resource Lock Limitation: EOA-based EIP-7702 accounts cannot use Resource Locks due to security requirements.

​
Implementation

​
Account Configuration Update

Update your account configuration to enable EIP-7702: 
{
  "account": {
    "type": "kernel-v3.3-ecdsa",
    "deploymentType": "EIP7702",
    "signerAddress": "0x5Cb2369421F8a00Ef556d662D6E97C1419B1d37c",
    "accountAddress": "0x5Cb2369421F8a00Ef556d662D6E97C1419B1d37c"
  }
}

​
Implementation Guide

Follow our complete implementation guide with working code examples.

​
Resources

Overview

Understand EIP-7702 capabilities and constraints

Getting Started

Complete implementation example

Troubleshooting

Handle multi-input scenarios and edge cases

​
Technical Benefits

Single-Transaction Operations

Bundle multiple operations in single transactions

Address Preservation

Keep existing EOA addresses without migration

Simple Integration

Minimal code changes for existing applications

​
What’s Next

  • Multi-input support: Expanding single-transaction execution constraints
  • Additional implementations: Support for more smart account types
  • Enhanced fallbacks: Improved 3-step pattern tooling
Questions? Join our Discord or reach out via support.