How It Works
- User signs a single message
- MEE executes operations on the source chain
- MEE waits for bridge completion
- MEE executes operations on the destination chain
- User receives final tokens
Basic Cross-Chain Flow
Runtime Injection for Bridge Outputs
Since bridge outputs aren’t known upfront, useruntimeERC20BalanceOf:
Automatic Sequencing: MEE retries the swap instruction until the constraint is satisfied (bridge tokens have arrived).
Fusion Mode for External Wallets
For MetaMask/Rabby users:Example: Bridge → Swap → Deposit
Complete flow: USDC on Arbitrum → WETH yield on BaseKey Benefits
| Traditional | With MEE |
|---|---|
| 4+ signatures | 1 signature |
| Manual bridge waiting | Automatic |
| ETH needed on both chains | Pay in one token |
| Risk of stuck states | No stuck states—programmatic fund retrieval via cleanups |
Important: Cross-chain transactions are not atomic—only single-chain batches are fully atomic (all-or-nothing). For cross-chain flows, if a step fails after bridging, tokens won’t be lost—use cleanup transactions to programmatically return funds to the user’s wallet.
Next Steps
Composable Batching
Deep dive into dynamic parameters