Summary: Orbiter Finance’s docs position the project as a “ZK-tech Based Ethereum Acceleration Engine” for trustless, seamless cross-rollup transactions of Ethereum and Bitcoin native assets. The current primary-source surface spans not just a bridge frontend but a cross-rollup protocol design, arbitration/security model, API/SDK tooling, and customizable “Ultra Bridge” infrastructure, so it is better cataloged as broader cross-rollup interoperability infrastructure than as a simple consumer bridge.
What it does:
Enables cross-rollup transfers of Ethereum/Bitcoin native assets across a wide set of L2/L3 and adjacent networks
Documents a Sender / Maker protocol model where users send to Maker EOAs and Makers complete destination-side delivery subject to protocol rules
Describes arbitration and security components including the Maker Deposit Contract (MDC), Event Binding Contract (EBC), and ZK-SPV proofs
Publishes developer tooling including REST API references and SDK materials; the current JS SDK docs say the SDK is outdated and direct users to the API for quotes
Expands beyond the classic bridge flow with “Ultra Bridge” materials for customizable native-bridge deployments and broader interoperability tooling
Maintains a public GitHub org with smart-contract repos, SDK repos, bridge-related tooling, and a papers repository containing yellowpaper, coordinationlayer, new_era, and zkProver directories
Key claims:
The docs describe Orbiter as a “ZK-tech Based Ethereum Acceleration Engine” and say it enables trustless, seamless cross-rollup transactions of Ethereum/Bitcoin native assets
The overview docs list broad network coverage including Ethereum, zkSync Era, zkSync Lite, Linea, Mantle, Base, StarkNet, opBNB, Scroll, Arbitrum, Arbitrum Nova, Loopring, Optimism, Polygon, Polygon zkEVM, BNB Chain, Zora, ImmutableX, BOB, BEVM, Bitlayer, and BSquared
The overview claims transactions between two EOAs can complete in 10 to 20 seconds and frames the product as unusually cost-efficient
The bridge-protocol docs are unusually concrete about the operating model: sender-to-maker EOA transfers, destination-network identification codes embedded in the transfer amount, and an arbitration path using MDC, EBC, and ZK-SPV components
The JS SDK docs broaden the apparent network scope further by showing EVM, BTC, Tron, Starknet, and Solana examples, while also noting that the SDK is outdated and the API should now be used for quotes
The public GitHub org suggests a broader technical surface than the homepage alone, including bridge skills, smart contracts, SDKs, and a papers repo
Whitepaper: The current docs did not surface a canonical Orbiter whitepaper or technical paper in this pass, but the public GitHub organization does maintain a papers repository with yellowpaper, coordinationlayer, new_era, and zkProver directories. The best current source of truth is the docs plus the GitHub org; see ../whitepapers/orbiter-finance-primary-sources-2026-04-27.md.