#dusk $DUSK @Dusk After staking for a while on the testnet, I figured it was time to claim my rewards. I originally thought it would be as simple as clicking a “Claim” button—the rewards would automatically add to my principal so I could keep compounding. Turns out Dusk’s setup is totally different.
The rewards don’t auto-compound. They accumulate in your account, but they only become actual staked assets when you actively go in and claim them. If you never click that claim button, the rewards just sit there: they don’t grow and they don’t compound.
At first I thought it was just a UI/UX design choice. But when I thought about it, on Ethereum or other mainstream PoS chains, rewards basically auto-enter your effective staked balance. You don’t have to do anything—compounding just happens in the background.
That’s not how it works on Dusk. You have to remember to claim. If you’re running an automated, unattended node, you might forget. Or if you’re a less active small staker, you might never even think about it. The result is that your rewards remain stuck in a “pending claim” state forever, wasting your chance to compound.
It’s kind of like putting money in a savings account: the interest is there every month, but it doesn’t automatically transfer back to your principal. You have to do it yourself. Most modern banks have already automated this. Here, though, it requires manual action.
For small stakers, this really is an invisible loss of returns. The rewards are there, but you’re not fully using them. For institutions, it might not be a big issue—they likely have systems that remind them. But for individual stakers, especially those who aren’t very engaged, this is real opportunity cost.
To be clear: I only tried claiming once or twice on the testnet and didn’t track long-term how much compounding you’d lose if you forget. And I also can’t verify whether this flow changes on the mainnet.
I’m still wondering—does this “you need to remember to claim” design exist for technical or compliance reasons, or is it just an early product decision? If it’s truly necessary, it creates an invisible rewards gap between small stakers and institutional stakers.
@Dusk $DUSK #dusk
The rewards don’t auto-compound. They accumulate in your account, but they only become actual staked assets when you actively go in and claim them. If you never click that claim button, the rewards just sit there: they don’t grow and they don’t compound.
At first I thought it was just a UI/UX design choice. But when I thought about it, on Ethereum or other mainstream PoS chains, rewards basically auto-enter your effective staked balance. You don’t have to do anything—compounding just happens in the background.
That’s not how it works on Dusk. You have to remember to claim. If you’re running an automated, unattended node, you might forget. Or if you’re a less active small staker, you might never even think about it. The result is that your rewards remain stuck in a “pending claim” state forever, wasting your chance to compound.
It’s kind of like putting money in a savings account: the interest is there every month, but it doesn’t automatically transfer back to your principal. You have to do it yourself. Most modern banks have already automated this. Here, though, it requires manual action.
For small stakers, this really is an invisible loss of returns. The rewards are there, but you’re not fully using them. For institutions, it might not be a big issue—they likely have systems that remind them. But for individual stakers, especially those who aren’t very engaged, this is real opportunity cost.
To be clear: I only tried claiming once or twice on the testnet and didn’t track long-term how much compounding you’d lose if you forget. And I also can’t verify whether this flow changes on the mainnet.
I’m still wondering—does this “you need to remember to claim” design exist for technical or compliance reasons, or is it just an early product decision? If it’s truly necessary, it creates an invisible rewards gap between small stakers and institutional stakers.
@Dusk $DUSK #dusk
