Users and liquidity are spread over many blockchains: Ethereum, several layer 2s, BNB Chain, Solana and more. A product that wants to reach them has to work on all of those chains without becoming a separate product per chain. Multi-chain tooling is the shared foundation that makes this possible: one place to configure chains, connect to them, deploy to them and show users one consistent picture.
What the Foundation Includes
- Chain registry: one configuration per chain with RPC endpoints, contract addresses, tokens, decimals, block explorers, confirmation depth and fee rules. Adding a chain becomes a configuration change.
- RPC management: multiple providers per chain with health checks, failover and rate-limit handling, so one provider outage does not take your product down.
- Consistent deployments: the same contract addresses across EVM chains where possible, and a record of what runs where. See smart contract tooling.
- Unified data: balances, positions and history across chains in one model, fed by indexing and event listeners.
- Moving between chains: bridges and cross-chain messages behind one interface, see cross-chain bridges.
EVM and Solana Together
EVM chains share one model; Solana has different accounts, transactions, fees and finality. A good abstraction hides what users do not need to see, but does not pretend the chains are the same: transaction building, signing and confirmation stay chain-specific under a common interface.
Chain Abstraction for Users
The end goal is often that users do not need to know which chain they are on: one balance, payment in USDC on whichever chain is cheapest, gas handled for them through gasless transactions. That is achievable, provided the foundation underneath handles the differences properly.
Frequently Asked Questions
How hard is it to add a new chain?
For an EVM chain on a good foundation, mostly configuration, deployment and testing. A chain with a different model, such as Solana, needs its own adapter.
Do we need our own nodes?
Not always. Multiple providers with failover are enough for many products; own nodes help with latency, cost at volume or chains with poor provider support.
Can users see one total balance?
Yes. Balances from all chains are combined, with the per-chain detail available when needed.
Who owns the code?
Ownership of the source code is set out in the contract, and the code can be fully yours, including documentation and tests.
Part of our blockchain development. See our USDC-denominated cross-chain trading app for a multi-chain product in practice.
Go Multi-Chain Without the Mess
Tell us which chains you support today and which come next. We will build a foundation that makes each new chain a small step.