KardiaChain Docs
Search…
KardiaChain Docs
Introduction
Technology
For Users
KardiaChain Proposer Validator Selection Process
Staking
Transaction Fee
Wallets
For Developers
Tutorials
SDK
RPC
KardiaID Service
Archived Docs
Golang SDK
Network
KVM
System requirement
Deployment
KSML
Staking Overview
Delegation period
Consensus
Delegator
Proposer selection procedure
Staking rewards and distributions
Slashing and Jail
Rewards mechanism
Validator
KardiaChain Metamask (extension) Wallet
Powered By GitBook
Staking Overview
KardiaChain uses Delegated Proof of Stake (DPoS) as its mechanism for selecting the validator set. It is designed with the roles of validator and delegator, to maximize security chain. Actors who are interested in maintaining the network can run a validator node. KardiaChain limits the amount of validator slots. The system encourages KAI holders to participate as delegators.
Validators assume the role of producing new blocks, validate blocks, and guarantee finalized. Delegators choose and select validators to delegate with their stakes. KardiaChain will have 20 validators but can change in the future to suit the expansion of the network. The validators are determined by the most delegated delegators to them. The top 20 validator candidates will become KardiaChain validators and participate in the consensus process.
The staking system pays out rewards to all validators and their delegators through execution consensus protocol. If validators double sign, are frequently offline, do not participate in the consensus process their staked (including delegators delegated to them) can be slashed.
Previous
KSML
Next
Delegation period
Last modified 1yr ago
Copy link