fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
38 lines
1.8 KiB
Markdown
38 lines
1.8 KiB
Markdown
# 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.
|