Blokista Docs
  • Summary
  • DOCUMENTATION
    • Learn about the Blokista Platform
      • Blokista Overview: vision, strategy and platform components
      • The Blokista Blockchain
        • Discovering the Network
        • Blokista Consensus
        • Delegation through Staking with Validators
        • Ethereum (EVM) Compatibility and Smart Contracts
        • Boosting Blokista's Scalability
      • Blokista Token (BCC)
        • BCC Tokenomics
        • Exchanges, Wallets, On-Ramps and DeFi Tools Supporting BCC
        • BCC on Other Chains
      • Interoperability
      • Blokista Governance and Development
        • Blokista Assembly
        • Blokista Improvement Proposals (FIPs)
      • Wallets supporting Blokista
    • Blokista for Business
    • Things you can do on Blokista
      • Interacting with the Blokista Blockchain
      • Blokista Ecosystem
      • Community
      • Grants and Bounties
    • Blokista Mobile Infrastructure Use Cases
  • Developers
    • Network Details
      • Blokista Mainnet
      • Blokista Testnet Spark
      • Token Faucets
      • Network Upgrades
        • Upgrade Guide
        • Upgrade Guide (explorer nodes)
        • Block 13,800,000 Fork
        • FIP's
    • Blokista Consensus
      • Contracts Overview
      • Stake, Delegate and Withdraw
      • Vote
      • End-of-Cycle Flow
      • Contract Addresses
    • How to run network nodes
    • Resources & Tools
      • TheGraph
      • WalletConnect on Blokista
    • Important smart contracts
      • Blokista Token
      • Blokista Dollar
      • Major Deployed Contracts
      • Bridges
        • Ethereum ↔ Blokista GoodDollar Token
        • Ethereum ↔ Blokista BCC20 Tokens
        • BSC ↔ Blokista BNB
        • BSC ↔ Blokista Native
        • BSC ↔ Blokista BCC20
        • Ethereum ↔ Blokista Native
    • How to become a validator
      • Getting started as a validator
      • Getting started as on the Blokista testnet
  • Links
    • Discord
    • Facebook
    • GitHub
    • LinkedIn
    • Medium
    • Telegram
    • Twitter
    • YouTube
Powered by GitBook
On this page
  • Sybil protection and incentives via delegated proof of stake
  • The AuRa Consensus Model
  1. DOCUMENTATION
  2. Learn about the Blokista Platform
  3. The Blokista Blockchain

Blokista Consensus

PreviousDiscovering the NetworkNextDelegation through Staking with Validators

Last updated 2 years ago

Consensus refers to the agreement process between nodes in a network. The nodes must agree on which transactions to include in the next block on the chain before these transactions are committed.

There are 2 aspects to the process - the actual consensus mechanism to add transactions to blocks, and Sybil protection and validator incentives.

Sybil protection and incentives via delegated proof of stake

Blokista uses delegated Proof of Stake (dPoS) to provide Sybil protection and align the validator incentives.

In order to participate in securing the network consensus, a node operator must stake a minimum required amount of BCC tokens (currently set at 100,000 BCC). Becoming a validator on Blokista is permissionless, meaning that a node operator just needs to satisfy certain technical requirements. The need to stake BCC ensures that an entity cannot create multiple seemingly distinct validators without incurring a significant cost. Hence, the Sybil protection. Currently, the maximum number of validators on Blokista is 100.

The validator who publishes a block agreed upon during a given consensus round is rewarded by the network protocol in newly minted BCC tokens. They also receive the fees users paid for the transactions included into the block.

Over time, validators can expect to publish a share of blocks equal to their share of the overall stake. Since BCC uses dPoS, a validator can increase their share by attracting BCC tokens from delegators. The mechanics of delegation on BCC are discussed in more detail on the .

Validators who violate the consensus rules (by, for instance, not revealing random numbers) can expect their stake (including the delegators' contribution) to be frozen. This provides a strong incentive for validators to behave in the desired manner.

The AuRa Consensus Model

Blokista currently uses Parity's AuRa (Authority Round) to append blocks to Blokista. This consensus mechanism is also notably used by the xDAI blockchain.

In this model, the validators take turns signing blocks. A signed block is broadcast to all validators, and if the majority agree it is valid, it is added to the chain. A new block is added every 5 seconds, regardless of whether any transactions occurred during that time.

Although, in theory, achieving transaction finality in this model may take some time, for practical purposes, a transaction on Blokista can be considered finalized after a single block confirmation.

\

following page
consensus model