I was reading through Dusk’s consensus design, and one part really stood out to me: what happens when the network can’t reach consensus?
If most provisioners go offline or get isolated, Dusk can face several failed iterations. After 16 consecutive failures, the protocol can switch to Emergency Mode.
What I like here is that Dusk doesn’t simply stop and wait.
Open iterations can keep running until a candidate block gets the required quorum. And if recovery takes too long, Dusk can create an Emergency Block.
This isn’t a normal transaction block. It’s basically a way for the network to recover and safely move into the next round. It also carries a new seed and proof of the emergency requests.
For me, this is the interesting part of consensus design.
Anyone can talk about speed when everything is working.
I’m more interested in what a blockchain does when things go wrong.
That’s where Dusk’s Emergency Mode caught my attention.
#dusk $DUSK @Dusk
If most provisioners go offline or get isolated, Dusk can face several failed iterations. After 16 consecutive failures, the protocol can switch to Emergency Mode.
What I like here is that Dusk doesn’t simply stop and wait.
Open iterations can keep running until a candidate block gets the required quorum. And if recovery takes too long, Dusk can create an Emergency Block.
This isn’t a normal transaction block. It’s basically a way for the network to recover and safely move into the next round. It also carries a new seed and proof of the emergency requests.
For me, this is the interesting part of consensus design.
Anyone can talk about speed when everything is working.
I’m more interested in what a blockchain does when things go wrong.
That’s where Dusk’s Emergency Mode caught my attention.
#dusk $DUSK @Dusk