Dusk's August 16 bridge incident made me go back and actually read how $DUSK distributes block rewards — not the marketing summary, the tokenomics docs.
@Dusk_Foundation 's monitoring flagged suspicious behavior on a team-managed wallet used in bridge operations. Addresses were recycled, bridge services paused, a recipient blocklist pushed to the Web Wallet the same day. Fast response. But bridge pauses always make me want to understand where money actually flows before I convince myself an incident is truly contained.
So I went digging.
Block generators take 70% of every reward, plus up to an extra 10% depending on credits bundled into the block certificate — and anything undistributed from that 10% gets burned rather than redistributed.
That last part is the detail worth sitting with.
The variable 10% isn't really a bonus for generators — it's a participation incentive disguised as one. The split was specifically designed to push generators to include all known votes in the certificate, and to give voting provisioners a reason to actually vote.
If participation is low and votes don't make it into the certificate, that slice doesn't get redistributed to voters. It just disappears.
So provisioners aren't simply getting "the remainder." They're getting whatever generators chose to include — and in low-participation rounds, that could be meaningfully less than the headline reward structure implies.
That's not a flaw. Most PoS chains weight proposers heavily. But it does mean the effective provisioner yield is sensitive to network participation levels in ways that APY numbers alone won't tell you.
Rewards are probabilistic and depend on consensus participation and stake size relative to total active network stake — which makes participation health the variable I'd watch more closely than APY.
What metric would you want to see tracked — average credits per certificate, or burn rate on that variable 10%?
#DUSK #DuskNetwork #DuskReward #RWA
@Dusk_Foundation 's monitoring flagged suspicious behavior on a team-managed wallet used in bridge operations. Addresses were recycled, bridge services paused, a recipient blocklist pushed to the Web Wallet the same day. Fast response. But bridge pauses always make me want to understand where money actually flows before I convince myself an incident is truly contained.
So I went digging.
Block generators take 70% of every reward, plus up to an extra 10% depending on credits bundled into the block certificate — and anything undistributed from that 10% gets burned rather than redistributed.
That last part is the detail worth sitting with.
The variable 10% isn't really a bonus for generators — it's a participation incentive disguised as one. The split was specifically designed to push generators to include all known votes in the certificate, and to give voting provisioners a reason to actually vote.
If participation is low and votes don't make it into the certificate, that slice doesn't get redistributed to voters. It just disappears.
So provisioners aren't simply getting "the remainder." They're getting whatever generators chose to include — and in low-participation rounds, that could be meaningfully less than the headline reward structure implies.
That's not a flaw. Most PoS chains weight proposers heavily. But it does mean the effective provisioner yield is sensitive to network participation levels in ways that APY numbers alone won't tell you.
Rewards are probabilistic and depend on consensus participation and stake size relative to total active network stake — which makes participation health the variable I'd watch more closely than APY.
What metric would you want to see tracked — average credits per certificate, or burn rate on that variable 10%?
#DUSK #DuskNetwork #DuskReward #RWA