#dusk $DUSK @Dusk
Reading Dusk's slashing docs, one line stopped me: warnings and faults only reset when a provisioner earns a reward — meaning it actually produced or voted on a block. No timer. No automatic decay. Only participation clears the record.
Soft slashing on $DUSK SK doesn't burn stake. A fault moves a chunk of it into the rewards pool and shrinks the node's effective size, which lowers its odds of getting picked for the next committee. So a penalized provisioner needs to get selected again to reset its faults — but the penalty is what makes selection less likely in the first place.
That's the part I hadn't clocked. It's not just "bad nodes get punished." It's a system where recovery runs through the same door that got harder to walk through. #dusk pitches this as protecting reliability, and mechanically it does — laggards get deprioritized, uptime gets rewarded. But the path back depends entirely on getting picked again, not on waiting it out.
Worth checking: how many epochs it typically takes a suspended provisioner on @Dusk to land back in an active committee after a single fault.
Reading Dusk's slashing docs, one line stopped me: warnings and faults only reset when a provisioner earns a reward — meaning it actually produced or voted on a block. No timer. No automatic decay. Only participation clears the record.
Soft slashing on $DUSK SK doesn't burn stake. A fault moves a chunk of it into the rewards pool and shrinks the node's effective size, which lowers its odds of getting picked for the next committee. So a penalized provisioner needs to get selected again to reset its faults — but the penalty is what makes selection less likely in the first place.
That's the part I hadn't clocked. It's not just "bad nodes get punished." It's a system where recovery runs through the same door that got harder to walk through. #dusk pitches this as protecting reliability, and mechanically it does — laggards get deprioritized, uptime gets rewarded. But the path back depends entirely on getting picked again, not on waiting it out.
Worth checking: how many epochs it typically takes a suspended provisioner on @Dusk to land back in an active committee after a single fault.
