The detail that made me look twice: Dusk’s own whitepaper says a block can carry a success attestation and still not be FINAL.
The current overview describes Succinct Attestation as giving deterministic finality once a block is ratified. But the technical spec adds an important layer: blocks can sit in ACCEPTED, ATTESTED, CONFIRMED, or FINAL states. If a block lands above iteration 0 while lower iterations lack fail attestations, it can remain accepted and potentially be replaced by a lower-iteration block.
That doesn’t mean Dusk has weak finality. The protocol explicitly handles this through rolling finality. Validation needs a 2/3 supermajority, then a newly selected ratification committee votes on that result before the protocol advances.
What caught my attention is the integration implication. For regulated settlement, “included on-chain” and “economically irreversible” are not always identical signals. My interpretation: serious financial infrastructure should care about the block’s consensus state, not merely its inclusion.
That nuance may matter just as much as the privacy story around DuskFoundation and DUSK.
How clearly will Dusk expose these finality states to institutions building settlement workflows?
@Dusk_Foundation $DUSK #dusk
The current overview describes Succinct Attestation as giving deterministic finality once a block is ratified. But the technical spec adds an important layer: blocks can sit in ACCEPTED, ATTESTED, CONFIRMED, or FINAL states. If a block lands above iteration 0 while lower iterations lack fail attestations, it can remain accepted and potentially be replaced by a lower-iteration block.
That doesn’t mean Dusk has weak finality. The protocol explicitly handles this through rolling finality. Validation needs a 2/3 supermajority, then a newly selected ratification committee votes on that result before the protocol advances.
What caught my attention is the integration implication. For regulated settlement, “included on-chain” and “economically irreversible” are not always identical signals. My interpretation: serious financial infrastructure should care about the block’s consensus state, not merely its inclusion.
That nuance may matter just as much as the privacy story around DuskFoundation and DUSK.
How clearly will Dusk expose these finality states to institutions building settlement workflows?
@Dusk_Foundation $DUSK #dusk