Chainalysis screens transactions for blockchain risk. Your AML/KYT Trigger (Screening Policy) decides which transactions are sent to Chainalysis, and your Outcome (Post-Screening Policy) decides what happens based on the result. See Building a Compliance Policy for how Trigger and Outcome work in general, and About AML/KYT for how AML/KYT fits into screening.
This is a premium feature that requires an additional purchase. Contact your Customer Success Manager if you do not already have an agreement with an AML provider. Fireblocks Support enables it on your workspace, and you connect it in the Console.
How it works
Fireblocks sends transaction details, including the output address, transaction hash, and Customer Reference ID, to Chainalysis for Know Your Transaction (KYT) screening. Chainalysis returns a risk result: a categorical risk level (Unknown, Low, Medium, High, Severe) and the specific risk category that was matched, if any. Chainalysis supports the baseline Outcome actions: Accept, Reject, and Alert.
Fireblocks waits for up to 10 minutes for an incoming result and one minute for an outgoing one. After that, the Outcome rules for a timed-out screening apply.
You can view screened transactions on the Transaction History page, the Audit Log, or via the API. The externalId in a screening result is the identifier Chainalysis assigned when Fireblocks registered the transfer: a transfer for an incoming transaction, a withdrawal attempt for an outgoing one. Look it up in Chainalysis with the same API key you configured in Fireblocks. The Developer Portal lists the endpoints. Transaction rejection information is available only from Fireblocks, not directly from Chainalysis. Chainalysis can also send you severity alerts for indirect risk exposure through its own UI.
Setup
Before you begin, Fireblocks Support must enable AML/KYT on your workspace.
- Create an API key in Chainalysis. Chainalysis documents this in the KYT API documentation. You need access to the Know Your Transaction (KYT) API in Chainalysis to create the key. If you are later removed from the Chainalysis account, create a new key.
- Connect it in the Fireblocks Console:
- Go to Policies > Compliance > AML > Policy > Connect.
- Select Chainalysis V2.
- Enter your API key.
Default Trigger (Screening Policy) and Outcome (Post-Screening Policy) rules apply until you create your own.
You can read the policies and a transaction's result through the API; connecting the provider is Console-only. See Chainalysis on the Developer Portal.
To switch to a new API key later, submit a ticket to Fireblocks Support with the new key.
Testing transaction rejection
You can test that rejection rules work before relying on them in production:
- Incoming: add a rule that accepts transactions above a small threshold (for example, $0.0568) and a final rule that rejects everything else, then send test transactions above and below that threshold.
- Outgoing: add a rule that rejects transactions matching a specific risk category, then mark one of your own destination addresses as high-risk in Chainalysis to trigger it.
Transactions that receive an "Unknown" result are not affected by these test rules, and both only apply within your configured blocking-timeout window.
Supported assets
Download the attached spreadsheet of supported assets.
Chainalysis supports blockchains and tokens broadly; newly deployed tokens are typically supported automatically, without Fireblocks needing to add them individually.
An ERC-20 token needs a USD price in Fireblocks to be screened properly. Outgoing transactions in an unpriced token are not registered with Chainalysis, and incoming transactions in an unpriced token do not trigger risk alerts, so Outcome rules based on risk score cannot apply to them.
- Testnet assets are supported.
- SOL transactions with an amount of 0.0 bypass screening with an Unsupported Route status.
Limitations
- Only one AML/KYT provider can be connected to a workspace at a time. To switch or disconnect a provider, contact Fireblocks Support.