Supported Assets

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 supported for this asset.
  • USDC Pair — Indicates if the asset can be traded directly against USDC for stablecoin-settled transactions.
  • Withdrawal — The ability to send crypto out of a wallet.
  • Deposit — The ability to receive crypto to a wallet.
  • Precision QTY — Decimal places for quantity.
  • Precision Price — Decimal places for price.
  • Confirms — Confirmations required on the blockchain network.
  • NY Support — If the coin is supported in New York state.
  • Tag/Memo based Asset — Networks that may require a tag/memo with the address.

Note: All listed assets support USD trading; additional trading pairs (such as USDC) are specified in the table below.

Supported Assets

SymbolNameTypeNetworkUSDC PairWithdrawalDepositPrecision QTYPrecision PriceConfirmsNY SupportTag/Memo
AAVEAaveERC20EthereumYesSupportedSupported8314YesNo
ADACardanoNativeCardanoYesSupportedSupported8415YesNo
ALGOAlgorandNativeAlgorandNoSupportedSupported841YesNo
APEApeCoinERC20EthereumNoSupportedSupported8414YesNo
ARBArbitrumNativeArbitrumNoSupportedSupported851YesNo
ATOMCosmosNativeCosmosNoUnsupportedUnsupported831YesYes
AVAXAvalancheNativeAvalancheYesSupportedSupported851YesNo
BATBasic Attention TokenERC20EthereumYesSupportedSupported8514YesNo
BCHBitcoin CashNativeBitcoin CashYesSupportedSupported826YesNo
BNBBinance CoinNativeBinance Smart ChainNoSupportedSupported821NoNo
BONKBonkSPL20SolanaNoSupportedSupported881YesNo
BTCBitcoinNativeBitcoinYesSupportedSupported826YesNo
COMPCompoundERC20EthereumYesSupportedSupported8314YesNo
CRVCurve DAOERC20EthereumYesSupportedSupported8514YesNo
DOGEDogecoinNativeDogeYesSupportedSupported856YesNo
DOTPolkadotNativePolkadotYesSupportedSupported852YesNo
ETCEthereum ClassicNativeEthereum ClassicYesSupportedSupported85372YesNo
ETHEthereumNativeEthereumYesSupportedSupported8214YesNo
FILFilecoinNativeFilecoinNoUnsupportedUnsupported84N/AYesNo
GALAGalaERC20EthereumNoSupportedSupported8614NoNo
GRTThe GraphERC20EthereumNoSupportedSupported8614YesNo
HBARHedera Hash GraphNativeHedera Hash GraphNoUnsupportedUnsupported86N/AYesYes
ICPInternet Computer ProtocolNativeInternet ComputerNoUnsupportedUnsupported84N/AYesNo
LDOLido DAOERC20EthereumNoSupportedSupported8414YesNo
LINKChainlinkERC20EthereumYesSupportedSupported8214YesNo
LTCLitecoinNativeLitecoinYesSupportedSupported826YesNo
NEARNEAR ProtocolNativeNEAR ProtocolNoUnsupportedUnsupported84N/AYesNo
NEXONexoERC20EthereumNoSupportedSupported8414NoNo
OPOptimismNativeOptimismNoSupportedSupported841NoNo
PEPEPepeERC20EthereumYesSupportedSupported8814YesNo
POLPolygon Ecosystem TokenNativePolygonYesSupportedSupported851YesNo
PUMPPumpSPL20SolanaYesSupportedSupported861NoNo
SANDThe SandboxERC20EthereumNoSupportedSupported8514YesNo
SHIBSHIBA INUERC20EthereumYesSupportedSupported8814YesNo
SOLSolanaNativeSolanaYesSupportedSupported851YesNo
SUISuiNativeSuiNoUnsupportedUnsupported85N/ANoNo
TIACelestiaNativeCelestiaNoUnsupportedUnsupported83N/ANoYes
TONToncoinNativeThe Open NetworkNoUnsupportedUnsupported85N/ANoNo
TRUMPOfficial TrumpSPL20SolanaYesSupportedSupported841NoNo
TRXTronNativeTronNoSupportedSupported861NoNo
UNIUniswapERC20EthereumYesSupportedSupported8414YesNo
USDCUSD CoinERC20Ethereum, Solana, PolygonNoSupportedSupported6514NoNo
USDTUSD TetherERC20EthereumNoSupportedSupported6514NoNo
WIFDog Wif HatSPL20SolanaYesSupportedSupported851YesNo
XLMStellarNativeStellarNoUnsupportedUnsupported86N/AYesYes
XRPRippleNativeRippleYesSupportedSupported861YesYes

Additional Details

Use the Verify Wallet Address API to verify the validity of an address for a given coin. Some assets/networks have additional required specifications.

AssetAdditional Specifications
BTCBakkt Trade supports three Bitcoin wallet formats for v2 wallets: Legacy (P2PKH) addresses starting with 1 (e.g. 1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2); P2SH addresses starting with 3 (e.g. 3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy); Native SegWit (Bech32) addresses starting with bc1 (e.g. bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq).
BCHFor BCH network transactions, Bakkt exclusively supports legacy addresses and does not support the CashAddr format or wallets that begin with bitcoincash or q.
XRPMay require a tag/memo unique identifier along with the blockchain address to ensure funds are credited to the client account.
ATOMMay require a tag/memo unique identifier along with the blockchain address to ensure funds are credited to the client account.
XLMMay require a tag/memo unique identifier along with the blockchain address to ensure funds are credited to the client account.

Jurisdiction Restrictions

Bakkt controls which assets can be traded in specific jurisdictions. Clients must work with Bakkt Support to understand jurisdiction-level trading restrictions and ensure customers can access permitted instruments in their location.

In the Bakkt API, instruments (also called symbols) are the digital asset types that Bakkt offers. The Request the Instruments List endpoint and AWS S3 reports use these symbols in lists, reports, and notifications.

Retrieving the Instruments List

You can retrieve the current list of supported instruments programmatically using the Instruments API endpoint.

curl --request GET \
  --url https://api.bakkt.com/apex-crypto/api/v2/instruments \
  --header 'Authorization: API-Key <YOUR_API_KEY>' \
  --header 'Content-Type: application/json'

Expected Response (200 OK):

{
  "instruments": [
    {
      "symbol": "BTCUSD",
      "name": "Bitcoin",
      "baseCurrency": "BTC",
      "quoteCurrency": "USD"
    }
  ]
}

Did this page help you?