Blockchain Confirmation Policy
Overview
Levain currently has an internal blockchain confirmation policy that is used to determine the number of blockchain confirmations required before a transaction is considered confirmed. This policy applies only to blockchains that has the concept of finality, such as Bitcoin, Ethereum and most EVM-compatible blockchains, across:
- Transactions
- Wallet creation, if applicable, only for blockchains that require a transaction to create a wallet
- Webhook events, when a transaction is subsequently considered as confirmed
Significance of blockchain finality
This only applies to blockchains with the concept of finality, such as Bitcoin, Ethereum and most EVM-compatible blockchains. For blockchains that do not have the concept of finality, the concept of confirmations does not apply.
Blockchain finality is the concept that once an on-chain transaction is confirmed, it is considered irreversible and irrevocable. This is important as it ensures that the transaction is not susceptible to attacks, such as double-spending.
The number of confirmations required before a transaction is considered confirmed varies across different blockchains, and is dependent on the blockchain's consensus mechanism. Usually, the higher the number of confirmations, the more unlikely it is for the transaction to be reversed or rolled back.
Blockchains are different from traditional financial systems in that they are decentralized and rely on consensus mechanisms to validate transactions. This is in contrast to traditional financial systems as they generally rely on a central authority (e.g. central banks, clearing houses, etc.) to process transactions, and once a transaction is confirmed, it is considered final.
For example, in Singapore, the Monetary Authority of Singapore (MAS) regulates the concept of finality - and when a transaction is considered final, irreversible and irrevocable - under the Payment and Settlement Systems (Finality and Netting) Act.
Existing confirmation policy
For testnets, we usually set it lower than the mainnet so that you can speed up your testing process.
The below table shows the default blockchain confirmation policy within Levain. For now, you won't be able to configure the policy for your organizational account.
Blockchain Name | Network Name | CAIP Identifier | Blockchain Confirmation Policy | Estimated Time |
---|---|---|---|---|
Ethereum | Mainnet | caip2:eip155:1 |
16 | ~3 minutes |
Ethereum | Sepolia Testnet | caip2:eip155:11155111 |
4 | |
Ethereum | Goerli Testnet | caip2:eip155:5 |
4 | |
Polygon | Mainnet | caip2:eip155:137 |
16 | ~30 seconds |
Polygon | Mumbai Testnet | caip2:eip155:80001 |
4 | |
Binance Smart Chain | Mainnet | caip2:eip155:56 |
16 | ~48 seconds |
Binance Smart Chain | Testnet | caip2:eip155:97 |
4 | |
Arbitrum | Mainnet | caip2:eip155:42161 |
16 | ~10 seconds |
Arbitrum | Goerli Testnet | caip2:eip155:421613 |
4 | ~10 seconds |
Bitcoin | Mainnet | caip2:bip122:000000000019d6689c085ae165831e93 |
4 | ~40 minutes |
Bitcoin | Testnet | caip2:bip122:000000000933ea01ad0ee984209779ba |
4 | |
Base | Mainnet | caip2:eip155:8453 |
16 | ~3 minutes |
Base | Goerli Testnet | caip2:eip155:84531 |
4 | |
Linea | Mainnet | caip2:eip155:59144 |
16 | ~90 seconds |
Linea | Testnet | caip2:eip155:59140 |
4 | |
OP | Mainnet | caip2:eip155:10 |
16 | ~30 seconds |
OP | Goerli Testnet | caip2:eip155:420 |
4 | |
OP | Sepolia Testnet | caip2:eip155:11155420 |
4 | |
Tron | Mainnet | caip2:tip474:728126428 |
16 | ~48 seconds |
Tron | Shasta Testnet | caip2:tip474:2494104990 |
16 | |
DeFiChain EVM | Mainnet | caip2:eip155:1130 |
16 | ~30 seconds |
DeFiChain EVM | Testnet | caip2:eip155:1131 |
16 | ~30 seconds |
Solana | Mainnet | caip2:solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
16 | ~6 seconds |
Solana | Testnet | caip2:solana:4uhcVJyU9pJkvQyS88uRDiswHXSCkY3z |
16 |