Supported Assets & Wallet Types
Definition Guide:
- Name - The Name of the crypto coin.
- Symbol - The ticker symbol that represents the crypto coin.
- Type - The type of token on the blockchain layer.
- Network - The blockchain network that are supported for this asset. For more details information please see this document Address Types Supported
- Withdrawal - The ability to send crypto coin out of a wallet.
- Deposit - The ability to receive crypto coin to a wallet.
- Precision Quantity - The number of decimal places used to represent the coin's quantity.
- Precision Price - The number of decimal places used to calculate and display the coin's price.
- Confirms - The number of confirmations required to be accepted by a blockchain network.
- NY Support - If the coin is supported in the state of New York.
- Tag/Memo based Asset These networks may require a unique identifier along with the blockchain address to ensure the crypto funds are credited to the client account. Typically exchanges will enforce the use of tag but sending to a self custody wallet no tag may be required.
| # | Name | Symbol | Type | Network | Withdrawal | Deposit | Precision QTY | Precision Price | Confirms | NY Support | Tag/Memo based Asset |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Aave | AAVE | ERC20 | Ethereum | Unsupported | Unsupported | 8 | 3 | N/A | Yes | No |
| 2 | Algorand | ALGO | Native | Algorand | Supported | Supported | 8 | 4 | 1 | Yes | No |
| 3 | ApeCoin | APE | ERC20 | Ethereum | Unsupported | Unsupported | 8 | 4 | N/A | Yes | No |
| 4 | Arbitrum | ARB | Native | Arbitrum One | Unsupported | Unsupported | 8 | 5 | N/A | Yes | No |
| 5 | Avalanche | AVAX | Native | Avalanche | Supported | Supported | 8 | 5 | 20 | Yes | No |
| 6 | Basic Attention Token | BAT | ERC20 | Ethereum | Unsupported | Unsupported | 8 | 5 | N/A | Yes | No |
| 7 | Bitcoin | BTC | Native | Bitcoin | Supported | Supported | 8 | 2 | 6 | Yes | No |
| 8 | Bitcoin Cash | BCH | Native | Bitcoin Cash | Supported | Supported | 8 | 2 | 6 | Yes | No |
| 9 | Bonk | BONK | SPL20 | Solana | Unsupported | Unsupported | 8 | 8 | N/A | Yes | No |
| 10 | Cardano | ADA | Native | Cardano | Supported | Supported | 8 | 4 | 15 | Yes | No |
| 11 | Celestia | TIA | Native | Celestia | Unsupported | Unsupported | 8 | 3 | N/A | No | No |
| 12 | Chainlink | LINK | ERC20 | Ethereum | Supported | Supported | 8 | 2 | 14 | Yes | No |
| 13 | Compound | COMP | ERC20 | Ethereum | Unsupported | Unsupported | 8 | 3 | N/A | Yes | No |
| 14 | Cosmos | ATOM | Native | Cosmos | Unsupported | Unsupported | 8 | 3 | 1 | Yes | Yes |
| 15 | Curve DAO | CRV | ERC20 | Ethereum | Unsupported | Unsupported | 8 | 5 | N/A | Yes | No |
| 16 | Dog Wif Hat | WIF | SPL20 | Solana | Unsupported | Unsupported | 8 | 5 | N/A | Yes | No |
| 17 | Dogecoin | DOGE | Native | Doge | Supported | Supported | 8 | 5 | 6 | Yes | No |
| 18 | Ethereum | ETH | Native | Ethereum | Supported | Supported | 8 | 2 | 14 | Yes | No |
| 19 | Ethereum Classic | ETC | Native | Ethereum Classic | Supported | Supported | 8 | 5 | 372 | Yes | No |
| 20 | Filecoin | FIL | Native | Filecoin | Unsupported | Unsupported | 8 | 4 | N/A | Yes | No |
| 21 | Gala | GALA | ERC20 | Ethereum | Unsupported | Unsupported | 8 | 6 | N/A | No | No |
| 22 | Hedera Hash Graph | HBAR | Native | Hedera Hash Graph | Unsupported | Unsupported | 8 | 6 | N/A | Yes | No |
| 23 | Internet Computer Protocol | ICP | Native | Internet Computer | Unsupported | Unsupported | 8 | 4 | N/A | Yes | No |
| 24 | Lido DAO | LDO | ERC20 | Ethereum | Unsupported | Unsupported | 8 | 4 | N/A | Yes | No |
| 25 | Litecoin | LTC | Native | Litecoin | Supported | Supported | 8 | 2 | 6 | Yes | No |
| 26 | NEAR Protocol | NEAR | Native | NEAR Protocol | Unsupported | Unsupported | 8 | 4 | N/A | Yes | No |
| 27 | Official Trump | TRUMP | SPL20 | Solana | Unsupported | Unsupported | 8 | 4 | N/A | No | No |
| 28 | Optimism | OP | Native | Optimism | Unsupported | Unsupported | 8 | 4 | N/A | No | No |
| 29 | Pepe | PEPE | ERC20 | Ethereum | Supported | Supported | 8 | 8 | 14 | Yes | No |
| 30 | Polkadot | DOT | Native | Polkadot | Supported | Supported | 8 | 5 | 2 | Yes | No |
| 31 | Polygon Ecosystem Token | POL | ERC20 | Ethereum | Unsupported | Unsupported | 8 | 5 | N/A | Yes | No |
| 32 | Ripple | XRP | Native | Ripple | Unsupported | Unsupported | 8 | 5 | 1 | Yes | Yes |
| 33 | SHIBA INU | SHIB | ERC20 | Ethereum | Supported | Supported | 8 | 8 | 14 | Yes | No |
| 34 | Solana | SOL | Native | Solana | Supported | Supported | 8 | 5 | 1 | Yes | No |
| 35 | Stellar | XLM | Native | Stellar | Unsupported | Unsupported | 8 | 6 | N/A | Yes | Yes |
| 36 | Sui | SUI | Native | Sui | Unsupported | Unsupported | 8 | 5 | N/A | No | No |
| 37 | The Graph | GRT | ERC20 | Ethereum | Unsupported | Unsupported | 8 | 6 | N/A | Yes | No |
| 38 | The Sandbox | SAND | ERC20 | Ethereum | Unsupported | Unsupported | 8 | 5 | N/A | Yes | No |
| 39 | Toncoin | TON | Native | The Open Network | Unsupported | Unsupported | 8 | 5 | N/A | No | No |
| 40 | Uniswap | UNI | ERC20 | Ethereum | Unsupported | Unsupported | 8 | 4 | N/A | Yes | No |
| 41 | USD Coin | USDC | ERC20 | Ethereum | Supported | Supported | 6 | 5 | 14 | No | No |
Additional Details
Use the Verify Wallet Address to verify the validity of an address for a given coin. Some Assets/Networks have additional required specifications, see these below.
| Asset | Additional Specifications |
|---|---|
| BTC | Bakkt Trade supports three Bitcoin wallet formats for v2 wallets, which have been standard since 2019: 1. Legacy (P2PKH) Addresses: These start with the number 1. Example: 1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN22. P2SH Addresses: Identified by starting with the number 3. Example: 3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy3. Native SegWit (Bech32) Addresses: Beginning with bc1 Example: bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq |
| BCH | For BCH network transactions, Bakkt exclusively supports legacy addresses and does NOT support the CashAddr format of BCH or wallets that begin with bitcoincash or q. |
| XRP | These networks may require a tag/memo unique identifier along with the blockchain address to ensure the crypto funds are credited to the client account. |
| ATOM | These networks may require a tag/memo unique identifier along with the blockchain address to ensure the crypto funds are credited to the client account. |
| XLM | These networks may require a tag/memo unique identifier along with the blockchain address to ensure the crypto funds are credited to the client account. |