#dusk $DUSK @Dusk
Rolling Finality: How Dusk Confirms Transactions
Not every block needs to jump from “accepted” to permanently final in a single moment. Dusk takes a more progressive approach through rolling finality.
A block may first be accepted, meaning consensus was reached, but a lower-iteration competing block could still replace it. If all earlier iterations are already proven to have failed, the block becomes attested and cannot be replaced by a lower-iteration alternative.
Then comes confirmation. Each suitable successor adds more evidence that provisioners are building on the same chain. For an accepted block, the number of required successors depends on the unresolved earlier iterations. The more uncertainty, the more confirmations needed.
Finally, confirmation rolls through the chain: once a block is confirmed and its parent is final, it can become final too.
The interesting part is that finality in Dusk is not treated as a simple timer or fixed confirmation count. It adapts to the block’s history and the evidence created by later consensus rounds.
That creates a moving path from possibility → acceptance → stronger confidence → finality.
Rolling Finality: How Dusk Confirms Transactions
Not every block needs to jump from “accepted” to permanently final in a single moment. Dusk takes a more progressive approach through rolling finality.
A block may first be accepted, meaning consensus was reached, but a lower-iteration competing block could still replace it. If all earlier iterations are already proven to have failed, the block becomes attested and cannot be replaced by a lower-iteration alternative.
Then comes confirmation. Each suitable successor adds more evidence that provisioners are building on the same chain. For an accepted block, the number of required successors depends on the unresolved earlier iterations. The more uncertainty, the more confirmations needed.
Finally, confirmation rolls through the chain: once a block is confirmed and its parent is final, it can become final too.
The interesting part is that finality in Dusk is not treated as a simple timer or fixed confirmation count. It adapts to the block’s history and the evidence created by later consensus rounds.
That creates a moving path from possibility → acceptance → stronger confidence → finality.