KardiaChain Docs
  • Introduction
  • Technology
    • Consensus
    • Kardia Virtual Machine (KVM)
    • Kardia Smart Contract Markup Language
    • Peer to Peer (P2P)
    • Onchain AI
    • NF3 Chip
  • For Users
    • KardiaChain Proposer Validator Selection Process
    • Staking
      • Validators
      • Delegators
      • Disciplines and Rewards
        • Disciplines
        • Rewards
    • Transaction Fee
    • Wallets
      • MetaMask Compatible
      • KardiaChain Mobile App Wallet
      • [Deprecated] KardiaChain Web Wallet
        • [Deprecated] KardiaChain Wallet Extension
  • For Developers
    • Tutorials
      • Platform
        • Running KardiaChain node
        • Private KardiaChain Network
        • KAI Integration for Exchanges
      • Smart contract development
        • Dev environment
          • Solidity
          • IDE and tools
            • Remix
            • Hardhat
            • Truffle
        • Contract verification
      • KRC20 Tokens
        • Deploying KRC20 Token
        • KRC20 token verification
      • KRC721 Tokens
        • Deploy KRC721 tokens
      • Building DApp
        • Frontend
        • Data indexing service
    • SDK
      • Web3
      • [Deprecated] KardiaChain JS SDK
      • [Deprecated] KardiaChain Golang SDK
    • RPC
      • JSON RPC API
    • KardiaID Service
      • KardiaID Service Design
      • KardiaID Service API
  • Archived Docs
    • Golang SDK
    • Network
    • KVM
    • System requirement
    • Deployment
      • Configuration
      • Local
      • Public testnet
      • Mainnet
    • KSML
    • Staking Overview
      • Delegation period
      • Consensus
      • Delegator
        • What is a delegator ?
        • Choose validator
        • Directive of delegator
        • Risk
      • Proposer selection procedure
      • Staking rewards and distributions
        • Block reward distributed
        • Fee distributed
      • Slashing and Jail
      • Rewards mechanism
      • Validator
        • What is a validator ?
        • The different states a validator
        • The responsibility of validator
        • The incentive run a validator
        • To become validator
    • KardiaChain Metamask (extension) Wallet
Powered by GitBook
On this page

Was this helpful?

  1. Archived Docs

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.

PreviousKSMLNextDelegation period

Last updated 4 years ago

Was this helpful?