Voting Power
Last updated
Last updated
Operators receive staking contract shares, which signal their proportional ownership within a specific contract. For consensus to be reached, a supermajority threshold quorum of attestations must be met to successfully execute a given task. Importantly, the value of a share varies between staking contracts, as each corresponds to a different asset with unique economic and security characteristics.
Dynamic Voting Power (DVP) determines an Operator’s influence in the consensus process, proportional to the amount of (re)staked assets securing the network. It is calculated by summing the total value of all assets (re)staked by an Operator, each weighted by its respective multiplier.
The multiplier reflects the asset’s value within the staking contract. By multiplying the staked amount and the asset’s price, the USD equivalent of the staked assets in that contract is derived, which is then used to determine voting power.
A consensus-based mechanism that calculates the fluctuations in asset value and changes in an Operator’s stake. A quorum continuously monitors and updates the voting power of individual Operators, with updates finalized through consensus among Operators within the network. This process is executed using Internal Tasks within the CLI.
Total voting power is the sum of voting power of all the operators. If the total voting power of the Task Definition is zero, the task will revert with InvalidRequiredVotingPower error.
Minimum Voting Power
The AVS can set a policy of requirements for minimum voting power per task to participate in the AVS (register / work).
When building a PoS (proof of stake) network, you can often run into a problem where a particular operator has a disproportionately large amount of voting power, such that their vote can drastically swing the outcome.
If an operator registers with more than the max effective balance that you set, its voting power is set to that value. This way, you can have an operator set where a single operator's voting power does not dominate over the consensus of task validation. Check the setMaxEffectiveBalance method to set it for your AVS.
Formula for Voting Power with max effective balance:
The main feature for dual staking. The AVS developer can set a policy of requirements for minimum amount of shares per strategy that operators must (re)stake to participate in the AVS.
