#dusk $DUSK @Dusk $TUT flying again go long on $PORTAL
A provisioner can look ready before Dusk considers it eligible. That gap caught my attention because it turns staking from a deposit into a continuing test of readiness.
The first condition is blunt: at least 1,000 DUSK must remain staked. It is easy to read that figure as an entry price, but it behaves more like a floor the operator must keep standing on. A partial unstake or penalty that pushes the position below it does not simply reduce influence. It ends eligibility.
Maturity is quieter. A new stake cannot participate as soon as its transaction settles. #dusk waits until the start of the epoch after the next boundary, normally six to twelve hours. That pause feels inconvenient only if staking is treated as a purchase. From the network’s side, it is a buffer. Capital can arrive quickly; responsibility should not.
Then comes the condition no balance can guarantee: conduct. A provisioner may hold enough stake and run a synchronized node yet still be suspended after failing to participate correctly. @Dusk distinguishes ordinary failure from provably invalid behavior. Soft penalties can move active stake into a locked portion while ownership remains with the staker. Hard penalties can burn stake for invalid votes or conflicting signatures. Downtime and deception both threaten consensus, but treating them as equal would be crude.
What feels honest is that these conditions cannot cover for one another. Wealth cannot erase the waiting period. Maturity cannot excuse unreliable operation. A clean record cannot rescue a stake below minimum.
Eligibility, then, is not a badge earned once. It is a live judgment. An operator can qualify today and lose that standing tomorrow through absence, misconfiguration, or a duplicated consensus key. Perhaps that is the real point: Dusk does not ask a provisioner once appeared trustworthy. It keeps asking whether provisioner is ready for next block.
What matters most for Dusk provisioner eligibility?