# Consensus and finality

> Understand the draft QDPoS design, scheduled validator activity, and finality signal.

Source: https://docs.iceroot.com/network/consensus/

The [draft QDPoS protocol](https://docs.iceroot.com/core/protocol-design/index.md) combines elected validators, scheduled blocks, and finality derived from signed block headers.

## Proposed parameters

| Parameter              | Draft value                    |
| ---------------------- | ------------------------------ |
| Validator seats        | 53                             |
| Slot duration          | 8 seconds                      |
| Round                  | 53 slots                       |
| Finality threshold     | 36 of 53 validators            |
| Election check         | Every 24 rounds                |
| Seat changes per check | At most one, gated by finality |

ROOT holders split voting weight among validators. A vote names 20 to 53 validators with at most 5% of the account’s weight each, validator accounts cannot vote, and an account holding more than 5% of ROOT’s supply carries no vote weight. Weight follows liquid ROOT balances; the draft does not require locking or bonding. Every node enforces these limits. They constrain how vote weight can be concentrated, but they do not determine whether several accounts or validators belong to the same person or organization. [Validators and voting](https://docs.iceroot.com/network/validators/index.md#proposed-voting-rules) lists the rules and what they do.

Changing at most one seat per election check rate-limits how quickly elections can replace the active set. That slows election-driven capture. It is not a bound on other attacks, such as compromising, buying, bribing, or coordinating validators that already hold seats.

The active set validates in a deterministic schedule. A missed slot remains empty and carries no penalty. A forger produces a block only when its relay sees at least 27 of the 53 validators online. That is a local safeguard, separate from the finality threshold of 36.

## Production and finality

A block’s inclusion and its finalization are separate events. Block production continues while later signed headers accumulate the votes needed to finalize earlier blocks.

The draft uses two header fields, `maxHeightPreviouslyForged` and `maxHeightPrevoted`, to derive implied votes. Its analysis gives an earliest finalization 71 blocks later. Timing depends on validator order and availability; the paper’s estimates are derived values, not measurements of a deployed network.

For the proposed API, `confirmations` measures how far the tip has advanced. **`finalized: true`** is the signal for an irreversible credit or destination-chain action, under the fault assumptions stated below.

## Faults and stalls

The draft distinguishes two guarantees:

- **Safety:** conflicting finalization is prevented with at most 18 Byzantine validators in a stable set, or 16 beside a one-seat transition.
- **Progress:** finality continues with up to 17 crashed validators. This claim does not cover coordinated Byzantine forking.

Without new finality, the proposed response is:

1. **After four rounds:** raise an alert.
2. **After 24 rounds:** pause ordinary user transactions. Evidence, validator system messages, and claims and refunds of hash time-locked transfers remain admissible.

Both levels lift automatically when finality resumes. Claims of time-locked entries, such as vesting tranches, are ordinary user transactions, so they wait until the pause lifts.

A permanent loss of enough seats requires a coordinated recovery release; the threshold does not automatically fall.

Finality window details, some system-message rules, and penalty durations remain open in the draft. Current runtime behavior must be checked against the matching Heartwood release.
