Omni Bridge launches with a hybrid architecture, utilizing different verification methods based on chain-specific requirements and technical constraints. This approach allows us to support multiple chains from day one while progressively transitioning to full Chain Signatures integration.Documentation Index
Fetch the complete documentation index at: https://docs.near.org/llms.txt
Use this file to discover all available pages before exploring further.
Supported Chains
The bridge currently supports the following networks:- EVM Chains:
- Ethereum
- Base
- Arbitrum
- BNB Chain
- Polygon (PoS)
- Non-EVM Chains:
- Bitcoin
- Solana
- Zcash
Architecture Overview
Omni Bridge utilizes Chain Signatures as its primary verification mechanism for outbound transfers from NEAR. Incoming transfers rely on chain-specific verification methods, including light clients for maximum security where available.Verification Methods
- Ethereum & Bitcoin: Light Client verification for inbound transfers.
- Other Chains: Message passing protocols verified by the NEAR network.
- Outbound (All Chains): Chain Signatures (MPC) for secure transaction signing.
Future Development
- Protocol Improvements
- Enhanced fee mechanisms
- Cross-chain contract calls
- New token standards support
- Infrastructure
- Expanded relayer network
- Improved monitoring tools
- Enhanced developer tooling
Get Involved
Areas for Contribution
- Chain integrations
- Performance optimization
- Security analysis
- Developer tools
- Near-One/omni-bridge - Omni Bridge repository
- Near-One/bridge-sdk-js - JavaScript SDK
- Near-One/bridge-sdk-rs - Rust SDK and Bridge CLI