Was pulling numbers for DUSK and got stuck staring at one line longer than I meant to — Burned (24h): 22,163.29 $DUSK against Rewards Paid (24h): 149,388.84. Block #4,314,618, epoch #1,998, @Dusk chain humming along at its usual ~10s clip.
That's roughly 15% of the daily reward pool just... gone. Not because someone hit a burn button for optics. It's baked into how block rewards split — the generator gets 70% plus up to 10% more, but only if enough committee credits land in the certificate. Whatever doesn't get attested in time doesn't roll over to anyone. It burns.
So the burn rate isn't a supply-management dial the team turns for a headline. It's a live readout of how well the voting committee is actually coordinating block to block. High burn on a given stretch = more missed attestations than usual, not "more deflation, more bullish."
Hmm — kind of flips the framing I walked in with. Went in assuming burn was a deliberate scarcity lever. Turns out it's closer to a consensus-health gauge wearing a tokenomics costume. Still not sure how tightly that 24h number tracks actual validator uptime versus just normal iteration overhead though. Anyone tracked it against epoch-over-epoch churn?
#dusk $DUSK @Dusk
That's roughly 15% of the daily reward pool just... gone. Not because someone hit a burn button for optics. It's baked into how block rewards split — the generator gets 70% plus up to 10% more, but only if enough committee credits land in the certificate. Whatever doesn't get attested in time doesn't roll over to anyone. It burns.
So the burn rate isn't a supply-management dial the team turns for a headline. It's a live readout of how well the voting committee is actually coordinating block to block. High burn on a given stretch = more missed attestations than usual, not "more deflation, more bullish."
Hmm — kind of flips the framing I walked in with. Went in assuming burn was a deliberate scarcity lever. Turns out it's closer to a consensus-health gauge wearing a tokenomics costume. Still not sure how tightly that 24h number tracks actual validator uptime versus just normal iteration overhead though. Anyone tracked it against epoch-over-epoch churn?
#dusk $DUSK @Dusk
