Rainbow Bridge

Overview

Rainbow Bridge connects NEAR and Ethereum by carrying headers, events, and proofs between bridge contracts. Relayers transport evidence, while on-chain verification checks relevant source-chain information before destination execution.

The architecture reduces reliance on a single custodian, but liveness still depends on relayers, source and destination progress, gas funding, and contract operation. Direction-specific verification and challenge processes can produce different transfer times. Users should verify official contracts, token mappings, recipient, expected asset representation, and current operating status. Integrators need to monitor source finality, proof acceptance, destination execution, and any separate claim step. Light-client verification narrows trust assumptions but does not remove smart-contract, upgrade, chain-consensus, or application-interface risk. Matching ticker symbols do not prove asset identity, so crediting must use the network and contract or native-asset identifier. Routing and custody records must bind the source asset, destination representation, contract addresses, decimals, mint or custody model, and redemption path.

Operational support needs separate status for every stage, timeout and replay protection, route-specific monitoring, and a documented recovery path. Paused contracts, depleted liquidity, delayed proofs, or destination failure should enter review rather than being reported as a completed cross-chain payment. Completion of an early stage does not prove that value or instructions reached the destination. Operational modeling should cover a multi-stage operation: source authorization, source inclusion and finality, message or proof production, relay, destination verification, destination execution, and destination finality. An official or canonical label does not remove these dependencies. Risk exposure depends on the exact verification route. Security analysis must account for the exact validators or signers, proof mechanism, relayers, upgrade controls, rate limits, and liquidity arrangements used by the route.