Jump to content
Onchain Report

Crypto news from every chain

Ethereum confirmations and Sui checkpoints: What each tells you

The difference between Ethereum confirmations and Sui checkpoints is block depth versus certified transaction history: one counts later blocks; the other marks batch inclusion.

Onchain Report Newsroom#d9a1672 min read

Ethereum confirmations and Sui checkpoints: What each tells you

After a transfer, Ethereum confirmations count the blocks added after a transaction’s block, while a certified Sui checkpoint records transactions in a validator-signed batch. The labels describe different evidence about transaction history: one is a measure of depth, and the other is a position in Sui’s permanent record.

What Ethereum confirmations tell you

Ethereum confirmations increase as new blocks follow the block that included your transaction. More confirmations mean greater block depth, which makes a change of history less likely under the chain’s consensus rules. The count is not itself Ethereum’s separate finality status.

Ethereum also exposes “safe” and “finalized” block states. A safe block has been justified by the Beacon Chain and is expected to become canonical; a finalized block has been accepted as canonical by more than two-thirds of validators. These states are separate from simply counting blocks after inclusion.

What a Sui checkpoint tells you

A Sui checkpoint is a batch in the chain’s ordered history. Validators build checkpoints from committed transactions, and a quorum signs a checkpoint before it becomes part of the permanent record. The checkpoint contains transaction and effects digests, compact identifiers for the transactions and their outcomes.

A transaction can reach finality before it appears in a checkpoint. A full node can certify its effects after a quorum of validators acknowledges the same effects digest; inclusion in a certified checkpoint is another proof of finality. So the checkpoint number is a history reference, not a tally of how many confirmations the transaction has accumulated.

Take a Suibridge transfer from Ethereum to Sui. Suibridge locks the supported asset on Ethereum and mints its counterpart on Sui. On the Ethereum side, read the confirmation depth against the bridge’s source policy. A confirmed source transaction is evidence about how far its block sits behind the chain’s head; Ethereum’s safe or finalized status is a distinct signal.

On Sui, read the checkpoint sequence number to locate the transaction in destination history. It tells you which certified batch includes the transaction, not how many blocks came after it. The difference matters when interpreting why Suibridge waits before minting: the related explanation helps connect source confirmations with safe minting, while the Sui checkpoint remains a destination record. Don’t convert its sequence number into an Ethereum confirmation count.