Chains
RAVN spans EVM chains, Solana, and native Bitcoin. One integration covers all of them. Use the chain ID in every request.EVM
Non-EVM
Native coin on any EVM chain uses the sentinel address
0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE. Amounts are always strings in the token’s smallest
unit (wei, lamports, satoshis).Tempo’s native currency is literally
USD (18 decimals): a non-transferable unit of account,
not a market-priced asset, so no venue lists it as swappable, only its ERC-20 tokens
(USDC.e, pathUSD, USDT0, PRIME) route. Its explorer also has a dedicated payment receipt view at
https://explore.tempo.xyz/receipt/{txHash}, alongside the usual /tx/{txHash} transaction page.
And Tempo’s PRIME is Hastra’s liquid-staking receipt for Figure’s tokenized HELOC pool, not
Echelon Prime / Parallel’s governance token of the same ticker.NO_LIQUIDITY if none can.
Venues
RAVN aggregates the venues below. On every quote, the venues eligible for that specific route, never all of them at once, are queried in parallel and the best real output wins: Most venues return one fixed execution type; a few return different types depending on the source chain or execution mode, noted per row below. Theid column is the
value you’ll see in venue.id on a quote and /health, and what excludeVenues takes. Exclude and identify venues by id, not name: RAVN’s own multi-step routes are all named RAVN (venue.id compose, or relay for Relay with a DEX on arrival).
Every venue delivers the asset the user asked for, never a wrapped copy. The one wrap in the
list, Layerswap, exists only for pairs where WBTC itself is the requested output. RAVN runs no
bridge of its own. NEAR Intents moves coins in and out through its own bridge, so on its routes
the deposit is held as a matching token on NEAR for the minutes the swap takes. RFQ and gasless
venues let the user swap with zero native gas, because they sign an off-chain message and a
solver covers the gas.
THORChain with BTC as the source requires THORChain’s memoless feature, which THORChain can
disable network-wide with its
HALTMEMOLESS flag, and currently has. RAVN checks that flag on
every quote and simply leaves THORChain out of the race while it is set, so you never receive a
quote that cannot execute.This changes nothing you need to handle: selling BTC still works, because Chainflip, Relay
and NEAR Intents all serve it and keep competing. THORChain sending funds to native BTC is
unaffected either way: that path uses an ordinary memo with no registration.Rift enforces no minimum output. It picks its route and rate when the deposit lands, so the
user can receive more or less than quoted. Its quotes carry
slippage.noMinimum: true: show
that to the user before they send. Rift races only when you leave slippageBps out (Auto); a
request with its own slippage limit never gets a Rift quote.Private swaps
Setconfidential: true on /quote and the race narrows to the venues
with a private settlement path, NEAR Intents (Confidential Intents) and Houdini Swap, so the
deposit and the payout can’t be linked on-chain. You get NO_LIQUIDITY rather than a public fill
if neither can quote. Houdini Swap only ever races on these requests. It settles through two of
its partner exchanges in turn, which hold the funds for the minutes to an hour the swap takes,
and prices about 3% below spot, so it usually wins only where NEAR Intents can’t quote. See
confidential on /quote for its compliance rules.
Settlement models
RFQ market makers
Professional market makers quote a firm, signed price. The user signs and a solver settles.
Zero slippage, zero gas.
Intent networks
The user expresses an intent, or deposits the origin asset, and solvers compete to fill and
deliver on the destination.
Solver and relayer networks
Relayers fill on the destination chain and deliver the canonical asset. This gives fast
cross-chain execution without bridging.
Validator-vault networks
A decentralized, threshold-signed validator network custodies a deposit channel and swaps
against its own AMM or vault liquidity. No single custodian ever holds the funds.
On-chain DEX aggregators
One transaction the user signs and broadcasts, routed across on-chain pools by the
aggregator’s own router. Same-chain only. The transaction hash is the swap’s settlement
proof, so you report it to
/status yourself./health endpoint always reports the
current live venue set.