Note: These values are subject to change.
Before signing an attestation for a source chain event, Circle waits for a specified number of onchain block confirmations to achieve hard finality.
Select the applicable CCTP version below to view the required block confirmations and average time to attestation for each blockchain.
- CCTP V1
- CCTP V2
The table below shows the average time required for an attestation to become available after a message is emitted onchain.
| Source Chain | Number of Blocks | Average Time |
|---|---|---|
| Ethereum | ~65* | ~13 to 19 minutes* |
| Avalanche | 1 | ~8 seconds |
| OP Mainnet | ~65 ETH blocks* | ~13 to 19 minutes* |
| Arbitrum | ~65 ETH blocks* | ~13 to 19 minutes* |
| Noble | 1 | ~20 seconds |
| Base | ~65 ETH blocks* | ~13 to 19 minutes* |
| Polygon PoS | ~200* | ~8 minutes |
| Solana | 32 | ~25 seconds |
| Sui | 1 | ~8 seconds |
| Aptos | 1 | ~8 seconds |
| Unichain | ~65 ETH blocks* | ~13 to 19 minutes* |
Block confirmations for L2s to Ethereum
Layer 2 (L2) blockchains publish transaction data in batches to Ethereum L1, and the frequency of these posts varies by chain. Some submit batches every few minutes, while others are less frequent. After a batch is posted, Circle waits for the Ethereum L1 block containing the batch to finalize, which typically happens after ~65 blocks, or 13 to 19 minutes, before issuing an attestation.
The tables below show the average time required for an attestation to become available after fast and standard messages are emitted onchain, respectively.
Note: These values are subject to change.
| Source Chain | Number of Blocks | Average Time |
|---|---|---|
| Ethereum | 2 | ~20 seconds |
| Arbitrum | 1 | ~8 seconds |
| Base | 1 | ~8 seconds |
| Codex | 1 | ~8 seconds |
| Linea | 1 | ~8 seconds |
| OP Mainnet | 1 | ~8 seconds |
| Polygon PoS | 13 | ~35 seconds |
| Solana | 2-3* | ~8 seconds |
| Unichain | 1 | ~8 seconds |
| World Chain | 1 | ~8 seconds |
| Source Chain | Number of Blocks | Average Time |
|---|---|---|
| Ethereum | ~65* | ~13 to 19 minutes* |
| Arbitrum | ~65 ETH blocks* | ~13 to 19 minutes* |
| Avalanche | 1 | ~8 seconds |
| Base | ~65 ETH blocks* | ~13 to 19 minutes* |
| Codex | ~65 ETH blocks* | ~42 to 48 minutes* |
| Linea | 1 | ~6 to 32 hours** |
| OP Mainnet | ~65 ETH blocks* | ~13 to 19 minutes* |
| Polygon PoS | ~33 | ~90 to 120 seconds |
| Solana | 32 | ~25 seconds |
| Sonic | 1 | ~8 seconds |
| Unichain | ~65 ETH blocks* | ~13 to 19 minutes* |
| World Chain | ~65 ETH blocks* | ~13 to 19 minutes* |
Block confirmations for L2s to Ethereum
Layer 2 (L2) blockchains publish transaction data in batches to Ethereum L1, and the frequency of these posts varies by chain. Some submit batches every few minutes, while others are less frequent; for example, Codex posts state roots every ~30 minutes. After a batch is posted, Circle waits for the Ethereum L1 block containing the batch to finalize, which typically happens after ~65 blocks, or 13 to 19 minutes, before issuing an attestation.
Hard finality for Linea
The typical time before hard finality on Linea is 6-32 hours. This is expected to be reduced in a future Linea upgrade.
Finality for Solana
For Solana Standard Messages, Circle waits for block finality before attesting. This takes 32 blocks. For Fast Messages, Circle only waits for the block to be confirmed, meaning the block has received votes from validators representing over two-thirds of the total stake. This typically takes 2-3 blocks.
Did this page help you?
© 2023-2025 Circle Technology Services, LLC. All rights reserved.
