by Unity Nodes
docs.near.orgchain abstraction › omnibridge › overview

Omni Bridge Overview

Updated 01-11-2026

View on docs.near.org

Learn about Omni Bridge, a multi-chain asset bridge that enables secure and efficient transfers between blockchain networks using Chain Signatures and MPC technology.

The Omni Bridge is a multi-chain asset bridge that facilitates secure and efficient asset transfers between different blockchain networks. It solves key challenges in cross-chain communication by leveraging Chain Signatures and its decentralized Multi-Party Computation (MPC) service to enable trustless cross-chain asset transfers.

[!TIP]

To learn more see How Omni Bridge Works.

Supported Chains

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.

Currently the supported chains are:

  • Ethereum - (Light client + Chain Signatures)
  • Bitcoin - (Light client + Chain Signatures)
  • Zcash - (Light client + Chain Signatures)
  • Solana - (Wormhole + Chain Signatures)
  • Base - (Wormhole + Chain Signatures)
  • BNB - (Wormhole + Chain Signatures)
  • Arbitrum - (Wormhole + Chain Signatures)
  • Polygon - (Wormhole + Chain Signatures)
  • HyperEVM - (Wormhole + Chain Signatures)
  • Fogo - (Wormhole + Chain Signatures)
  • Abstract - (MPC verification + Chain Signatures)
  • Starknet - (MPC verification + Chain Signatures)
  • Aptos - (MPC verification + Chain Signatures)

The bridge contract lists how each chain's inbound transfers are verified. Read it with:

near contract call-function as-read-only omni.bridge.near get_provers json-args {} network-config mainnet now

Bitcoin and Zcash are listed by get_utxo_chain_connectors instead.

[!NOTE]

See Omni Bridge Roadmap for more details.

Resources

Back to Documentation