# Jumper Support Matrix for Tezos / Cross-Chain

Documentation of Jumper API/SDK support for chains used in Tezos CCIP DON onboarding and fallback routing.

## Purpose

- **Jumper**: Cross-chain routing and UX (quote, route selection, execution). Used alongside LiFi; route selection logic can try Jumper first for supported chains, then fall back to LiFi or direct CCIP/adapter.
- **Scope**: ChainID 138, ALL Mainnet (651940), Etherlink (42793), Tezos (L1 or as Etherlink EVM).

## Verification steps

1. **Check Jumper supported chains**
   - Jumper API/SDK documentation: https://jumper.exchange/ or current Jumper docs.
   - Query or list supported chain IDs.

2. **Record support**

| Chain        | Chain ID | Jumper supported | Fallback |
|-------------|----------|------------------|----------|
| ChainID 138 | 138      | Verify           | LiFi (if not in LiFi: direct CCIP/adapter) |
| ALL Mainnet | 651940   | Verify           | AlltraAdapter, direct |
| Etherlink   | 42793    | Verify           | EVMAdapter(42793), direct CCIP or custom relay |
| Tezos L1    | N/A (non-EVM) | Verify (if Jumper has Tezos) | TezosAdapter + relay only |

3. **If Jumper does not support 138 / 651940 / 42793 / Tezos**
   - Use **LiFi + direct adapter/CCIP** for those chains.
   - Jumper only for chains where Jumper returns routes; otherwise route selection uses LiFi or direct bridge/adapter.

## Route selection logic (reference)

1. If destination/source in Jumper supported list → try Jumper getQuote / getRoute.
2. If Jumper fails or not supported → try LiFi (if chain in LiFi supported list).
3. If LiFi not supported → use direct bridge/adapter (CCIP, EVMAdapter, TezosAdapter, AlltraAdapter).

## Env (if Jumper requires API key)

- `JUMPER_API_KEY` (optional): Set if Jumper provides higher rate limits or required access.