The following tables list the blockchain ledgers and tokens supported by Ripple Custody, along with the types of operations supported for each.
Testnet names are subject to change, for example, when a reset occurs on the ledger. If a testnet is reset, the month-year of the reset is appended to the name, for example: xrpl-testnet-april-2024.
The following table gives an overview of the supported networks and operations for Bitcoin-type ledgers in Ripple Custody.
| Ledger | Symbol | Networks | Send/ Receive | Stake | Smart Contract Calls | Cancel/Replace Transaction | Empty Account | Send to Multiple Destinations |
|---|---|---|---|---|---|---|---|---|
| Bitcoin | BTC | Mainnet / Testnet3 | Yes | N/A | N/A | Yes | Yes | Yes |
| Bitcoin Cash | BCH | Mainnet / Testnet | Yes | N/A | N/A | Yes | Yes | Yes |
| Litecoin | LTC | Mainnet / Testnet | Yes | N/A | N/A | Yes | Yes | Yes |
| Dogecoin | DOGE | Mainnet / Testnet | Yes | N/A | N/A | Yes | Yes | Yes |
| Dash | DASH | Mainnet / Testnet | Yes | N/A | N/A | Yes | Yes | Yes |
In the case of Bitcoin-type ledgers, Ripple Custody does not support transactions where the destination is a pay-to-taproot (P2TR) address.
The following table gives an overview of the supported networks and operations for EVM ledgers in Ripple Custody.
| Ledger | Symbol | Networks | Send/ Receive | Stake | Smart Contract Calls | Cancel/Replace Transaction | Empty Account | Send to Multiple Destinations |
|---|---|---|---|---|---|---|---|---|
| Arbitrum | ARB | Mainnet / Sepolia | Yes | N/A | Yes | Yes | Yes ** | No |
| Avalanche C-Chain | AVAX | Mainnet / Fuji | Yes | N/A | Yes | Yes | Yes ** | No |
| Base | ETH | Mainnet / Sepolia | Yes | N/A | Yes | Yes | Yes ** | No |
| Binance Smart Chain | BNB | Mainnet / Testnet | Yes | N/A | Yes | Yes | Yes ** | No |
| Celo | CELO | Mainnet | Yes | N/A | Yes | Yes | Yes ** | No |
| Ethereum | ETH | Mainnet / Holesky / Sepolia | Yes | N/A | Yes | Yes | Yes** | No |
| Linea | ETH | Mainnet | Yes | N/A | Yes | Yes | Yes ** | No |
| Optimism | OP | Mainnet / Sepolia | Yes | N/A | Yes | Yes | Yes ** | No |
| Polygon | MATIC | Mainnet / Amoy | Yes | N/A | Yes | Yes | Yes ** | No |
| Scroll | ETH | Mainnet | Yes | N/A | Yes | Yes | Yes ** | No |
| Sei | SEI | Mainnet | Yes | N/A | Yes | Yes | Yes ** | No |
Notes:
- For Ethereum and other EVM ledgers, all assets that follow the ERC-20, ERC-721, and ERC-1155 (or chain-equivalent) standard specifications are supported.
- ERC-20 tokens must implement the
IERC20Metadatainterface — that is, the contract must expose thename(),symbol(), anddecimals()methods. Contracts that omit any of these methods are not supported. This applies to all EVM ledgers. See ERC-20 metadata requirement for details. - Wallet emptying is possible for native coin transfers, by calculating the expected fee and subtracting it from the sent amount.
- For the payloads required to add these EVM ledgers, see Dynamic ledger payloads.
The following table gives an overview of the supported networks and operations for other ledgers in Ripple Custody.
| Ledger | Symbol | Networks | Send/ Receive | Stake | Smart Contract Calls | Cancel/Replace Transaction | Empty Account | Send to Multiple Destinations |
|---|---|---|---|---|---|---|---|---|
| Algorand | ALGO | Mainnet / Testnet | Yes | N/A | N/A | No | No | No |
| Cardano | ADA | Mainnet / Preprod | Yes | Yes | N/A | No | Yes | Yes |
| Hedera | HBAR | Mainnet / Testnet Jan 2024 | Yes | N/A | N/A | No | No | No |
| Polkadot | DOT | Mainnet / Westend | Yes | Yes | N/A | No | No | No |
| Solana | SOL | Mainnet / Devnet | Yes | No | N/A | No | No | Yes |
| Stellar | XLM | Mainnet / Testnet Sept 2024 | Yes | N/A | N/A | No | No | No |
| Tezos | XTZ | Mainnet / Ithaca | Yes | Yes | Yes (with limitations) | No | No | No |
| Tron | TRX | Mainnet / Testnet | Yes | No | N/A | No | No | No |
| XRPL | XRP | Mainnet / Testnet Aug 2024 | Yes | N/A | N/A | No | No | No |
Notes:
- For Hedera ledgers, fungible and non-fungible tokens are supported.
- For XRPL ledgers, fungible tokens are supported.
The following table gives an overview of native currencies by ledger, with the number of decimal places the currency is divisible by to arrive at its smallest denomination. The currencies listed apply to the ledger's mainnet.
This list is given for guidance only, and may be subject to change. You must check the latest ledger and network documentation for up-to-date information.
| Ledger | Currency | Smallest denomination | Decimal places |
|---|---|---|---|
| Algorand | ALGO | MicroAlgo | 6 |
| Bitcoin | BTC | Satoshi | 8 |
| Cardano | ADA | Lovelace | 6 |
| Ethereum | ETH | Wei | 18 |
| Hedera | HBAR | Tinybar | 8 |
| Polkadot | DOT | Planck | 10 |
| Stellar | XLM | Stroop | 7 |
| Solana | SOL | Lamport | 9 |
| Tezos | XTZ | Microtez | 6 |
| Tron | TRX | Sun | 6 |
| XRPL | XRP | Drop | 6 |
ERC-20 tokens are only supported if they implement the IERC20Metadata interface.
The ERC-20 token contract must expose all three of the following methods:
| Method | Description |
|---|---|
name() | Returns the name of the token (e.g., "USD Coin"). |
symbol() | Returns the ticker symbol (e.g., "USDC"). |
decimals() | Returns the number of decimal places (e.g., 6). |
These methods were optional in the original EIP-20 specification. Since OpenZeppelin Contracts 4.x, they are defined in the IERC20Metadata interface and are implemented by virtually all modern tokens.
Contracts deployed before the IERC20Metadata standard that omit one or more of these methods are not supported. If such a token is sent to a Ripple Custody managed address, the system will not emit detected or confirmed events for it and the token will not appear in the platform.
Expected behavior for non-compliant tokens:
- No
detectedorconfirmedevents are emitted. - The token does not appear in account balances or transaction history.
- No manual intervention or on-call action is required — the token is silently ignored.
This requirement applies to all EVM-compatible ledgers (Ethereum, Polygon, Arbitrum, Avalanche C-Chain, Base, Binance Smart Chain, Celo, Linea, Optimism, Scroll, and Sei).
The supported blockchain ledgers have the following limitations:
- Due to a Solana network requirement, support for cold storage is limited.
- EVM ledgers require either Geth nodes with traces enabled, or BESU nodes.
- Sending BTC to Taproot addresses is not supported.