About the Elliptic integration

You can configure Fireblocks to provide transaction information, such as output address, transaction hash, and a Customer Reference ID, to Elliptic for Know Your Transaction (KYT) screening. Using the AML Transaction Screening Policy, you decide which transactions are screened and sent to Elliptic for further analysis.

For a list of supported assets on Fireblocks and Elliptic, see here.

Viewing risk information

Auditable risk information about all your screened transactions is available from Elliptic and Fireblocks. You can view your screened transactions on the Fireblocks Console’s Transaction History page and Audit Log, or use the Fireblocks API. Transaction rejection information is only available from Fireblocks.

You can also receive notifications of indirect risk exposure and ongoing risk attributions via severity alerts in the Elliptic UI.

Before you begin

Before you can connect your Elliptic account, complete the process of enabling the Compliance tab.

Initial setup

Generate your Elliptic API key

1. Log in to your Elliptic dashboard.
2. Generate your API key and secret key:
   1. If you have access to Workspace Settings, follow Elliptic's guide for generating your API key and secret key.
   2. If you don't have access to Workspace Settings, contact your Elliptic Account Manager or support@elliptic.co to have your API key and secret key generated.
3. Copy your API key and secret key.

Activate the Elliptic integration on Fireblocks

1. In the Fireblocks Console, go to Settings > Compliance > AML > Connect provider.
2. Select Elliptic.
3. Enter your Elliptic API key and secret key.

AML Transaction Screening Policy

The Elliptic integration uses your workspace’s AML Transaction Screening Policy to determine which incoming and outgoing transactions to screen. Upon activating the Elliptic integration, the default AML Transaction Screening Policy is used until you create an optional custom policy.

AML Post-Screening Policy

The Elliptic integration uses your workspace’s AML Post-Screening Policy to pre-determine what action to take on a screened transaction based on the screening result returned by Elliptic. Upon activating the Elliptic integration, the default AML Post-Screening Policy is used until you create an optional custom policy.

Additional configurations

You can set up Customer Reference IDs to automatically associate users with incoming and outgoing transactions. This allows you to view the potential risk of transacting with each user.

Testing transaction rejection

Incoming transactions

1. Add two rules to the end of your AML Post-Screening Policy that reject small dust transactions (e.g., $0.0568) from an identified source, such as from a well-known exchange.
   1. The first rule should accept all transactions greater than $0.0568.
   2. The second rule (the last rule on the policy) rejects all transactions.
2. Initiate transactions above and below the amount threshold to trigger the respective rules.

These rules can be disabled at your request. Also, remember that only transactions with an attribution made within the Inbound Blocking Timeout period will be rejected. This does not include transactions that receive an “Unknown” screening result from Elliptic.

Outgoing transactions

1. Create a reject rule on your AML Post-Screening Policy to match transactions identified as high-risk by Elliptic.
2. Set one of your destination wallet addresses as a custom address in Elliptic. You can delete the custom address after you complete testing.

These rules can be disabled at your request. Also, remember that only transactions with an attribution made within the Outbound Blocking Timeout period will be rejected. This does not include transactions that receive an “Unknown” screening result from Elliptic.

Supported assets (V1)

Elliptic has a list of assets and networks that its screening service supports. You can log in to your Elliptic account to view their supported assets. Fireblocks supports the subset of these assets and networks as listed below.

You can request support for screening additional assets that are a part of Elliptic's list by submitting a request to Fireblocks Support. On your request, make sure to list the specific assets you want to be supported in your workspace.

Supported assets (Holistic)

Elliptic Holistic supports a wider range of assets by supporting blockchains holistically. This means that newly deployed tokens are supported automatically. Fireblocks supports all tokens on the following blockchains for screening with Elliptic Holistic.

• Algorand
• Aptos
• Arbitrum One
• Avalanche C-Chain
• BNB Smart Chain
• Base
• Bitcoin
• Bitcoin Cash
• Cardano
• Celo
• Core DAO
• Cosmos Hub
• DYDX
• Dogecoin
• Ethereum
• Ethereum Classic
• Fantom Opera
• Flare
• Gnosis
• Hedera
• Injective
• Linea
• Litecoin
• NEAR Protocol
• OP Mainnet (Optimism)
• Polkadot
• Polygon
• Ripple
• Solana
• Stellar
• TON
• TRON
• Tezos
• Worldchain
• XinFin Network
• ZCash
• Zilliqa EVM Mainnet
• zkSync Era