Voting Power
Last updated
Last updated
Othentic Stack allows AVS builders to configure a policy of requirements that Operators need to meet for registration, consensus roles (i.e. Performer, Attester, Aggregator), and certain types of tasks.
Operator Voting Power:
To fit the consensus engine into the shared security environment, the Operator's voting power is proportional to the amount of (re)stake assets locked on the L1, which is referred to as “dynamic voting power”.
The influence of each Operator in the consensus process is determined directly by the voting power.
Here's the formula to illustrate the voting power calculation:
Voting power equals the sum of all the staked funds on the L1 multiplied by each Staked Amount's respective Multiplier. Various factors and network-specific rules can determine the multiplier.
Minimum Voting Power
The AVS can set a policy of requirements for minimum voting power per task to participate in the AVS (register / work).
Total Voting Power
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.
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.
Formula for Voting Power with max effective balance:
Minimum Shares Per Strategy
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.
