Othentic
  • Introduction
    • Introducing Othentic Stack
    • Use Cases
  • AVS Framework
    • Abstract
    • Quick Start
    • Othentic CLI
      • Key Management
      • Contracts Deployment
      • Operator Registration
      • AVS Logic Implementation
      • Operator Deposit
      • Node Operators
      • Rewards Distribution
      • P2P Config
        • Custom P2P Messaging
        • P2P Auth Layer
        • Metrics and Monitoring
        • Logging
        • Persistent storage
        • Latency
      • CLI Command Reference
    • Smart Contracts
      • AVS Governance
      • Attestation Center
      • Hooks
        • Task Logic
        • Operator Management
        • Rewards Fee Calculator
      • OBLS
      • Othentic Registry
      • Message Handlers
    • Othentic Consensus
      • Abstract
      • Task & Task Definitions
      • Leader Election
      • Proof of Task
      • Execution Service
      • Validation Service
      • Voting Power
      • Rewards and Penalties
      • Internal Tasks
    • FAQ
    • Supported Networks
    • Explainers
      • Networking
      • Multichain
      • Production Guidelines
      • Operator Allowlisting
      • Governance Multisig
  • External
    • AVS Examples
  • GitHub
  • Othentic Hub
Powered by GitBook
On this page
  • Overview
  • Dynamic Voting Power (DVP)
  • Staking Contract Multiplier
  • Validated Voting Power (VVP)
  • Total Voting Power
  • Minimum and Maximum Voting Power
  • Minimum Shares Per Strategy
  1. AVS Framework
  2. Othentic Consensus

Voting Power

PreviousValidation Service NextRewards and Penalties

Last updated 2 months ago

Overview

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)

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.

Staking Contract Multiplier

The staking multiplier is a configurable weight applied to a specific staking contract. It adjusts the influence, staked tokens from that contract have, in governance or voting mechanisms.

In systems where multiple staking contracts exist—across networks or staking products—not all staked tokens are treated equally. The multiplier allows protocol teams to assign relative importance to each contract, acting as a scaling factor for voting power.

By default, all staking contracts have a multiplier of 1, meaning each token contributes 1:1 to voting power unless otherwise configured.

Key Characteristics

  • Positive Value: Must be a positive, non-zero number (e.g. 2, 5, 10). It ensures no staked tokens can nullify voting power.

  • Custom Governance Weighting: A higher multiplier increases the voting power per staked token, while a lower multiplier reduces it. For example, a multiplier of 2 means each token staked in that contract contributes the equivalent of two tokens in voting power.

  • Reflects Risk, Trust, or Strategy: Use multipliers to

    • Reward long-term or high-risk staking.

    • Deprioritize newer or untested contracts.

    • Balance influence across diverse token-holder communities.

  • Dynamically Updatable: Multipliers can be adjusted over time to reflect evolving trust models, risk assessments, or governance priorities.


Validated Voting Power (VVP)


Total Voting Power

Minimum and Maximum Voting Power

Minimum Voting Power

The AVS can set a policy of requirements for minimum voting power per task to participate in the AVS (register / work).

Maximum Effective Balance

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.

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.

You can set the multiplier for a staking contract by using the CLI command.

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 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 error.

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 method to set it for your AVS.

Internal Tasks
InvalidRequiredVotingPower
setMaxEffectiveBalance
set-staking-contract-multiplier