Supported Chains

Curve Abstraction

The SDK separates chains by their signing curve. When you call sign(), sendAssets(), or any enclave method, you pass the share for the curve that chain uses — not a chain-specific share. This means one wallet covers all chains.

Supported Mainnets

Supported Testnets

Choosing the Right Share

Use WALLET_CHAINS[chain].curve to look up which share to pass at runtime:

import { WALLET_CHAINS, WalletChain } from "@tatumio/wallet-sdk";

const chain = WalletChain.SOLANA_MAINNET;
const curve = WALLET_CHAINS[chain].curve; // "ED25519"

await client.sendAssets({
  body: {
    share: shares[curve].share,  // shares.ED25519.share
    chain,
    to: "SolanaAddressHere",
    token: "NATIVE",
    amount: "0.5",
  },
});

Chain Configuration

getWalletChainConfig(chain) returns the full config object for a chain:

import { getWalletChainConfig, WalletChain } from "@tatumio/wallet-sdk";

const config = getWalletChainConfig(WalletChain.ETHEREUM_MAINNET);
// {
//   chainId: "eip155:1",
//   curve: "SECP256K1",
//   requiresRpcUrl: false,
//   tatumRpcNetwork: "ethereum-mainnet"
// }

RPC Handling

Automatic RPC Resolution

For chains where requiresRpcUrl is false, the SDK automatically resolves a Tatum RPC URL using your API key. You don't need to pass rpcUrl.

Check getWalletChainConfig(chain).requiresRpcUrl for the selected chain before you build a request.

Custom RPC URLs

For chains where requiresRpcUrl is true, supply an rpcUrl in the call body:

await client.sendAssets({
  body: {
    share: shares.SECP256K1.share,
    chain: WalletChain.TRON_MAINNET,
    to: "TRecipientAddress",
    token: "NATIVE",
    amount: "10",
    rpcUrl: "https://api.trongrid.io",
  },
});

You can also pass a custom rpcUrl on any chain to override the automatic one.