Router Protocol

• Name: Router Protocol
• URL: https://www.routerprotocol.com/
• Tags: ethereum-ecosystem solana-ecosystem
• Category: cross-chain execution and routing infrastructure / interoperability API
• Summary: Router Protocol’s old Router Chain story is dead weight now. The live docs say that chain has been sunset and instead present Router OGA as a route-packaging layer sitting above bridges, DEXs, and solver paths. In this corpus it fits better as execution middleware than as a meaningful standalone chain.
• What it does:
  • Exposes the Xplore REST API for cross-chain swap and bridge quotes, chain/token/tool discovery, and transaction-status tracking
  • Frames the network as a programmable execution graph connecting bridges, DEXs, solvers, and messaging protocols
  • Publishes architecture around a permissionless node registry, on-chain reputation, split-and-optimize execution, modular hooks, and execution/liquidity oracles
  • Supports swaps and bridge flows across EVM, non-EVM, and L2 networks including Ethereum, Optimism, BSC, Polygon, World Chain, HyperEVM, Base, Plasma, Arbitrum, and Solana in the current docs snapshot
  • Maintains public security-assessment materials through its docs and GitHub audit repository
• Key claims:
  • The current docs say “Router Chain has been sunset” and that the old Router Chain documentation is “no longer valid,” which is important because it shifts the research focus to OGA rather than to the legacy chain narrative
  • The OGA docs describe Router as a “non-custodial, chain-agnostic programmable execution graph” designed to unify fragmented liquidity across EVM, non-EVM, and L2 networks
  • The docs repeatedly claim sub-10 bps execution costs on trades up to $50 million and 99.5% settlement reliability
  • The architecture docs emphasize a permissionless node registry with EIP-712 authentication and on-chain reputation scoring for bridges, DEXs, and solver nodes
  • The API docs show a production Xplore endpoint plus separate chains, tokens, tools, quote, and transaction-status APIs, which makes the system look like integrator-facing execution infrastructure rather than only a consumer bridge frontend
  • The security docs link a public audit-report repository and a downloadable “Router Protocol Aggregator” security assessment PDF, which is a strong operational signal even without a canonical public OGA whitepaper URL surfaced in this pass
• Whitepaper: No clearly accessible canonical Router OGA whitepaper URL surfaced in this pass. The strongest current public source of truth appears to be the live OGA docs plus the public audit materials and GitHub organization; see ../whitepapers/router-protocol-primary-sources-2026-04-27.md.
• Sources:
  • https://www.routerprotocol.com/
  • https://docs.routerprotocol.com/
  • https://docs.routerprotocol.com/docs/about-oga/
  • https://docs.routerprotocol.com/docs/about-oga/architecture/
  • https://docs.routerprotocol.com/docs/about-oga/supported-chains/
  • https://docs.routerprotocol.com/docs/about-oga/security/
  • https://docs.routerprotocol.com/docs/api-reference/
  • https://github.com/router-protocol
  • https://github.com/router-protocol/audit-reports

Internal linkages

• Best upward reads: across and li-fi. Those are stronger anchors for app-facing route selection and execution packaging.
• Keep this note on route ranking, venue admission, and API-hidden defaults rather than treating Router as a peer to every underlying bridge it can package.

Governance / control risk

• The real questions are who gets admitted into the graph, how routes and fallbacks are ranked, how reputation is computed, and how much of that policy stays inspectable versus hidden behind the API.

• That is the whole point here: Router matters only if developers outsource multichain path selection to its graph and status layer. The leverage sits in default menu control, not in the soft aggregator label.

• Last reviewed: 2026-05-26 UTC