I was tracing what happens when a Dusk block proposer goes offline mid-round, expecting to find some kind of halt and recover routine. Instead I found something quieter: a NilQuorum.
On the surface, missing a block sounds like a problem no candidate, no progress. But Succinct Attestation doesn't wait for a fix. If the committee can't reach quorum on a valid candidate within an iteration, it reaches quorum on the absence of one. A Failed Attestation is still an attestation just one certifying "nothing here" instead of a block.
That's the part that changed how I saw it. The network isn't tolerating failure by ignoring it; it's treating failure as a first class outcome with its own cryptographic proof. The round doesn't stall it just advances to the next iteration with a fresh committee, and rolling finality quietly accounts for how many empty iterations preceded the eventual block.
So the "crisis" case and the normal case use the same voting machinery. A dead proposer doesn't trigger recovery logic it just produces a different kind of vote.
Still not sure how this behaves under sustained proposer unavailability rather than a single missed slot.
#dusk $DUSK @Dusk
On the surface, missing a block sounds like a problem no candidate, no progress. But Succinct Attestation doesn't wait for a fix. If the committee can't reach quorum on a valid candidate within an iteration, it reaches quorum on the absence of one. A Failed Attestation is still an attestation just one certifying "nothing here" instead of a block.
That's the part that changed how I saw it. The network isn't tolerating failure by ignoring it; it's treating failure as a first class outcome with its own cryptographic proof. The round doesn't stall it just advances to the next iteration with a fresh committee, and rolling finality quietly accounts for how many empty iterations preceded the eventual block.
So the "crisis" case and the normal case use the same voting machinery. A dead proposer doesn't trigger recovery logic it just produces a different kind of vote.
Still not sure how this behaves under sustained proposer unavailability rather than a single missed slot.
#dusk $DUSK @Dusk