Documentation
Docs14. Staking & Delegation
14. Staking & Delegation
Kortana uses a Delegated Proof of Stake mechanism to secure the KSC BFT consensus.
14.1 Validator Registration & Self-Stake
To participate in consensus, a node must register as a validator. This requires locking a minimum amount of self-stake (configured via governance parameters). Validators must run an active node and generate BLS consensus keys.
14.2 Delegated Staking
Users who do not wish to run a node can delegate their DNR to an active validator using a DelegateStake transaction.
- Voting Power: Delegating DNR increases the validator's weight in the BFT consensus.
- dPOH Delegation: A specialized
DelegatePoHtransaction exists to allow validators to outsource the computationally heavy SHA-256 hash generation to dedicated generator nodes without risking their consensus voting keys.
14.3 Unbonding Period
To prevent long-range attacks and ensure slashable stake remains locked while disputes are resolved, un-staking (or un-delegating) requires an unbonding period. Funds are locked as unbonding state until the required number of epochs have passed.