The canonical coverage page — per product, honestly
Six Bitcoin-family chains and eleven account-based chains, each with mainnet and testnet, 10,000+ assets in the catalogue. ECDSA (DKLS23) and EdDSA (FROST) are both native, so no chain is a second-class citizen.
Share the Trust, Guard the Keys

Long chain lists usually hide a second-class tier: chains where signing is a different code path, where testnet does not exist, or where the token standard is half supported. The list below is the production list — both curve families are native, every protocol has its testnet, and one integration reaches all of them.
Coin control, multi-account inputs and up to 150 recipients per transaction.
Unified EVM address across the EVM set; gas sponsorship on six EVM chains, Solana and Tron.
| Bitcoin family | EVM chains | Solana / Tron / others | |
|---|---|---|---|
| Signature | ECDSA (DKLS23) | ECDSA (DKLS23) | EdDSA (FROST) on Solana; both on XRP |
| Batching | 150 recipients / tx | Batch endpoint | Batch on Solana |
| Gas sponsorship | — | EIP-7702 (6 chains) | Solana fee payer · Tron token-approval |
| Address model | Per-chain formats | One unified address | Native formats |
The numbers come from the production catalogue, not a marketing deck.
Up to 150 recipients in one UTXO transaction; account chains use a batch endpoint that manages individual sends.
On account chains an asset appears after an explicit add-asset call. On UTXO chains generating the address is enough.
TRON prices in energy and bandwidth; Solana and TRON carry a static-fee model; EVM chains support sponsored transactions.
The catalogue is data-driven, so adding a protocol is roadmap work rather than a rewrite. Ask before you assume it is absent.
Get answers to commonly asked questions.
Per product — this page is the source of truth other pages link to, and a capability is listed only where it actually works. Coverage claims that differ per feature are stated on the feature's own page.
Both, for every chain — 34 networks total. Pilots run on testnet with the same API surface.
Tell us in a demo — chain onboarding is a defined internal process, and real demand moves the queue.
