You can add non-EVM assets to your Fireblocks workspace via the Console, the Fireblocks API, or Fireblocks Support. Certain assets are available globally across all workspaces; others must be listed manually.
What standards are supported?
You can list additional assets on these non-EVM blockchains:
- Algorand (ASA)
- Canton (CIP-56)
- Digital Bits (XDB)
- Hedera (ERC-20)
- NEAR (NEP-141)
- Ripple (XRPL)
- Solana (SPL)
- Solana (Token-2022)
- Stellar
- Sui
- Tezos (FA1.2, FA2)
- TON
- 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, 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, Sui, 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 it available to all 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.
Adding Solana Token-2022 tokens to a workspace
Fireblocks supports both SPL tokens and the Solana Token-2022 standard. Token-2022 introduces additional capabilities known as Token Extensions (for more information, see the Solana documentation on Token-2022 Extensions). Fireblocks support for these extensions varies by extension type.
Important warnings for Solana Token-2022
- Interest Bearing: Solana provides a utility function to help you view your accumulated balance, which may differ from the balance shown in Fireblocks.
- Memo Transfer: If you perform a transfer via Fireblocks and add a note, it will not be included as a memo instruction. This may cause the transfer to fail if the asset requires a memo. To ensure successful transfers, use Solana program calls directly when memo functionality is needed.
- Non-Transferable: Transfers will fail if this extension is enabled. Always verify token properties before initiating a transfer.
- Confidential Transfers / Transfer Fee: Solana's hidden balance and transfer mechanisms used by confidential transfers are not supported by Fireblocks. Regular transfers are supported, but you must use the Fireblocks Program Call API to view and use hidden balances.
- Default Account State: Tokens may be received in a frozen state by default. Verify the token is unfrozen before attempting transfers.
Adding Canton CIP-56 tokens to a workspace
CIP-56 is Canton Network's token standard for institutional assets, covering balance queries, transfers, and transaction history, with built-in privacy controls and support for regulated transfer workflows. When listing a CIP-56 token in your workspace, you will need the token's Admin ID and Instrument ID. You can obtain these from the token issuer.
Finding newly added assets
To find the new asset's ID using the Console, select 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.