I Read Dusk's Incentive Design and Found Something Unusual in It
I was reading through dusk_foundation's whitepaper, specifically the section on block reward distribution.
Most PoS chains give the block proposer the bulk of the reward and move on.
Dusk does something different here.
The split is 80% to the block generator, 10% to the voting committee, 10% to Dusk.
But the 80% isn't fixed. The generator earns the full amount only if they include all known votes in the block. The variable portion, 10% of the total reward, scales with how many votes the generator actually includes.
This is a direct response to what the whitepaper calls the "future-generator incentive problem."
The mechanic is worth understanding. Because Succinct Attestation predetermines generators for all iterations within a single round, a validator scheduled for a later iteration knows in advance they're up next. That creates an incentive to let earlier iterations fail so they can collect the block reward without competition.
This is structural. It exists in any committee-based PoS design where future block producers are predictable ahead of time.
The variable reward structure partially addresses this. One design choice I noticed specifically: the next-iteration generator is excluded from the current voting committee. They can't strategically abstain to benefit from a failed iteration if they're not in the committee at all.
What I'm less convinced about is the enforcement layer. Soft slashing locks a portion of stake, hard slashing burns it, but both depend on fault proofs being included in subsequent blocks. That creates its own incentive questions at the validator level.
The design is coherent. The slashing enforcement is where the real test happens.
$DUSK #dusk @Dusk $ETH $BTC
I was reading through dusk_foundation's whitepaper, specifically the section on block reward distribution.
Most PoS chains give the block proposer the bulk of the reward and move on.
Dusk does something different here.
The split is 80% to the block generator, 10% to the voting committee, 10% to Dusk.
But the 80% isn't fixed. The generator earns the full amount only if they include all known votes in the block. The variable portion, 10% of the total reward, scales with how many votes the generator actually includes.
This is a direct response to what the whitepaper calls the "future-generator incentive problem."
The mechanic is worth understanding. Because Succinct Attestation predetermines generators for all iterations within a single round, a validator scheduled for a later iteration knows in advance they're up next. That creates an incentive to let earlier iterations fail so they can collect the block reward without competition.
This is structural. It exists in any committee-based PoS design where future block producers are predictable ahead of time.
The variable reward structure partially addresses this. One design choice I noticed specifically: the next-iteration generator is excluded from the current voting committee. They can't strategically abstain to benefit from a failed iteration if they're not in the committee at all.
What I'm less convinced about is the enforcement layer. Soft slashing locks a portion of stake, hard slashing burns it, but both depend on fault proofs being included in subsequent blocks. That creates its own incentive questions at the validator level.
The design is coherent. The slashing enforcement is where the real test happens.
$DUSK #dusk @Dusk $ETH $BTC