What is Chain Abstraction?
Eliminate manual bridging, chain switching, and wallet complexity when transacting across chains.
Managing multiple chains, tokens, and accounts fragments wallet liquidity for Web3 users. Even with enough assets overall, funds scattered across chains make transacting difficult and require complex, time-consuming conversions.
Chain abstraction lets users access a unified balance across all wallet-linked chains, enabling transactions anywhere.
Instead of bridging manually chain by chain, users express a clear intent: the SDK requests a quote (which source chains to draw from, and the fees), the user reviews it and signs a single message covering the whole operation.
The signed intent is submitted to the Nexus network, where a solver delivers the funds on the destination chain — usually within seconds — and is reimbursed from the user's deposited funds at settlement. See the intent lifecycle for the full flow.
Showing a subset of supported chains. See Supported Chains & Tokens for the full list.
As part of setup, devs configure allowances per chain and token. Users approve or reject these allowances. For supported chains and tokens, the protocol uses these allowances to deposit the required funds into the source-chain Vault contracts.
Note
Why Chain Abstraction?
Chain abstraction enables unified balance to simplify and streamline Web3 transactions. It offers:
Chain abstraction enables unified balance to simplify and streamline Web3 transactions. It offers:
- Fast Fulfilment: Solvers front liquidity on the destination chain, so users receive funds in seconds instead of waiting for bridge finality.
- Unified Liquidity: Provides a consolidated view of user assets across wallet-linked chains with no manual bridging.
- Simplified UX: One signature replaces multi-step bridging, chain switching, and per-chain gas management.
- Streamlined DX: Developers can add unified balances to dApps with minimal changes and no smart contract updates for new chains.
How is this guide?