Overview
Your workspace automatically uses the default Deposit Control and Confirmation Policy. Depending on the blockchain, the default policy 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, we recommend a high amount of confirmations.
Blockchains with a finality property
The following blockchain networks have a finality property and don't rely on a variable number of confirmations. The default policy contains the correct value for these blockchain networks and can't be changed.
You cannot specify a custom number of confirmations for blockchain networks with a finality property. If you list and modify their set value, Fireblocks Support will require you to submit a revised policy that does not include these blockchain networks.
- Aevo: 360
- Algorand: 1
- Astar: 2
- Atom: 1
- Axelar: 1
- Base: 1
- Berachain: 1
- Blast: 1
- Camino: 1
- Canto: 2
- Celestia: 1
- Centrifuge: 2
- Chiliz 2.0: 1
- CoreDAO: 2
- dYdX: 1
- EOS: 2
- Hedera: 1
- Immutable X: 2
- Injective: 1
- Iota: 25
- Kusama: 2
- Kava: 2
- Lachain: 1
- Linea: 2
- Mantle: 1
- Noble: 1
- Osmosis: 1
- Peaq: 2
- Polkadot: 2*
- Ripple: 1
- Scroll: 1
- Sei: 1
- Solana: 1
- Stellar: 1
- Telos: 252
- Terra: 2
- Terra Classic: 2
- Tezos Etherlink: 2
- Thorchain: 1
- Ton: 1
- WeMix: 1
- WorldChain: 30
- zkSync: 2
- Zilliqa: 1
*The Polkadot blockchain has a unique confirmation architecture that Fireblocks represents accordingly:
- Transactions processed on a non-finalized block are represented with 1 confirmation.
- Transactions processed on a finalized block are represented with 2 confirmations.
All other blockchains
For all other blockchain networks, all deposits, including transfers between Vaults, require 1 confirmation.
Contract call operations
Contract call operations require 3 confirmations.