Hello, dear friends!
You hit Send. Your wallet creates the transaction and broadcasts it to the Dusk network. Nodes validate it and place it in the mempool. A block generator then takes it from the mempool and includes it in a candidate block.
Getting into a block is not the same as being final. The block is accepted and the transaction is executed. It then moves through confirmation and, once the block reaches finality, the transaction becomes immutable and irreversible. Before finality, a block can still be reverted by consensus rules.
So who decides whether the block is valid? Dusk uses Succinct Attestation, a permissionless Proof-of-Stake consensus protocol based on committees. A provisioner proposes a block, a committee validates it, and another committee ratifies the result. Once ratified, the block gets deterministic finality.
And this is where DUSK staking comes in. A provisioner is a staker running a node that can participate in consensus. Direct staking requires at least 1,000 DUSK, and the node must stay online and synchronized. A new stake becomes active after the required epoch boundary, normally within about 6–12 hours. One epoch contains 2,160 blocks.
Rewards are not a fixed APY. They depend on consensus participation and the amount of active stake. Each block reward consists of newly emitted $DUSK plus the transaction fees included in that block.
But staking also means responsibility. Dusk has two types of consensus penalties. A soft penalty can suspend a provisioner and move part of its active stake into locked stake. A hard penalty applies to provably invalid behavior, such as invalid votes or signing conflicting proposals or votes, and can burn part of the stake.
So the journey looks like this:
Send → validation → mempool → block → execution → confirmation → finality.
And underneath it:
$DUSK → stake → provisioner → consensus → finality → rewards — with responsibility attached.
#dusk $DUSK @Dusk
You hit Send. Your wallet creates the transaction and broadcasts it to the Dusk network. Nodes validate it and place it in the mempool. A block generator then takes it from the mempool and includes it in a candidate block.
Getting into a block is not the same as being final. The block is accepted and the transaction is executed. It then moves through confirmation and, once the block reaches finality, the transaction becomes immutable and irreversible. Before finality, a block can still be reverted by consensus rules.
So who decides whether the block is valid? Dusk uses Succinct Attestation, a permissionless Proof-of-Stake consensus protocol based on committees. A provisioner proposes a block, a committee validates it, and another committee ratifies the result. Once ratified, the block gets deterministic finality.
And this is where DUSK staking comes in. A provisioner is a staker running a node that can participate in consensus. Direct staking requires at least 1,000 DUSK, and the node must stay online and synchronized. A new stake becomes active after the required epoch boundary, normally within about 6–12 hours. One epoch contains 2,160 blocks.
Rewards are not a fixed APY. They depend on consensus participation and the amount of active stake. Each block reward consists of newly emitted $DUSK plus the transaction fees included in that block.
But staking also means responsibility. Dusk has two types of consensus penalties. A soft penalty can suspend a provisioner and move part of its active stake into locked stake. A hard penalty applies to provably invalid behavior, such as invalid votes or signing conflicting proposals or votes, and can burn part of the stake.
So the journey looks like this:
Send → validation → mempool → block → execution → confirmation → finality.
And underneath it:
$DUSK → stake → provisioner → consensus → finality → rewards — with responsibility attached.
#dusk $DUSK @Dusk