the Dusk staking detail I kept coming back to is that locking DUSK does not immediately give that stake consensus power.
my first read was simple:
stake tokens.
become a provisioner.
enter consensus.
but Dusk inserts another state between those things:
eligibility.
a stake is recorded as an amount plus the block height where its transaction was included. to enter deterministic sortition, it must meet the minimum and survive a maturity period tied to epochs.
that period is not simply “wait N blocks from deposit.”
it includes the rest of the epoch where the stake lands, plus another full epoch. the result: new stakes become eligible at an epoch boundary.
so two stakes committed at very different times can still acquire consensus rights together.
someone staking near the start of an epoch waits longer than someone near its end, yet both can cross the eligibility boundary together.
that feels small until you separate the states.
locked capital is already exposed to the staking system.
eligible capital can actually enter sortition.
selected capital gets a concrete consensus role.
those are three different moments.
penalties split the picture again. suspension can exclude a provisioner from sortition for epochs. soft slashing can lock part of the stake and reduce its weight. hard slashing can burn stake.
so even “still staked” does not necessarily mean “still carrying the same consensus influence.”
that makes the epoch boundary more than bookkeeping.
it is part of the protocol's security surface.
imagine a large stake arriving late in an epoch. the capital is committed, but it cannot immediately reshape committee selection just because the transaction finalized.
Dusk makes stake ownership immediate and consensus eligibility delayed.
and that changed the question for me.
when we say a PoS network has gained new stake, do we mean the capital has been locked?
or that the protocol has actually allowed that capital to start deciding blocks?
@Dusk #Dusk $DUSK $GPS $VELVET
my first read was simple:
stake tokens.
become a provisioner.
enter consensus.
but Dusk inserts another state between those things:
eligibility.
a stake is recorded as an amount plus the block height where its transaction was included. to enter deterministic sortition, it must meet the minimum and survive a maturity period tied to epochs.
that period is not simply “wait N blocks from deposit.”
it includes the rest of the epoch where the stake lands, plus another full epoch. the result: new stakes become eligible at an epoch boundary.
so two stakes committed at very different times can still acquire consensus rights together.
someone staking near the start of an epoch waits longer than someone near its end, yet both can cross the eligibility boundary together.
that feels small until you separate the states.
locked capital is already exposed to the staking system.
eligible capital can actually enter sortition.
selected capital gets a concrete consensus role.
those are three different moments.
penalties split the picture again. suspension can exclude a provisioner from sortition for epochs. soft slashing can lock part of the stake and reduce its weight. hard slashing can burn stake.
so even “still staked” does not necessarily mean “still carrying the same consensus influence.”
that makes the epoch boundary more than bookkeeping.
it is part of the protocol's security surface.
imagine a large stake arriving late in an epoch. the capital is committed, but it cannot immediately reshape committee selection just because the transaction finalized.
Dusk makes stake ownership immediate and consensus eligibility delayed.
and that changed the question for me.
when we say a PoS network has gained new stake, do we mean the capital has been locked?
or that the protocol has actually allowed that capital to start deciding blocks?
@Dusk #Dusk $DUSK $GPS $VELVET
