Poolscan Docs
  • Summary
  • DOCUMENTATION
    • Learn about the PSC Blockchain Platform
      • PSC Blockchain Overview: vision, strategy and platform components
      • The PSC Blockchain
        • Discovering the Network
        • PSC Blockchain Consensus
        • Delegation through Staking with Validators
        • Ethereum (EVM) Compatibility and Smart Contracts
        • Boosting PSC Blockchain's Scalability
      • PSC Blockchain Token (PSC)
        • PSC Tokenomics
        • Exchanges, Wallets, On-Ramps and DeFi Tools Supporting PSC
        • PSC on Other Chains
      • Interoperability
      • PSC Blockchain Governance and Development
        • PSC Blockchain Assembly
        • PSC Blockchain Improvement Proposals (FIPs)
      • Wallets supporting PSC Blockchain
    • PSC Blockchain for Business
    • Things you can do on PSC Blockchain
      • Interacting with the PSC Blockchain
      • PSC Blockchain Ecosystem
      • Community
      • Grants and Bounties
    • PSC Blockchain Mobile Infrastructure Use Cases
  • Developers
    • Network Details
      • PSC Blockchain Mainnet
      • PSC Blockchain Testnet
      • Token Faucets
    • PSC Blockchain Consensus
      • Contracts Overview
      • Stake, Delegate and Withdraw
      • End-of-Cycle Flow
      • Contract Addresses
    • How to run network nodes
    • Resources & Tools
      • WalletConnect on PSC Blockchain
    • How to become a validator
      • Getting started as a validator
      • Getting started as on the PSC Blockchain testnet
  • Links
    • Facebook
    • GitHub
    • Telegram
    • Twitter
Powered by GitBook
On this page
  • Consensus - 0xC48b6EAECd49959235dE3DE5C73974079d2Be325
  • Block Reward - 0xF3f4A70EE8cFE0A1F28B59B2d85c505c1d32bcbB
  • Voting - 0x26a48c9D3A8C90132B2Ab5904850679F157b7991
  • Proxy Storage - 0x0DfD2e7fffCA07655e3F5600dC53e0D8cF0B7D98
  1. Developers

PSC Blockchain Consensus

PreviousToken FaucetsNextContracts Overview

Last updated 1 year ago

Consensus is a fault-tolerant mechanism that is used in blockchain systems to achieve the necessary agreement on the single state of the network. PoolScan Network Coin network is using a (DPoS) consensus model. DPoS is a variation of consensus. In PoS there are a set of validators that are responsible for keeping the network updated and validating the network's state. They do this in turns, every validator has their turn in line. On their turn the validator updates the network's state, and the rest of the validators check that the update is valid.

Consensus contract is used to manage the list of the network validators and delegators

BlockReward contract is calculates the reward amount that validators and delegators will receive on each block validation. The reward size is proportional to validator's stake.

With Voting contract validators are vote on various changes on these 3 base level contracts. All those contracts are proxied with implementation that handles the logic. The implementations can be changed only by the Voting process.

The bridge is used to transfer the PoolScan Network Coin native token between PoolScan Network Coin and Ethereum networks.

This contract is responsible for handling the network DPos consensus. The contract stores the current validator set and chooses a new validator set at the end of each cycle. The logic for updating the validator set is to select a random snapshot from the snapshots taken during the cycle.

The snapshots are taken of pending validators, who are those which staked more than the minimum stake needed to become a network validator. Therefore the contract is also responsible for staking, delegating and withdrawing those funds.

Stake amount for a validator is the sum of staked and delegated amount to it's address.

minimum stake amount = 100,000 PoolScan Network Coin token

cycle duration blocks = 57600 (approximately 2 days)

This contract is responsible for generating and distributing block rewards to the network validators according to the network specs (5% yearly inflation).

Another role of this contract is to call the snapshot/cycle logic on the Consensus contract

This contract is responsible for opening new ballots and voting to accept/reject them. Ballots are basically offers to change other network contracts implementation.

Only network validators can open new ballots, everyone can vote on them, but only validators votes count when the ballot is closed.

Ballots are opened/closed on cycle end.

max number of open ballots = 100

max number of open ballots per validator = 100 / number of validators

minimum ballot duration (cycles) = 2

maximum ballot duration (cycles) = 14

This contract is responsible for holding network contracts implementation addresses and upgrading them if necessary (via voting).

This contract is based on non-reporting ValidatorSet .

This contract is based on BlockReward .

Consensus - 0xC48b6EAECd49959235dE3DE5C73974079d2Be325
described in Parity Wiki
Block Reward - 0xF3f4A70EE8cFE0A1F28B59B2d85c505c1d32bcbB
described in Parity Wiki
Voting - 0x26a48c9D3A8C90132B2Ab5904850679F157b7991
Proxy Storage - 0x0DfD2e7fffCA07655e3F5600dC53e0D8cF0B7D98
Delegated Proof of Stake
Proof of Stake