#dusk $DUSK @Dusk What I find interesting about Dusk is that consensus isn’t treated like one giant yes/no decision.
A block gets proposed first, then validators have a separate step to evaluate it before the network agrees on the final state.
That separation makes sense to me. Producing a block and accepting that block aren’t exactly the same thing.
Of course, more stages also mean more coordination, so there’s a tradeoff.
Curious to see whether this structure gives Dusk stronger protection against bad proposals, or simply adds another layer the network has to coordinate.
#dusk @Dusk $DUSK
A block gets proposed first, then validators have a separate step to evaluate it before the network agrees on the final state.
That separation makes sense to me. Producing a block and accepting that block aren’t exactly the same thing.
Of course, more stages also mean more coordination, so there’s a tradeoff.
Curious to see whether this structure gives Dusk stronger protection against bad proposals, or simply adds another layer the network has to coordinate.
#dusk @Dusk $DUSK
