Overview
Fireblocks supports certain non-EVM assets across all Fireblocks workspaces. In addition to these globally supported assets, Owners, Admins, Non-Signing Admins, Signers, and Editors can manually add more non-EVM assets to your organization's workspace as needed.
What standards are supported?
You can list additional assets on these non-EVM blockchains:
- Algorand (ASA)
- Digital Bits (XDB)
- Hedera (ERC-20)
- NEAR (NEP141)
- XRPL Ripple
- Solana (SPL)
- Stellar
- Tezos (FA1.2, FA2)
- TRON (TRC-20)
Some blockchains require a minimum balance or manual confirmation when adding asset wallets. Learn more about asset wallets on Algorand, Solana, Stellar, and Ripple.
How to add non-EVM assets to a workspace
Depending on the asset, you can add non-EVM assets to your workspace using one of these methods:
- Via the Fireblocks Console
- Via the Fireblocks API
- Via Fireblocks Support
Via the Fireblocks Console
You can use the Fireblocks Console to add non-EVM assets on the Algorand, NEAR, Solana, Stellar, and TRON blockchains.
- Go to the Assets page and search for the asset in the top left corner. If the asset is not listed, select List asset. This button also appears when attempting to create a wallet for assets not currently listed in the workspace.
- Select the asset’s blockchain, and select Continue.
- Copy and paste the asset’s contract address and name (if required). You can find this information using a block explorer for the asset’s blockchain network.
- Select Continue. Fireblocks verifies the contract address and blockchain and then displays the asset’s properties.
- Select List asset to list the asset in your workspace. You can now add asset wallets for this asset to any vault account.
Via the Fireblocks API
Use the Register an asset endpoint to add non-EVM assets on the Algorand, NEAR, Solana, Stellar, and TRON blockchains. This makes the asset available via the Fireblocks API for all asset-related operations, such as:
- Creating asset wallets for this asset in any vault account
- Whitelisting addresses for this asset in any whitelisted wallet
- Creating transactions with this asset
- Tracking active transactions with this asset
- Viewing previous transactions with this asset
- Retrieving vault accounts, exchange accounts, and whitelisted wallets that contain this asset
Via Fireblocks Support
Contact Fireblocks Support to add an unlisted asset on one of these blockchains to your workspace. You must provide a link to the token's page from the relevant block explorer:
Depending on the token requested, Fireblocks may make the token available to all Fireblocks customers or only to your workspaces.
All other non-EVM blockchains
All other non-EVM blockchain networks supported by Fireblocks only allow the storage and transfer of their base asset, except Terra Classic. Fireblocks support for Terra Classic only includes LUNC, USTC, KRTC, MNTC, and SDRC.
You can also submit requests for Fireblocks to support asset listing for non-EVM blockchains not currently supported by the feature. When attempting to list a new non-EVM asset in the Fireblocks Console, select Vote to support corresponding to the blockchain that’s not supported for asset listing. You can vote for as many blockchains as you want.
Finding newly added assets
To find the new asset’s ID using the Console, hover over the asset’s name to view additional details, including the asset’s ID in the Fireblocks API and its contract address. Use the asset’s ID in Fireblocks for all relevant API endpoints.
To find the new asset via the API, use the Get supported assets endpoint, then look for the asset by name, contractAddress, or id.
Troubleshooting
- Make sure the asset you're listing contains metadata. Otherwise, you may be unable to list the asset. You can check the asset's metadata using a block explorer.
- Incoming transactions involving assets deposited to your vault account before being added to your workspace do not appear in your Transaction History. However, the destination account balance will include the asset. Contact Fireblocks Support to re-scan the deposit address and recognize the incoming transaction.