Four rails. One of them is right.
Hyperion moves money between Stellar and the EVM chains without ever deciding for itself that a cross-chain message is real. It prices four rails that already made that decision and were audited for it, takes the one that lands the most, and tells you what the other three would have cost you.
That is a smaller promise than most bridges make, and it is the reason this one is worth using. The trust you are extending is Circle's, or Axelar's validator set's, or Allbridge's pool. It is never ours. We hold the bookkeeping, the limits and the fee, and we are honest about which of those three is taking your money.
Route planner
live local pricingStellar
origin leg
The leg you control. A ledger closes every five seconds and finality means finality, so once a departure is in a ledger there is nothing left to wait out. Seven decimal places, which is one more than USDC carries on every EVM chain, and that mismatch is checked rather than rounded away.
- finality
- 5s, deterministic
- precision
- 7 decimals
- router
- CDMOLDF4...ZOZ5LWCWF
- flow window
- 720 ledgers
Transfer execution
Axelar Interchain Token ServiceThe switchyard
one rail won
Arc
destination leg
The leg you wait on, except here you mostly do not. Arc settles deterministically in one confirmation and charges gas in USDC, which removes the usual problem of needing a second asset you do not have to move the first one. Six decimals on the token and eighteen on the gas accounting, and conflating those two is a mistake worth a factor of a million.
- confirmations
- 1
- gas token
- USDC
- precision
- 6 decimals
- cctp domain
- 26
Parked claim settlement
permissionless recoveryWhen a cross-chain delivery lands but cannot be handed directly to the recipient (for example, a destination Stellar classic account without an active asset trustline), the router parks the funds safely. Anyone can settle a parked claim once the recipient condition is resolved.
What is actually deployed
The Stellar half is live on testnet and verified against its own deployment record, which is a file in the contracts repository that a loader validates rather than casts. No CCTP adapter yet: Circle deploys those contracts per network and does not publish a fixed address list, so the router refuses that rail by name instead of pointing at an address somebody guessed.
- router
- CDMOLDF4SJDEDRWTDF7XAYMSRE6L3YEHHIRF57CFWNQYNC6ZOZ5LWCWF
- axelar its
- CBK3TPRQR5A3H2AWESOUX4MVYOP63VNQ5EYHCX26EEJUC5B5FLB4DV5O
- usdc
- CBIELTK6YBZJU5UP2WWQEUCYKLPU6AUNZ2BQ4WWFEIE3USCIHMXQDAMA
The switchyard above prices all four rails live locally based on the deployed router state. The addresses in this list are verified against the testnet deployment record.