Try   HackMD

Protocol Governance

tags: Overview Governance

Overview

Firechain uses a protocol-based voting mechanism for governance. There are two voting categories: global voting and delegated voting. The weighting of an account's vote is based on the amount of $FIRE held at the time of the vote, and weighting is applied to all elections for members of the global consensus group. Delegated voting is a more involved form of governance that's designed for use by smart contracts. For example, when a contract is deployed, it can designate a certain token whose holders can elect one or more specific nodes, or a specific consensus group, to process and validate the contract's responses.

In addition to the "sealing" of account-level transactions through reference in global blocks, the global consensus group are responsible for performing breaking upgrades at the global level of the Firechain network.

Definitions:

  • Super nodes are members of the global consensus group which are responsible for producing global blocks.
  • Delegate nodes are part of a delegated consensus group and are tasked with producing blocks for delegated accounts (e.g. contracts and EOAs that opt-in).

Voting

For each delegated consensus group, each account can vote for one node. This is done by sending a vote transaction to the protocol's built-in governance contract with a consensus group ID and the node's identifier. After the corresponding response transaction is confirmed by global chain, voting is successfully completed.

Votes are calculated every cycle (1,152 rounds ≈ 24 hours), and users can vote as often as they'd like. The nodes that will serve active consensus roles for next cycle are elected based on the standing vote tally at the moment the prior cycle ends. Votes can be rescinded or cancelled at any time simply by sending a cancel transaction. This design allows for a dynamic consensus layer with immediate feedback: nodes that misbehave get voted out quickly, and good behavior is implicitly rewarded through re-election.

FAQ

Can I vote for multiple super nodes in the global consensus group at the same time?

Each account can only cast one vote for per consensus group per round. In other words, you can cast a vote for one super node in the global group, plus one per delegate group.

If the delegate I voted for isn't eligible for whatever reason, what happens to my vote?

If you've voted for a node that either cancels their registration or loses eligibility for any reason, the election algorithm will discard your vote along with any others it may have received. In other words, your vote for that particular node becomes invalid. You are free to cast a vote for another node if you'd like.

If I don't have any FIRE in my wallet, can I still vote?

Voting is just like other Firechain transactions, which is to say it's free and doesn't consume FIRE. That means you can cast a vote even if you have no FIRE. However, super nodes are elected based on the relative weight of the votes cast for them, and 0 FIRE conveys 0 voting weight, so it won't have any bearing on the outcome of an election.

Who votes for delegates in the public consensus group?

Eligible nodes are randomly assigned to participate in the public consensus group from the global consensus pool, which is to say they're implicitly elected to the public group through super node votes. Specifically, 24 of the top 100 super nodes (ranked by eligible votes received) will be randomly assigned to the public consensus group each round.

Last changed by 
 
Firechain
Firechain is an async dApp platform built to power the open economy.
0
111

Read more

Participating in Consensus

:::info This document explains the high-level concepts involved with running validators, including staking requirements, election criteria, and incentives. Definitions of Terms: Staking: Locking an amount of FIRE of the account for certain purpose. In this document, this is GV registration. One Round: A time period lasting exactly 75 seconds. One Cycle: Exactly 1,152 rounds, which is approximately one day. Staking Address: The candidate's registered and bonded address. Block Creation Address: The candidate's block signing address.

Apr 17, 2023
Firechain.JS - Getting Started

Firechain.js is a JavaScript library for interacting with the Firechain network. It provides a set of simple APIs for things like sending transactions, querying the state of the blockchain, and deploying smart contracts, as well as a set of utility functions for encoding and decoding data. It also provides a set of networking modules for connecting to Firechain nodes. Firechain.js is available as an ES6 module and can be used in both Node.js and the browser. Installation Firechain.js is available as an npm package. We recommend using yarn to install it. yarn add @firechain/firechainjs yarn add @firechain/firechainjs-ws

Dec 9, 2022
Heat Generation

The Firechain Network is a shared resource. It is a public good that is available to all users. In order to ensure that the network is available to all users, Firechain uses a dynamic resource sharing mechanism called Heat. It's a measure of the amount of demand that an account has placed on the network recently. Accounts generate heat when they interact with the network, and that heat dissipates over time automatically. The easiest way to think about Heat is as a form of congestion control which ensures that the network remains useful to the most inclusive group of users possible by way of limiting the load that any one account can put on the network. Understanding Heat Most blockchains require accounts to pay some sort of fee in order to transact over the network, primarily to prevent spam and misuse of the network's resources. Firechain does not use transaction fees. Instead, we developed the concept of heat which enables the network to operate without economic barriers that can be untenable for a large percentage of the population. To obtain heat capacity, you can: Stake FIRE (staking ~268 FIRE grants about 1 transaction per minute); or Produce a PoW solution to generate transient heat capacity when you need it.

Nov 28, 2022
Creating a Genesis File

Here's an example that produces content for a genesis.json file that can be used to spin up a new chain. It described a simple setup wherein 2 global and 2 are selected in each round and each is responsible for producing 3 consecutive blocks. The selection of GVs is based on the proportional distribution of delegate votes. This example has one "pinned" validator that's always picked, and the other is randomly selected from delegates whose weighted rank falls in the top 100. In order to be eligible, validators must register and stake at least 5000 FIRE for 1 Epoch (5,184,000 blocks ≈ 3 months) to become bonded. :::info This is a complete example, meaning you can use it to spin up a node. ::: const genesisConfig = { // Feature Flags

Nov 16, 2022
Read more from Firechain
Published on HackMD