The Deposit Control and Confirmation Policy (DCCP) lets you specify how many blockchain network confirmations are required for incoming and outgoing transactions to clear so their funds can be credited to a wallet. Until a transaction clears, its deposit amount is locked in either the inflow or outflow state. After it clears, its deposit amount is accounted for in the wallet's currently available balance. Additionally, for UTXO-based blockchain networks, the transaction's outputs become immediately spendable.

Default confirmation policy

Your workspace automatically uses the default Deposit Control and Confirmation Policy. Depending on the blockchain, the default policy requires the number of confirmations described below.

Ethereum Classic

372 confirmations are required for all transactions made on the Ethereum Classic blockchain network. As this blockchain network is subject to a 51% risk of attack, Fireblocks recommends a high amount of confirmations.

Blockchains with a finality property

See the Blockchain confirmation limitations article for more information.

All other blockchains

For all other blockchain networks, all deposits, including transfers between Vaults, require 1 confirmation.

Contract call operations

Contract call operations default to 3 confirmations. You can configure this value in your Confirmation Policy.

Next steps

• Build a custom DCCP — Override the default with your own confirmation rules
• Blockchain confirmation limitations — View minimum and maximum confirmation values per blockchain