#dusk $DUSK @Dusk
I started with the 1,000 DUSK requirement, then got stuck on the wallet setup.
One stake can use two different keys.
The consensus key operates the node. It votes and signs blocks.
The owner key controls the other side: unstaking and withdrawal.
Dusk recommends keeping them separate.
That changed how I was looking at the 1,000 DUSK requirement.
It isn't just capital sitting in a wallet. It's an operating position attached to a machine that has to stay online 24/7 and participate in consensus.
Dusk is separating the authority to operate consensus from the authority to control the stake.
Compromising the consensus side doesn't automatically give control of the stake.
The trade-off is interesting.
The security boundary gets better. The recovery path gets harder.
If a provisioner has to be migrated or recovered under time pressure, how do operators keep that separation intact without losing their consensus role?
I started with the 1,000 DUSK requirement, then got stuck on the wallet setup.
One stake can use two different keys.
The consensus key operates the node. It votes and signs blocks.
The owner key controls the other side: unstaking and withdrawal.
Dusk recommends keeping them separate.
That changed how I was looking at the 1,000 DUSK requirement.
It isn't just capital sitting in a wallet. It's an operating position attached to a machine that has to stay online 24/7 and participate in consensus.
Dusk is separating the authority to operate consensus from the authority to control the stake.
Compromising the consensus side doesn't automatically give control of the stake.
The trade-off is interesting.
The security boundary gets better. The recovery path gets harder.
If a provisioner has to be migrated or recovered under time pressure, how do operators keep that separation intact without losing their consensus role?