Open the @Dusk_Foundation explorer at 2 a.m. and one number just sits there, unmoving: 1.7 million DUSK in unclaimed rewards. Total stake reads 216.9 million, active stake 215.2 million a healthy, humming network. But that 1.7 million is money nobody picked up. No alert flashes. No email fires. It just accumulates, like unopened mail in a hallway nobody walks through anymore.
The gap starts at onboarding. Once a stake is active, rewards are probabilistic, tied to consensus participation and stake size relative to the network not a guarantee, a lottery ticket you have to remember to cash. Claiming isn't automatic it's a second, separate action a provisioner has to initiate.
Migration compounds it. Because native DUSK runs 9 decimals and the ERC20 version runs 18, the contract rounds down to the nearest whole LUX fractions simply vanish, no refund, no notice. And if you hold DUSK on an exchange, the seamless bridge stops working entirely exchanges usually can't connect via WalletConnect, so you're withdrawing to self custody first, then migrating two transactions, two gas bills, one narrative that promised one click.
To be fair, the design isn't reckless. DUSK uses soft slashing stake isn't burned, just suspended and the original chain's transaction hash gets stored in the Dusk memo for traceability. Care went into the parts people can see.
But 1.7 million DUSK isn't sitting there because the protocol failed. It's sitting there because automated quietly became a marketing word, and somewhere a real person forgot to click claim.
#dusk $DUSK @Dusk
The gap starts at onboarding. Once a stake is active, rewards are probabilistic, tied to consensus participation and stake size relative to the network not a guarantee, a lottery ticket you have to remember to cash. Claiming isn't automatic it's a second, separate action a provisioner has to initiate.
Migration compounds it. Because native DUSK runs 9 decimals and the ERC20 version runs 18, the contract rounds down to the nearest whole LUX fractions simply vanish, no refund, no notice. And if you hold DUSK on an exchange, the seamless bridge stops working entirely exchanges usually can't connect via WalletConnect, so you're withdrawing to self custody first, then migrating two transactions, two gas bills, one narrative that promised one click.
To be fair, the design isn't reckless. DUSK uses soft slashing stake isn't burned, just suspended and the original chain's transaction hash gets stored in the Dusk memo for traceability. Care went into the parts people can see.
But 1.7 million DUSK isn't sitting there because the protocol failed. It's sitting there because automated quietly became a marketing word, and somewhere a real person forgot to click claim.
#dusk $DUSK @Dusk