Quickstart
Get up and running in 5 minutes
Architecture
Understand the transaction builder pattern
EVM Transfers
Bridge tokens from Ethereum, Base, Arbitrum
API Reference
Complete API documentation
How It Works
The SDK is a transaction builder — it handles all the bridge protocol complexity (validation, encoding, fee calculation) and gives you back unsigned transactions. You then sign and broadcast using whatever library you prefer. This design gives you full control over signing, gas estimation, and transaction management. Whether you’re building a frontend wallet integration or a backend service with your own key management, the SDK fits your architecture.The Three-Step Flow
Every cross-chain transfer follows the same pattern:1
Validate
Call
bridge.validateTransfer() with your transfer parameters. The SDK checks that addresses are valid, the token is registered, amounts survive decimal normalization, and returns a ValidatedTransfer object.2
Build
Pass the validated transfer to a chain-specific builder (like
evm.buildTransfer()). You get back an unsigned transaction — a plain object with to, data, value, etc.3
Sign & Send
Use your preferred library to sign and broadcast. The unsigned transaction format works directly with viem, ethers v6, near-kit, @near-js/*, and @solana/web3.js.
Packages
Install the umbrella package for everything, or pick individual packages to minimize bundle size:@omni-bridge
sdk → Umbrella (re-exports all)
core → Validation, types, API client
evm → Ethereum, Base, Arbitrum, Polygon, BNB
near → NEAR Protocol
solana → Solana
btc → Bitcoin, Zcash
Supported Chains
EVM Chains
Ethereum, Base, Arbitrum, Polygon, BNB Chain
NEAR
NEAR Protocol
Solana
Solana
Bitcoin
Bitcoin
Zcash
Zcash