I was reading Dusk’s consensus design today, and one thing actually caught my attention.
A block doesn’t simply become accepted after one vote.
First, a randomly selected committee checks the block during Validation.
Then comes Ratification — another committee reviews the result and votes again.
What I like about this design is the extra confirmation layer. A 2/3 supermajority is required for a successful quorum, so the network isn’t relying on a single group to make the final decision.
For me, this is more interesting than just saying “Dusk has fast consensus.”
It’s about how Dusk reaches agreement.
Speed matters, but I think the way a network protects that agreement matter just as much.
That’s the part of Dusk’s Succinct Attestation design I’m watching closely#dusk $DUSK @Dusk
A block doesn’t simply become accepted after one vote.
First, a randomly selected committee checks the block during Validation.
Then comes Ratification — another committee reviews the result and votes again.
What I like about this design is the extra confirmation layer. A 2/3 supermajority is required for a successful quorum, so the network isn’t relying on a single group to make the final decision.
For me, this is more interesting than just saying “Dusk has fast consensus.”
It’s about how Dusk reaches agreement.
Speed matters, but I think the way a network protects that agreement matter just as much.
That’s the part of Dusk’s Succinct Attestation design I’m watching closely#dusk $DUSK @Dusk