🔍 An accepted block on Dusk is not necessarily a final block. That difference matters when an application decides whether a transaction is safe to settle.
Dusk uses Succinct Attestation, a consensus protocol that works through iterations. If an earlier iteration remains unresolved, a block accepted in a later iteration can be replaced if the earlier iteration eventually succeeds.
The whitepaper defines a 2n rule, where n counts previous non-attested iterations. An accepted block needs 2n consecutive attested or confirmed blocks to become confirmed. When n equals 2, that means four qualifying blocks. Confirmation alone is not finality. The block’s parent must also be final.
Payment apps should check the network’s finality status before releasing funds. A transaction appearing on screen does not, by itself, mean the payment has reached finality.
#DUSK $DUSK $AMP $GTC @Dusk
Dusk uses Succinct Attestation, a consensus protocol that works through iterations. If an earlier iteration remains unresolved, a block accepted in a later iteration can be replaced if the earlier iteration eventually succeeds.
The whitepaper defines a 2n rule, where n counts previous non-attested iterations. An accepted block needs 2n consecutive attested or confirmed blocks to become confirmed. When n equals 2, that means four qualifying blocks. Confirmation alone is not finality. The block’s parent must also be final.
Payment apps should check the network’s finality status before releasing funds. A transaction appearing on screen does not, by itself, mean the payment has reached finality.
#DUSK $DUSK $AMP $GTC @Dusk