One World Chain Token Docs
  • Summary
  • DOCUMENTATION
    • Learn about the OWCT Platform
      • OWCT Overview: vision, strategy and platform components
      • The OWCT Blockchain
        • Discovering the Network
        • OWCT Consensus
        • Delegation through Staking with Validators
        • Ethereum (EVM) Compatibility and Smart Contracts
        • Boosting OWCT's Scalability
      • OWCT
        • OWCT Tokenomics
        • Wallets Supporting OWCT
        • OWCT on Other Chains
      • Interoperability
      • OWCT Governance and Development
        • OWCT Assembly
    • OWCT for Business
  • Developers
    • Network Details
      • OWCT Mainnet
      • OWCT Testnet
      • Token Faucets
      • Network Upgrades
        • Upgrade Guide
        • Upgrade Guide (explorer nodes)
        • Block 13,800,000 Fork
        • FIP's
    • OWCT Consensus
      • Contracts Overview
      • Stake, Delegate and Withdraw
      • Vote
      • End-of-Cycle Flow
      • Contract Addresses
    • How to run network nodes
    • Resources & Tools
      • TheGraph
      • WalletConnect on OWCT
    • Important smart contracts
      • OWCT Token
      • OWCT Dollar
      • Major Deployed Contracts
      • Bridges
        • OWCT (Mainnet) <=> OWCT (ETH)
        • OWCT (Mainnet) <=> OWCT (BSC)
        • OWCT (Mainnet) <=> OWCT (BASE)
        • ETH (Ethereum network) <=> ETH (OWCT network)
        • USDT (Ethereum network) <=> USDT (OWCT network)
        • USDC (Ethereum network) <=> USDC (OWCT network)
        • BNB (Binance network) <=> BNB (OWCT network)
    • How to become a validator
      • Getting started as a validator
      • Getting started on the OWCT testnet
  • Links
    • Discord
    • Facebook
    • GitHub
    • LinkedIn
    • Medium
    • Telegram
    • Twitter
    • YouTube
Powered by GitBook
On this page
  • Open a new ballot
  • Check ballot info
  • Vote
  • getQuorumState
  • getAccepted/getRejected
  • activeBallots
  1. Developers
  2. OWCT Consensus

Vote

PreviousStake, Delegate and WithdrawNextEnd-of-Cycle Flow

Last updated 9 months ago

OWCT chain functionality can be changed by voting on the contracts implementations. New implementations can be deployed, and opened to vote by validators for others to decide on whether to accept/reject the changes.

Open a new ballot

In order to open a new vote, a validator needs to call the `newBallot` function on the with the following params:

  • startAfterNumberOfCycles - number of cycles (minimum 1) after which the ballot is open for voting

  • cyclesDuration - number of cycles (minimum 2) for the ballot to remain open for voting

  • contractType

    • 1 - Consensus

    • 2 - BlockReward

    • 3 - ProxyStorage

    • 4 - Voting

  • proposedValue - address of the new implementation deployed for the relevant contract type

  • description - text description which should contain the reason/change introduced in the ballot

Check ballot info

Everyone can check all the ballots that were created using the `getBallotInfo` function. This function receives two params:

  • id - the ballot id

  • key - account address

Vote

Everyone can vote on open ballots, after the start block has passed and until the end block hasn't yet.

It's important to note that at the end of a vote, only validators count towards the final result.

Voting is done by calling the `vote` function, which receives two params:

  • id - the ballot id

  • choice - 1 is accept, 2 is reject

getQuorumState

Returns the state of a specific ballot id: 1 - in progress, 2 - accepted, 3 - rejected

getAccepted/getRejected

Returns the number of accepts/reject of a specific ballot id.

activeBallots

Returns an array of active ballot ids.

Some other useful functions on the are:

voting contract
voting contract
new ballot
getBallotInfo
vote