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

Ubit Consensus

PreviousFIP'sNextContracts 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. Ubit network is using a Delegated Proof of Stake (DPoS) consensus model. DPoS is a variation of Proof of Stake 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 Ubit native token between Ubit and Ethereum networks.

Consensus - 0x7eFA0D9149dcAcD0A15F265C0152842b6dBaEDED

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.

This contract is based on non-reporting ValidatorSet described in Parity Wiki.

minimum stake amount = 10,000 Ubit token

cycle duration blocks = 57600 (approximately 2 days)

Block Reward - 0x1132A6B3D704D00683112D2eA03862C64940d337

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 based on BlockReward described in Parity Wiki.

Voting - 0xD212f646A2C5ab586038568A9cfE5BD187fDe91D

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

Proxy Storage

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