Overview
Specific blockchain networks require a minimum number of confirmations. You cannot enter 0 confirmations for these blockchain networks.
EVM-compatible blockchains
All EVM-compatible blockchain networks require a minimum of 1 confirmation.
Maximum number of confirmations
Specific blockchain networks have a maximum number of confirmations.
| Maximum # of confirmations | Blockchain name |
| 1 |
|
| 3 |
|
| 20 |
|
| 30 |
|
| 100 |
|
| 300 |
|
| 1200 |
|
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.
| Blockchain name | Finality property value |
| Aevo | 360 |
| Abstract | 1 |
| Aleph Zero | 1 |
| Algorand | 1 |
| Apechain | 1 |
| Astar | 2 |
| Atom | 1 |
| Axelar | 1 |
| Base | 1 |
| Berachain |
1 |
| Blast |
1 |
| Bob |
1 |
| Boom |
1 |
| Camino |
1 |
| Canto |
2 |
| Celestia |
1 |
| Centrifuge |
2 |
| Codex |
1 |
| CoreDAO |
2 |
| dYdX |
1 |
| EOS |
2 |
| Ethereum Testnet Hoodi |
1 |
| Filecoin |
1 |
| Flow |
1 |
| Gunzilla |
1 |
| Hedera |
1 |
| HederaEVM |
1 |
| HyperEVM |
1 |
| Immutable X |
2 |
| Ink |
1 |
| Iota |
25 |
| Iotex |
1 |
| Kaia |
1 |
| Kava |
2 |
| Kusama |
2 |
| Lachain |
1 |
| Linea |
2 |
| Lisk |
1 |
| Manta |
1 |
| Mantle |
1 |
| Mantra |
1 |
| Neutron |
1 |
| Noble |
1 |
| Osmosis |
1 |
| Peaq |
1 |
| Plume |
1 |
| Polkadot |
Transactions processed on a non-finalized block are represented with 1 confirmation; on a finalized block, represented with 2 confirmations |
| Redbelly |
1 |
| Ripple |
1 |
| Scroll |
1 |
| Sei |
1 |
| Solana |
1 |
| Soneium |
1 |
| Sonic |
1 |
| Stellar |
1 |
| Telos |
252 |
| Terra |
2 |
| Terra Classic |
2 |
| Tezos Etherelink |
2 |
| Thorchain |
1 |
| TON |
1 |
| Unichain |
1 |
| Viction |
After 3/4 of all validators approve transaction |
| WeMix |
1 |
| WorldChain |
1 |
| zkSync |
2 |
| Zilliqa |
1 |
| Zircuit |
2 epochs (64 blocks on L1) from safe blocks to finalized blocks |
Using minimums and maximums for speed and security
If you're an advanced user, we recommend you modify the base number of confirmations to match your organization's requirements for its overall safety strategy and faster, more efficient trading.
Transfers between vault accounts
For transfers between your Fireblocks vault accounts, you can apply 0 confirmations to all assets. Since your vault accounts are under your direct management, you are more likely to submit the correct amounts.
Deposits from external sources to your Vault
For deposits from external wallets to your Fireblocks vault, apply a high number of confirmations for all assets to establish a higher level of certainty about the transaction. The trade-off is that transactions take longer to complete.
Alternatively, you can choose to set higher confirmation values for select assets of a particular blockchain. Some examples of higher-than-default values that align with some blockchain networks' confirmation behavior are:
- All assets on Bitcoin Cash (BCH): 6
- All assets on Bitcoin SV (BSV): 30
- All assets on Bitcoin (BTC): 3
- All assets on Dash (DASH): 3
- All assets on Ethereum Classic (ETC): 500
- All assets on Ethereum (Ethereum Proof-Of-Stake or ETH): 60 (ETH PoS 60 confirmations pertain to the number of blocks registered in the chain within a 2-epoch timeframe, which is the chain's finality period)
- All assets on Ethereum Proof-Of-Work (ETHW): 30
- All assets on Litecoin (LTC): 6
- USDC asset on Avalanche (AVAX): 7
- USDC asset Ethereum (ETH): 6
- All assets on ZCash (ZEC): 12
- All assets on XDC Network (XDC, formerly XINFIN): 30