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. Technology

Consensus

What is 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, also ensuring the security of the entire blockchain network. KardiaChain uses the DP0S-BFT (Delegated Proof of Stake-Byzantime Fault Tolerance) consensus algorithm. The consensus is divided into two periods: DPoS and BFT.

DPOS (Delegated Proof of Stake)

The DPoS is maintained through the election process. The stakeholders use their coins to vote for “Consensus Delegators” who will secure the network on their behalf. These “Consensus Delegators” may also be referred to as the Proposer-Validators who are responsible for achieving consensus during the generating and validating of new blocks. The voting power is proportional to the number of coins that each Proposer-Validator possesses. Thus, DPoS implements a real solution for a true consensus and democratic voting system. The advantage of DPoS :

  • will save computing power and energy efficiency.

  • consensus takes place more quickly.

BFT (Byzantime Fault Tolerance)

The BFT is important to the blockchain because it safeguards against faulty nodes or even destructive ones still maintain the operation. With BFT, it is possible to reach unambiguous finality under all network conditions so long as more than ⅔ of participants agree to the outcome of the block‘s information. The BFT protocol includes:

  • Propose a block

  • All participants acknowledge that

  • The block is finalized and added to the chain when receiving more than ⅔ committed vote from the participants.

PreviousTechnologyNextKardia Virtual Machine (KVM)

Last updated 4 years ago

Was this helpful?