Finality

Finality provides the block data needed to determine whether a transaction included in a block has reached a final state that cannot be reversed. On EVM chains, you can query the finalized block over RPC to determine finality. On other chains, you can calculate confirmation depth from the difference between the latest block (ledger) number and the block number that contains the transaction.

A transaction included in a block can become invalid if a chain reorganization (reorg) occurs. Crediting a deposit to a customer balance before finality risks letting the invalidated amount be withdrawn, so you can use Finality to set a finality threshold and credit only deposits that reach it.

Use Cases

• Finance & AccountingConfirm deposits

  Set a confirmation depth threshold per amount tier and credit only deposits that reach the threshold to customer balances. Applying a threshold suited to each amount size lets you manage the loss risk from reorgs.

• Withdrawal OpsComplete withdrawals

  Switch a withdrawal to completed once the block containing the withdrawal transaction reaches the finalized block or the confirmation depth threshold. This prevents marking a withdrawal as completed before finality and then missing one that needs to be resent after a reorg.

• InfrastructureCross-check data freshness

  Compare the latest block number with your own node or another source to check block lag. This prevents judging finality from data that does not yet reflect the latest state.

Available APIs

Block Queries — RPC

Block Queries — Data API