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
  2. Staking Overview

Consensus

The consensus is one of the important factors in a blockchain because it will ensure the data consistency of the nodes in the network, ensuring the security of the entire blockchain network. We use the consensus DPoS-BFT (delegated proof of stake - byzantime fault tolerance). The consensus is divided into two periods: DPoS and BFT.

Firstly, we will describe the DPoS. The DPoS includes a vote system where stakeholders are able to vote for delegators that will secure the network on their behalf. These delegators may also be referred to as validators and they are responsible for achieving consensus during the generation and validation of new blocks. The voting power is proportional to the number of coins each user holds. If a validator misbehavior or does not work efficiently, it will be quickly expelled and replaced by another one. Thus DPoS blockchain implements a real solution for a true consensus, democratic voting system. The advantage of DPoS is that it saves energy and consensus takes place more quickly.

Secondly, we will describe the BFT. The BFT is necessary for blockchain because it ensures that even if there are some faulty nodes or even destructive ones, the blockchain network operates normally. With BFT, it is possible to reach unambiguous finality under all network conditions so long as more than ⅔ of participants are honest. The BFT protocol includes:

  1. Propose block

  2. All participants acknowledge that

  3. The block is finalized when received more than ⅔ commit from all participants

PreviousDelegation periodNextDelegator

Last updated 4 years ago

Was this helpful?