KarpelesLab / libwallet / 24679627981

25%

Build Type

push

github

Committed by MagicalTux

Commit Message

Swap:availability — per-chain-id gating (not per-family)

Original 0.3.19 draft of this endpoint only branched on the chain
family ("solana" / "evm" / "bitcoin"). Not precise enough: Jupiter
and dFlow only route on Solana mainnet (devnet + testnet should
not show a Swap button), and 1inch's Classic Swap API covers a
specific list of EVM chain ids — anything else gets a 404 upstream.

Changes:
- AvailabilityResult.Chain → Network, formatted as "<type>.<chainId>"
  to match Asset:list's key convention ("evm.1", "solana.mainnet-beta",
  "bitcoin.dogecoin"). SwapAvailability exposes chainFamily /
  chainId convenience getters.
- Solana: only mainnet-beta is eligible; devnet / testnet get
  unsupported_chain.
- EVM: gated against oneInchSupportedChains — 1 / 10 / 56 / 100 /
  137 / 250 / 324 / 8453 / 42161 / 43114 / 59144. Chains outside
  that set return unsupported_chain regardless of API key.
- Bitcoin-family (bitcoin, bitcoin-cash, litecoin, dogecoin, etc.):
  unchanged, always unsupported_chain.

Tests cover all three families, Solana cluster variants, three EVM
chain ids in coverage, an EVM chain outside coverage, and the
chain-miss-beats-key-miss precedence.

Pre-release cleanup — 0.3.18 didn't ship this endpoint, so the
chain → network field rename is a same-version iteration.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Coverage Stats

15 of 17 new or added lines in 1 file covered. (88.24%)

1 existing line in 1 file now uncovered.

2529 of 11899 relevant lines covered (21.25%)

68.33 hits per line