NETSoon

Docs Protocol

Consensus on cblocks

How one unchanged Alpenglow instance decides a chain of cblocks, what a cblock hash binds, and why validators vote on executed state.

New Constellation runs a single Alpenglow instance. To Alpenglow, a cblock is simply the block of consensus slot i, identified by its hash h(c_i). Its votes, certificates and ParentReady are Alpenglow's own. Two things differ: when a cblock is valid, which is the voting rule of Validator, and the timeouts, which leave δblock for execution.

What a cblock binds

text
c_i = (i_parent, h(c_parent), x_4i, x_4i+1, x_4i+2, x_4i+3, h_state)

h(c_i) covers:

  • the slot and hash of the parent cblock,
  • for each of its four slots, the agreed set P_s and the attested commitments of the blocks in it,
  • h_state, the hash of the state after executing all four xblocks.

Every commitment covers its proposer block, ciphertext and key. So h(c_i) binds the cblock to its parent, to exactly one set of proposer blocks and their payloads, and to the state after executing them.

No proposer builds the cblock. Each validator assembles it from what it validated and executed, which is why a vote can include the state hash: the state after a slot depends on every proposer's block, and no proposer knows the others' blocks before validators do.

Votes and certificates

Validators run Alpenglow's Votor on h(c_i). Thresholds are Alpenglow's, by stake:

Vote or certificateThresholdEffect
Fast finalization80% notarization votes for h(c_i)c_i finalized in one round
Notarization60% notarization votes for h(c_i)c_i notarized; a finalization vote follows
Finalization60% finalization votesc_i finalized (slow path)
Notar-fallback60% notarization and notar-fallback votesc_i certified after a split first round
Skip60% skip votesconsensus slot i skipped

A validator casts at most one notarization vote per consensus slot: Algorithm 2 emits the Block event for c_i at most once.

Execution before voting

A notarization vote is for the post-execution state. A notarization certificate therefore certifies the proposer blocks and the state they produce. This works because the proposer blocks of a consensus slot are decided together: a validator that votes notarize knows the exact set P and has executed exactly those blocks, so the four slots of a cblock are decided and executed as a single Alpenglow block is.

Designs that decide each proposer's block independently must execute after consensus, and their votes cannot certify the resulting state. NewCon executes before voting, not before block production ends.

ParentReady

ParentReady for the first consensus slot of a window is emitted as in Alpenglow, on a notar-fallback certificate for some earlier cblock and skip certificates for every consensus slot after it. It starts the next window's proposers (Proposer) and sets every validator's timeouts for that window (Validator).

Skips

A skip certificate for one consensus slot skips the rest of its window for everybody, and the next window starts right away. Before a slot's timeout, a validator votes skip when:

  • attestations for one of its slots disagree,
  • a proposer equivocated,
  • fewer than a strict majority of proposers are attested,
  • a block of the agreed set is missing or invalid, or
  • the cblock is not executed in time.

A window whose third proposer crashed at its start is not skipped: its cblocks are voted on two proposers' blocks.

Finalization time

In a window of correct proposers, a validator executes c_i by 3δglobal + j · δcblock + δblock after its ParentReady, where j is the position of c_i in the window, which is inside its timeout T(i) because Δtimeout ≥ 3δglobal. With the parameters of Acrux Net, every cblock reaches every correct validator before its timeout, and Alpenglow's liveness finalizes it. The measured time from a cblock's last slot to its finalization on Acrux Net is published on Parameters.