#dusk $DUSK The first thing I went looking for with $DUSK was pretty simple: how does this blockchain actually decide that a block is final?
At first, I assumed it was just validators signing off on a block.
But then I looked closer at the finality certificate.
It includes the round, step, a PLONK-related score, an aggregated BLS signature, and a validator sequence mapping for the consensus committees.
That caught my attention because the certificate isn’t simply saying, “validators approved this blockchain block.” It carries several pieces of evidence showing how finality was reached.
And with Dusk’s XSC (XSC) framework in the picture, the consensus side becomes even more interesting to look at.
I’m not saying this automatically makes the design better or worse. I just think these technical details are easy to overlook when most of the conversation is about privacy.
The more I dig into Dusk, the more I realize there’s a lot happening underneath the surface.
What do you think—how important is this certificate structure to Dusk’s finality?
$DUSK #dusk @Dusk
At first, I assumed it was just validators signing off on a block.
But then I looked closer at the finality certificate.
It includes the round, step, a PLONK-related score, an aggregated BLS signature, and a validator sequence mapping for the consensus committees.
That caught my attention because the certificate isn’t simply saying, “validators approved this blockchain block.” It carries several pieces of evidence showing how finality was reached.
And with Dusk’s XSC (XSC) framework in the picture, the consensus side becomes even more interesting to look at.
I’m not saying this automatically makes the design better or worse. I just think these technical details are easy to overlook when most of the conversation is about privacy.
The more I dig into Dusk, the more I realize there’s a lot happening underneath the surface.
What do you think—how important is this certificate structure to Dusk’s finality?
$DUSK #dusk @Dusk