Supported Blockchains & Digital Assets
Tatum supports many blockchain protocols (testnet + mainnet) and nearly limitless digital assets in a single, unified SDK. This page gives an overview of all of the supported blockchains in Tatum, which features they support, and which assets are supported natively in Tatum's virtual accounts.
Not all blockchains function identically, so Tatum supports different features depending on the technical constraints of each blockchain. In the table below, you can compare which broad feature sets are supported on which blockchains.
The table does NOT include ALL supported features on each blockchain. It is simply an overview of some of the most commonly used and requested features for the purpose of comparison between chains.
Scroll to the right in the table to view all included features.
Blockchain / asset | API code | RPC node access | Basic blockchain operations | Notifications | NFT minting | NFT marketplaces + auctions | Gas Pump | Virtual accounts | Data API | Full History | Debug, trace, internal |
 | ALGO | ✓ | ✓ | | ✓ | | | ✓ | ✓ | ✓ | |
 | ARB | ✓ | | | | | | | | ✓ | ✓ |
 | AURORA | ✓ | | | | | | | | | |
 | AVAX | ✓ | | | | | | | | ✓ | ✓ |
 | BTC | ✓ | ✓ | ✓ | | | | ✓ | ✓ | ✓ | |
 | BCH | ✓ | ✓ | ✓ | | | | ✓ | | ✓ | |
 | BNB | ✓ | ✓ | | | | | ✓ | | ✓ | |
| BSC | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | ✓ | ✓ |
 | ADA | ✓ | | | | | | | | ✓ | |
 | CELO | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
 | CRO | ✓ | | | | | | | | ✓ | |
 | DOGE | ✓ | ✓ | ✓ | | | | ✓ | ✓ | ✓ | |
 | EGLD | ✓ | ✓ | | | | | ✓ | | ✓ | |
 | EOS | ✓ | | | | | | | | ✓ | ✓ |
 | ETH | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
 | ETC | ✓ | | | | | | | | ✓ | ✓ |
 | FTM | ✓ | | | | | | | | ✓ | |
 | FLOW | ✓ | ✓ | | ✓ | | | ✓ | | ✓ | |
 | GNO | ✓ | | | | | | | | ✓ | |
 | ONE | ✓ | ✓ | | ✓ | ✓ | ✓ | ✓ | | ✓ | |
 | KLAY | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | ✓ | |
 | KCS | ✓ | ✓ | | ✓ | | | ✓ | | ✓ | |
 | KSM | ✓ | | | | | | | | ✓ | |
 | LSK | ✓ | | | | | | | | ✓ | |
 | LTC | ✓ | ✓ | ✓ | | | | ✓ | ✓ | ✓ | |
 | NEAR | ✓ | | | | | | | | ✓ | |
 | OASIS | ✓ | | | | | | | | ✓ | |
 | OPTIMISM | ✓ | | | | | | | | ✓ | ✓ |
 | PALM | ✓ | | | | | | | | ✓ | |
 | DOT | ✓ | | | | | | | | ✓ | |
 | MATIC | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
 | RSK | ✓ | | | | | | | | ✓ | |
 | SOL | ✓ | ✓ | ✓ | ✓ | ✓* | | ✓ | ✓ | ✓ | |
 | XLM | ✓ | ✓ | | | | | ✓ | ✓ | ✓ | |
 | TEZOS | ✓ | | | | | | | | ✓ | |
 | TRON | ✓ | ✓ | ✓ | ✓ | | ✓ | ✓ | ✓ | ✓ | ✓ |
 | VET | ✓ | ✓ | | | | | | | ✓ | |
 | XDC | ✓ | ✓ | | | | ✓ | | | ✓ | |
 | XRP | ✓ | ✓ | ✓ | | | | ✓ | ✓ | ✓ | |
 | ZCASH | ✓ | | | | | | | | ✓ | |
 | ZIL | ✓ | | | | | | | | ✓ | |
* In alpha
- RPC node access - Indicates whether or not it is possible to call the RPC nodes of the given blockchain directly.
- Basic blockchain operations - If a chain supports basic blockchain operations in Tatum, you can generate wallets, private keys, account addresses, transfer tokens, and other such operations using Tatum's abstracted API endpoints.
- Notifications - Indicates whether Tatum's Notification Station feature is supported. (Note: even if Notification Station is not supported, it is still possible to set up webhook notifications on any blockchain that supports virtual accounts).
- NFT minting - If NFT minting is supported on a blockchain, it means that you can deploy NFT smart contracts and/or mint NFTs on the given blockchain with Tatum's abstracted API endpoints.
- NFT marketplaces + auctions - Indicates whether Tatum's instantly deployable NFT marketplace and auction smart contracts are available on the given blockchain.
- Data API - Indicates whether advanced data lookup operations that require indexing of the entire blockchain are available (e.g. get NFTs by address, get NFTs by collection, etc.).
- Full history - Indicates whether the entire historical data of the blockchain is available
- Debug, trace, internal - Indicates whether we support blockchain-specific methods
- API code - The code representing the given blockchain in Tatum's API. This code is used in all operations where it is necessary to specify the name of the chain on which you are working.
In addition to supporting blockchains, Tatum also natively supports many digital assets that can be used instantly with virtual accounts.
It is important to note that even if an ERC-20 (or equivalent, e.g. BEP-20 or TRC-20) asset is not natively supported in Tatum, you can still use it with virtual accounts. For more on how to do so, please refer to this guide.
All digital assets on a given blockchain are supported by the wallets generated within Tatum. This means if you want to generate a wallet to hold an ERC-20 like USDT on Ethereum, you would generate the exact same wallet as you would use to hold ETH. The same applies to ERC-721 and ERC-1155 tokens or their equivalents on any supported blockchain.
The following parameters are included in the table below:
- Asset - the name of the digital asset
- Base chain - the blockchain on which the asset exists
- API code - the code representing the given asset in Tatum's API. This code is used in all operations where it is necessary to specify the name of the asset.
Asset | Base chain | API code |
 | ETH | BAT |
 | BSC | BADA |
 | BSC | BUSD_BSC |
| ETH | BUSD |
| CELO | CEUR |
 | ETH | LINK |
 | ETH | XCON |
| CELO | CUSD |
| FLOW | FUSD |
 | ETH | FREE |
 | MATIC | GAMEE |
 | BSC | GMC_BSC |
| ETH | GMC |
 | TRON | INRT_TRON |
 | ETH | LATOKEN |
 | ETH | MKR |
 | BSC | MMY |
 | BSC | CAKE |
 | ETH | PAXG |
 | ETH | PAX |
| ETH | MATIC_ETH |
 | BSC | RMD |
 | ETH | REVV |
 | ETH | USDT |
| MATIC | USDT_MATIC |
| TRON | USDT_TRON |
 | ETH | SAND |
 | ETH | TUSD |
 | ETH | UNI |
 | ETH | LEO |
 | BSC | USDC_BSC |
| ETH | USDC |
| MATIC | USDC_MATIC |
| SOL | USDC_SOL |
 | BSC | BBTC |
| ETH | WBTC |
| BSC | BBCH |
| BSC | WBNB |
| BSC | BETH |
| BSC | BLTC |
| BSC | BDOT |
| BSC | BXRP |
Last modified 6d ago