@Dusk_Foundation
At first I assumed Dusk’s stake maturity rule was mostly a waiting period to stop someone from joining consensus too quickly. But the more I looked, the timing itself seemed more deliberate. A new stake is not eligible immediately, and it does not become eligible at an arbitrary block either. The whitepaper places eligibility at the beginning of an epoch, after the remainder of the current epoch plus another full epoch has passed. What caught my attention is that the rule effectively makes new provisioners enter consensus in batches rather than continuously. That creates a quieter dependency: the active validator set is partly shaped by the calendar of epochs, not just by who has staked. It also means a newly locked stake has to wait through a predictable period before it can affect deterministic sortition. Maybe this makes committee changes easier to reason about, but it also delays how quickly new participants can influence the system.
So maybe the question isn't why staking has a delay, but what that delay is really protecting?
@Dusk_Foundation #dusk $DUSK