LayerHopdocs

Reference

Providers

The liquidity providers behind LayerHop — Jupiter, Relay, deBridge, 0x, LI.FI — what each covers, how fees and tracking work, and what is coming.

Open in ClaudeOpen in ChatGPT

LayerHop routes through these providers. Each one is queried only for routes it supports; see Providers & ranking for how the winner is chosen.

Coverage at a glance#

Provider provider id Routes Tx type Tracking id
Jupiter jupiter Solana → Solana svm, submitViaApi — (confirm on chain)
Relay relay EVM → EVM (same or cross-chain), EVM → Solana evm source tx hash or Relay request id
deBridge debridge Cross-chain between all supported chains, incl. Solana → EVM evm or svm source tx hash or DLN order id
0x zerox Same-chain on EVM evm — (confirm on chain)
LI.FI lifi All supported chain pairs evm or svm source tx hash

Jupiter#

Solana's swap aggregator. LayerHop uses Jupiter's order-and-execute flow, which returns a quote together with a ready-to-sign transaction.

  • Routes: Solana same-chain swaps between different tokens.
  • Transactions: always submitViaApi: true. RFQ and gasless routes are co-signed by Jupiter and only land through its execute endpoint. See the submitViaApi flow.
  • Quote lifetime: at most 30 s (shorter if the RFQ quote expires sooner).
  • LayerHop fee: Jupiter's referral program, 50–255 bps; Jupiter keeps 20%. Channel fees below 50 bps are not charged on Jupiter routes (ourFeeBps: 0).
  • Tracking: nothing to track off-chain; status is always unknown.

Relay#

A cross-chain and same-chain execution network covering EVM chains and Solana.

  • Routes: any EVM source to any supported destination (EVM or Solana).
  • Not supported: Solana as the source — Relay returns raw Solana instructions rather than a signable transaction for those routes, so LayerHop does not quote them yet.
  • Transactions: evm, often with an ERC-20 approval.
  • Quote lifetime: 30 s.
  • LayerHop fee: Relay app fees (bps of input), accrued in USDC.
  • Tracking: by source transaction hash or Relay request id.

deBridge#

deBridge's DLN is an intent-based cross-chain network: makers fill orders on the destination chain from their own liquidity.

  • Routes: cross-chain only, between Ethereum, Arbitrum, Base, Optimism, BNB Chain, Polygon and Solana, in both directions.
  • Transactions: evm (with approval for ERC-20 input; value includes deBridge's fixed fee in the native coin) or svm for Solana sources.
  • Quote lifetime: 30 s. deBridge asks for orders to be submitted within about 30 s of building.
  • LayerHop fee: affiliate fee, up to 1000 bps, paid on the source chain.
  • Tracking: by source transaction hash (EVM hash or Solana signature) or DLN order id. Fills commonly land in seconds.

0x#

EVM DEX aggregator (Swap API v2, AllowanceHolder flow).

  • Routes: same-chain swaps on the supported EVM chains.
  • Requires: the API operator's ZEROX_API_KEY. Without it, 0x reports UNAUTHORIZED in errors.
  • Transactions: evm; ERC-20 sells carry an approval whose spender is 0x's AllowanceHolder contract (not to).
  • Quote lifetime: 30 s.
  • LayerHop fee: 0x swap fee in the sell token, up to 1000 bps. 0x may also charge its own fee on some pairs, already reflected in the output.
  • Tracking: nothing to track off-chain; status is always unknown.

LI.FI#

A bridge and DEX aggregator. LayerHop uses it as a fallback because it adds its own fee on top, so it tends to win only when nothing else routes the pair well.

  • Routes: every pair of supported chains, including same-chain and Solana source.
  • Transactions: evm (with approval when needed) or svm.
  • Quote lifetime: 60 s.
  • LayerHop fee: LI.FI integrator fee, only once the integrator is registered with LI.FI; until then ourFeeBps: 0.
  • Tracking: by source transaction hash.

Mayan#

Coming soon

Mayan (Solana ↔ EVM via Swift / MCTP). Quoting is implemented but transaction building is not, so Mayan is disabled and never appears in quotes.

Not available#

  • Odos shut down its service on 2026-07-30 and is not loaded. A second EVM same-chain source (KyberSwap or 1inch) is planned.
  • mock is a deterministic test provider, only present when an API runs with LAYERHOP_ENABLE_MOCK=1. Its transactions are dummies; never broadcast them.

Note

Provider limits and fee terms change. LayerHop reports what each quote actually charges in fees.ourFeeBps; treat the numbers above as a guide, not a guarantee.