At first I assumed liveness in Dusk's consensus was just a function of stake and participation — enough honest provisioners online, and the chain keeps moving on its own. But the more I looked at the emergency mode section, the picture got quieter than that. When enough consecutive iterations fail and no candidate reaches quorum, the network doesn't just keep retrying on its own terms forever. Provisioners can request an emergency block, and producing it depends on a seed signed by a key the paper simply calls Dusk's, checked against a public key listed as a global parameter. The request itself needs a majority of staked weight behind it, so it isn't unilateral. Still, the fallback for the system's worst case ends up routing through one specific, named party instead of the open sortition used everywhere else. Maybe that's a reasonable trade for a chain built around regulated finance. Makes me wonder whether decentralization is best judged by the common case, or by what happens once the common case breaks down.
#dusk #Consensus @Dusk $DUSK
#dusk #Consensus @Dusk $DUSK