You can override the default Deposit Control and Confirmation Policy (DCCP) by creating your own policy.
First, download the DCCP template, then modify it according to your organization’s business needs and risk models. For example:
- You can enter zero or a small number if you want faster confirmations for known and trusted sources.
- You can enter a higher number if you want to help mitigate risks for unknown or untrusted sources.
Please note that Fireblocks has restrictions on the number of confirmations allowed for certain blockchain networks.
When you’re finished, submit your policy template for review, approval, and implementation.
The DCCP operates on a first-match basis rule set using the following parameters:
|Source||This parameter defines the type of venue from which the transaction originates. This can be specific, such as a vault account; groups of accounts, such as all your Binance accounts; or general, such as all exchanges, all Fireblocks Network connections, and so on.|
|Destination||This parameter defines the type of venue where the transaction transfers its specified amount. This parameter uses the same values as the Source parameter.|
|Amount||This parameter defines the minimum or maximum amount a transaction must be before the rule applies to it. This parameter can be set to:
This parameter defines the type of asset sent in a transaction. This parameter can be set to a specific asset or to include any asset supported by Fireblocks.
Asset can be set to Any. However, if a specific asset is listed, a blockchain must be specified for the asset.
Asset can be listed in one of the following formats:
Many assets have similar symbols and names. The asset ID or contract address is recommended if your confirmation policy includes different rules for many specific assets.
This parameter defines the blockchain network where any specified asset is transferred. For example, you must define whether a rule applies to USDC transactions on Avalanche, Ethereum, or any other relevant blockchain.
You can only enter blockchain networks currently supported by Fireblocks in this field, including testnet blockchain networks.
|# of Confirmations||
This parameter defines the number of confirmations required for a transaction to clear and for funds to be credited to a wallet.
This parameter can be set to:
The table below contains some generic examples of DCCP rules. It takes a few of the recommended confirmation numbers above and applies them to the policy template, along with a brief explanation of each rule below the table.
|Rule #||Source||Destination||Amount||Asset||Blockchain Network||# of Confirmations|
- Incoming and outgoing ETH transactions of any amount on the Ethereum Classic blockchain network require 500 confirmations. As this blockchain network is subject to a 51% risk of attack, we recommend a high amount of confirmations.
- Transferring any amount between vaults within this Fireblocks workspace on any blockchain network requires 0 confirmations.
- Litecoin withdrawal transactions from the connected Coinbase Exchange third-party account into the Fireblocks vault require the minimum allowed confirmations, which is 6 confirmations.
- Incoming and outgoing BTC transactions above $10,000 on the Bitcoin blockchain network require 6 confirmations.
- Incoming and outgoing BTC transactions up to $10,000 on the Bitcoin blockchain network require 3 confirmations.
- Incoming and outgoing USDC transactions of any amount on the Avalanche blockchain network require 7 confirmations.
- Incoming and outgoing USDC transactions of any amount on the Ethereum blockchain network require 6 confirmations.
- Incoming and outgoing transactions from any source to any destination in your Vault of any amount on any blockchain network require 1 confirmation.
Have a question?
Contact Fireblocks Support for additional assistance if necessary.