12/8/22, 08:41 Advanced Configuration - Chainalysis – Fireblocks Help Center

ֿ
Anibal Garrido

Fireblocks Help Center

>
Advanced Topics
>
Integration with Chainalysis

Search

Articles in this section

Advanced Configuration - Chainalysis

6 months ago ·
Updated

Follow

The Advanced Configuration allows businesses to define what to do when there is a transaction
monitoring service interruption failure, whether to allow admin users the ability to unfreeze/bypass
transactions themselves, and the timeout period to keep funds in a pending locked state (pending an
Chainalysis screening result) in order to be able to automatically enact a rejection on the transaction
according to the Post-Screening Policy.

Default Configuration
Default Configuration

By default, the configuration will:

Bypass screening in the event of a service interruption

Allow admin users to have the ability to send rejected transactions according to risk strategy
(bypass outbound rejections via the console)
Allow admin users to have the ability to receive rejected transactions according to risk strategy
(unfreeze frozen inbound rejections via the console and API)
Have an inbound blocking timeout period of 30 seconds
Have an outbound blocking timeout period of 0 seconds

User-Defined Configuration

The default configuration can be replace with a user-defined configuration. Review the configuration
https://support.fireblocks.io/hc/en-us/articles/4409209170578-Advanced-Configuration-Chainalysis 1/4
12/8/22, 08:41 Advanced Configuration - Chainalysis – Fireblocks Help Center

definitions and sample configuration.

Advanced Configuration Definitions

In the rare case of a transaction monitoring service interruption failure,

Fireblocks will handle such a failure according to the bypass on failure flag.

By default, bypass on failure is active. This enables businesses to

automatically skip transaction monitoring service interruption failures in order to
maintain continuous operations. With the flag enabled, all transactions that
Disable Bypass
have a transaction monitoring service interruption bypass screening and are
on Failure Flag
accepted. After a transaction bypasses screening, the reason for the bypass is
visible in the transaction history.

Setting the disable bypass on failure flag to true (with a check mark)
deactivates bypass on failure, all transactions that have a transaction
monitoring service interruption failure will fail. 

By default, the disable admin unfreeze functionality flag is set to false.

Funds are frozen for rejected inbound transactions and can be manually
Disable Admin unfrozen by workspace users with admin roles using the unfreeze functionality.
Unfreeze
Functionality Setting the disable admin unfreeze functionality flag to true (with a check
Flag mark) disables this ability for all users, preventing console and API users from
being able to unfreeze funds. In this case, unfreezing funds will require
contacting Fireblocks support. 

By default, the disable admin bypass functionality flag is set to false.

Rejected outbound transactions can still be manually sent by workspace users
Disable Admin with admin roles using the bypass functionality.
Bypass
Functionality Setting the disable admin bypass functionality flag to true (with a check
Flag mark) disables this ability for all users, preventing console and API users from
being able to manually send rejected transactions. In this case, bypassing and
sending rejected transactions will require contacting Fireblocks support.

Inbound
By default, the inbound blocking timeout period is set to 30 seconds.
Blocking
https://support.fireblocks.io/hc/en-us/articles/4409209170578-Advanced-Configuration-Chainalysis 2/4
12/8/22, 08:41 Advanced Configuration - Chainalysis – Fireblocks Help Center
y , g p
Blocking
Timeout

The inbound transaction will stay in a pending locked state (pending an

Chainalysis screening result) until a screening result arrives or until it reaches
the inbound blocking timeout. Locking the transaction during this period
allows freezing the transaction's funds based on the screening result before
they become spendable (as funds that have already been spent cannot be
frozen). If no screening result is returned within the inbound blocking timeout,
the transaction's funds are released into the wallet. Funds may then be
manually frozen via the API.

By default, the outbound blocking timeout period is set to 0 seconds.

The outbound transaction will stay in a pending locked state (pending an

Outbound Chainalysis pre-screening result) until a screening result arrives or until it
Blocking reaches the outbound blocking timeout. Locking the transaction during this
Timeout period allows canceling the transaction prior to transaction creation based on
the screening result. If no screening result is returned within the outbound
blocking timeout, the transaction is moved to the next state in the transaction
process.

Sample Configuration*
Configuration Options Value

Disable Bypass on Failure

TRUE / FALSE FALSE (no check mark)
Flag (Default = FALSE)

Disable Admin Unfreeze

Functionality Flag (Default TRUE / FALSE FALSE (no check mark)
= FALSE)

Disable Admin Bypass

Functionality Flag (Default TRUE / FALSE FALSE (no check mark)
https://support.fireblocks.io/hc/en-us/articles/4409209170578-Advanced-Configuration-Chainalysis 3/4
12/8/22, 08:41 Advanced Configuration - Chainalysis – Fireblocks Help Center
Functionality Flag (Default TRUE / FALSE FALSE (no check mark)
= FALSE)

Inbound Blocking Timeout 0 or more seconds 600

(Default = 30 sec)

Outbound Blocking
0 or more seconds 0
Timeout (Default = 0 sec)

* For informational & illustrative purposes only.

Was this article helpful?

Yes
No

2 out of 3 found this helpful

Have more questions? Submit a request

Return to top

Fireblocks Help Center

https://support.fireblocks.io/hc/en-us/articles/4409209170578-Advanced-Configuration-Chainalysis 4/4