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
  • AVS Governance Multisig
  • Operations Multisig
  • Community Multisig
  1. AVS Framework
  2. Explainers

Governance Multisig

PreviousOperator Allowlisting

Last updated 2 months ago

We are continuously evaluating best practices for decentralized AVS governance mechanics.

The Governance Multisig account requires the authorization and cryptographic signature of multiple designated parties to perform actions. This security mechanism is commonly denoted as an "x-of-y" multisig, signifying that a minimum of x signatures from a total of y configured signatories are required to execute a transaction.

The ability and responsibility to make decisions regarding contract upgrades, pausing functionality, and adjusting parameters, have been delegated to three main governance multisigs. These multisigs provide a basic yet effective system of transparent governance, ensuring distributed control and accountability.

AVS Governance Multisig

Each AVS holds a Governance Multisig, which can execute routine upgrades and maintenance on all safety-critical actions. The role includes creating new types of tasks, setting slashing rates and conditions, setting tokens issuance, operator whitelisting, deregistering operators, updating AVS metadata, handling funds, and setting additional logic-specific rules to the AVS.

Operations Multisig

The Operations Multisig can execute routine code upgrades and maintenance. It can also pause Othentic functionality in emergency situations.

Operations Multisig: 0x74d9fB2B522cF886872AC333480Dc4779A4bb214

Community Multisig

The Community Multisig committee comprised of credibly neutral signatories. Under normal circumstances, the Community Multisig acts primarily as an observer, receiving regular updates on the Operations Multisig's transactions. However, in extraordinary circumstances, the Community Multisig has the authority to enact an emergency pause of AVS actions, effectively halting the AVS contracts.

Community Multisig: 0x17e49Fe369062d1eecA9564e5451021da778739B

The Community Multisig members include:

  • Jonathan King - Coinbase

  • Arik Galansky - Fireblocks

  • Anna Petrenko - Everstake

  • Artemiy Parshakov - P2P.org

  • Adam Winnick - Finality Capital

  • Eylon Aviv - Collider