Search

Search for projects by name

Recategorisation happening in
Learn more
L2BEAT Bridges is a work in progress. You might find incomplete research or inconsistent naming. Join our Discord to suggest improvements!

Near Omni Bridge logoNear Omni Bridge

About

The NEAR Omni Bridge (also called Rainbow Bridge) is an MPC-validated multichain bridge. The MPC signature request/response logic is implemented on the NEAR blockchan and is called "Chain Signatures" there. Although it currently is limited to sending...


  • Total value secured
  • Destination
  • Validated by
    MPC
  • Type
    Single-chain

  • About

    The NEAR Omni Bridge (also called Rainbow Bridge) is an MPC-validated multichain bridge. The MPC signature request/response logic is implemented on the NEAR blockchan and is called "Chain Signatures" there. Although it currently is limited to sending...

    Value Secured

    2025 Apr 03 — Jun 14

    Milestones & Incidents

    Rainbow becomes Omni

    2025 Apr 4th

    NEAR transitions from the lightclient-validated Rainbow Bridge to the MPC-validated Omni Bridge.

    Learn more
    Risk summary
    Technology

    Principle of operation

    The NEAR Omni Bridge is a Token Bridge that allows transferring assets and passing arbitrary messages between Ethereum, NEAR, and Aurora chains (and more chains in the future). The bridge locks tokens in the escrow contracts on Ethereum and mints / releases tokens on the Aurora or NEAR networks. When bridging back to Ethereum, tokens are burned / locked on Aurora / NEAR and then released from the escrow on Ethereum.

    • Funds can be frozen if a user bridges an unsupported token or specifies an unsupported destination address.

    MPC validation and ethereum light client

    Multi-party computation (MPC) is used to validate bridge transactions going out from NEAR. This usually means that multiple distributed signers need to combine their signatures to create a single signature authorizings a transaction. The MPC setup is offchain and from an Ethereum L1 perspective is equal to an EOA. Transfers from Ethereum to NEAR are validated by an Ethereum light client implemented as a smart contract on NEAR, of which the source code is unverified.

    • Funds can be stolen if the MPC signers collude or the MPC implementation is exploited.

    • Funds can be frozen if the MPC signers stop signing bridge messages.

    • Users can be censored if the MPC signers do not sign bridge messages.

    Permissions
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner

    Ethereum

    Actors:

    Near Omni Multisig 0x2468…CDE1
    • A Multisig with 3/5 threshold.
    • Can upgrade with no delay
      • OmniBridge
    • Can interact with OmniBridge
      • manage the pauser role and all pause flags (pause and unpause), manage token lists, claim ownership of token contracts and upgrade them, change the derived signer address for incoming message validation
    Used in:
    • Can interact with OmniBridge
      • validate bridge transactions (derived address of the MPC setup)
    • Can interact with OmniBridge
      • pause the bridge escrow for deposits and withdrawals
    Smart contracts
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    A diagram of the smart contract architecture
    A diagram of the smart contract architecture

    Ethereum

    Escrow for all tokens of the NEAR Omnibridge.

    • Roles:
      • defaultAdmin: Near Omni Multisig
      • nearBridgeDerivedAddress: EOA 1
      • pauseAdmin: EOA 2
    • This contract can store any token.
    BridgeToken 0xd5A0…C88F

    The standard implementation used for new tokens minted by the bridge.

    Value Secured is calculated based on these smart contracts and tokens:

    Main escrow for all tokens bridged from Ethereum via Near Omni Bridge to other chains.

    The current deployment carries some associated risks:

    • Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).