# Blocks and finality

> Why a transfer on USD Network is final the moment it is sealed, and how you can tell.

## Deterministic finality

USD Network has one block producer, the USD.NET sequencer, and blocks are hash-linked: each block names the hash of the one before it. A sealed block is never replaced, so a transfer in a sealed block is final. You do not need to wait for confirmations.

A transfer's `status` tells you where it is:

| Status | Meaning |
| --- | --- |
| `pending` | Accepted and waiting to be sealed. On testnet this lasts well under a second. |
| `final` | Sealed into the block shown in `block`, at position `index`. |
| `failed` | Rejected at sealing time, with the reason in `error`. Nothing moved and no fee was charged. |

## How you can check it

Finality is a promise from the operator. The transparency log makes that promise checkable:

- Every block's hash is a leaf in an append-only Merkle log.
- A [consistency proof](/open-data/consistency-proofs) between any two checkpoints shows that the later log contains the earlier one unchanged. If a block were ever rewritten, no such proof could exist.
- An [inclusion proof](/open-data/inclusion-proofs) shows a given block is in the log at a given checkpoint.

Checkpoints are also anchored to Solana every hour, and independent witnesses can cosign them, so a rewrite would also have to fool records and parties USD.NET does not control.

## Ordering

Transfers are sealed in the order the sequencer received them. Each account's transfers must use consecutive nonces, so a sender's own transfers are always applied in the order they were signed.
