# All Supported Blockchains

Every supported chain, one integration — both curve families native to the same MPC core.

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. Vaultody's list is
the production list. ECDSA (DKLS23) and EdDSA (FROST) are both first-class, so Solana is not a
bolt-on behind a different signer, and every protocol carries mainnet and testnet records — what
you build against on testnet is what ships. The current grid lives on
[What we support](/what-we-support).

## The same objects everywhere

Vaults, vault accounts, addresses and transaction requests have the same shape on every protocol:
the chain is a parameter, not a second integration.

- **One unified address across the EVM set**, native formats on the Bitcoin family, TRON, XRP and
  Solana.
- **A catalogued asset list with USD pricing**, so balances and reporting work without you
  maintaining a token list.
- **Mainnet and testnet records per protocol**, on the same API surface.

## Where the families genuinely differ

- **Bitcoin family (UTXO)** — coin control, multi-account inputs, and up to 150 recipients in a
  single transaction.
- **Account-based chains** — an asset appears in a balance once it is registered against the
  account; on UTXO chains generating the address is enough.
- **Fees** — TRON prices in energy and bandwidth, Solana and TRON carry a static-fee model, and
  EVM chains support sponsored transactions. Budgeting logic that assumes one fee model needs a
  per-family branch.

Plan for those shapes and the rest of your integration is one code path.

## FAQ

**Are all chains equally supported?**
In the way that matters, yes: both curve families are native to the MPC core, so no chain sits
behind a different signer. What differs is the chain's own model.

**Can we pilot on testnet?**
Every protocol has mainnet and testnet records, and a pilot runs on testnet against the same API
surface it will use in production.

## Related

- [What we support](/what-we-support)
- [Unified EVM Address](/features/unified-evm-address)
- [Integrations: Blockchains](/integrations/protocols)
- [Key Management](/features/key-management)