Fireblocks can screen an asset only when it is mapped to your screening provider's asset catalog, and Fireblocks expands those mappings about every two months.
How asset coverage works
Transaction screening and Travel Rule checks run through the providers you connect. A provider can screen an asset only when Fireblocks has mapped that asset to the provider's catalog. Which blockchains and assets a provider can screen depends on the provider's own data coverage, not on Fireblocks, so coverage differs from one provider to the next.
Fireblocks supports these providers:
- AML/KYT screening: Chainalysis, Elliptic, and TRM Labs.
- Travel Rule: Notabene, Sumsub, and GTR.
A workspace can connect one AML/KYT provider at a time.
How Fireblocks expands coverage
Fireblocks reviews and expands its asset mappings on a regular cycle, roughly every two months, as providers add coverage. When a new mapping goes live, transactions in the newly mapped assets can be screened.
Check whether an asset is screened
Each provider's article in the Help Center has a Supported assets section with a spreadsheet you can download. That spreadsheet is the only published list of screened assets.
Apart from the spreadsheet, you find out at transaction time. Open the transaction in Transaction History and review the screening result in the transaction details.
What happens when an asset isn't mapped
When a transaction involves an asset that isn't mapped to your provider, Fireblocks shows the asset as unsupported and skips the screening check for that transaction automatically. The transaction continues without a screening result.
Some transactions also skip screening regardless of the asset. Program calls, contract calls, and NFTs bypass screening with the reason UNSUPPORTED_ASSET.
Request screening for an asset
You can't map an asset yourself, because there is no self-serve option. To ask for an asset to be added, contact Fireblocks Support or your Customer Success Manager. Include the Fireblocks asset ID, the blockchain, and the contract address. Fireblocks considers the request for its next mapping cycle.
Some gaps come from the provider. If your provider doesn't cover an asset yet, Fireblocks can't map it until the provider adds it.