MFEV Blockchain Consensus

Consensus is a fault-tolerant mechanism that is used in blockchain systems to achieve the necessary agreement on the single state of the network. MFEV Network is using a Proof of Distribution(POD) consensus model. In POD 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 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 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 MFEV Coin between MFEV Network and Ethereum networks.

Consensus - 0xa0B4785393F6855b12F1bb99C58d8498E1E15cc2

This contract is responsible for handling the network POD 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 MFEV Coin

cycle duration blocks = 57600 (approximately 2 days)

Block Reward - 0xD6b89B6d2d9db8B9EEdD94Aa8dFD80f599c308cE

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.

Voting - 0xEe904A74b1484eBB1339C0aA0328B96A7CCa5A80

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 - 0x3357C518eCFf72E4752DB57156A9d8C9dcf5e192

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