Routing
Routing
The chains the protocol can touch, and how the set grows.
Every chain the protocol can touch is identified by a canonical ChainId in @arc-route/types. The current set includes Ethereum, Base, Solana, Arbitrum, Optimism, Polygon, Avalanche, BNB, HyperEVM, and Arc — the Arc settlement chain, which is always the terminal destination of a route in this version of the protocol.
A network's presence in the set means more than a checkbox: it means the bridge lanes and liquidity venues on that chain are wired into the routing graph with sufficient depth and reliability to participate in scored routes. Because routing depends on real, available depth, a chain with connectivity but no reported liquidity contributes no traversable edges.
New networks are added when the bridge lanes required to route and settle on them are registered, liquidity snapshots are flowing, and the lanes have demonstrated sufficient depth and reliability. Adding a network is not merely a configuration change; it is a decision that the system can serve transfers on that chain to the same standard as the rest of the set.
The set expands deliberately, in step with the Genesis roadmap, rather than opportunistically. Because ChainId is an enumerated type, adding a chain is a typed change reviewed in the open on GitHub.