LogoLogo
SDKAPI
Version-v1.4.0 (current)
Version-v1.4.0 (current)
  • Learn
    • Introduction
      • Obol Collective
      • OBOL Incentives
      • Key Staking Concepts
      • Obol vs Other DV Implementations
      • Obol Splits
      • DV Launchpad
      • Frequently Asked Questions
    • Charon
      • Introduction to Charon
      • Distributed Key Generation
      • Cluster Configuration
      • Charon Networking
      • CLI Reference
    • Futher Reading
      • Ethereum and Its Relationship With DVT
      • Community Testing
      • Peer Score
      • Useful Links
  • Run a DV
    • Quickstart
      • Quickstart Overview
      • Create a DV Alone
      • Create a DV With a Group
      • Push Metrics to Obol Monitoring
    • Prepare to Run a DV
      • How and Where To Run DVs
      • Deployment Best Practices
      • Test a Cluster
    • Running a DV
      • Activate a DV
      • Update a DV
      • Monitoring Your Node
      • Claim Rewards
      • Exit a DV
    • Partner Integrations
      • Create an EigenLayer DV
      • Create a Lido CSM DV
      • DappNode
  • Advanced & Troubleshooting
    • Advanced Guides
      • Create a DV Using the SDK
      • Migrate an Existing Validator
      • Enable MEV
      • Combine DV Private Key Shares
      • Self-Host a Relay
      • Advanced Docker Configs
      • Beacon node authentication
    • Troubleshooting
      • Errors & Resolutions
      • Handling DKG Failure
      • Client Configuration
      • Test Commands
    • Security
      • Overview
      • Centralization Risks and Mitigation
      • Obol Bug Bounty Program
      • Smart Contract Audit
      • Software Development at Obol
      • Charon Threat Model
      • Contacts
  • Community & Governance
    • Governance
      • Collective Overview
      • The Token House
      • The RAF
        • RAF #1
      • Delegate Guide
      • Grants Program
        • How to create a proposal in Questbook?
        • Grant Track for Boosting Obol DV Adoption
        • Grant Track for Strengthening the Collective: Operators & Community Growth
        • Grant Track for Establishing OBOL Token’s Role in DeFi & Governance
    • The OBOL Token
      • Token Utility
      • Staking & stOBOL
      • Token Distribution & Liquidity
      • Token Holders FAQ
      • TGE FAQ
    • Community
      • Staking Mastery Program
      • Techne
    • Contribution & Feedback
      • Filing a Bug Report
      • Documentation Standards
      • Feedback
  • Walkthrough Guides
    • Walkthroughs
      • Walkthrough Guides
  • SDK
    • Intro
    • Enumerations
      • FORK_MAPPING
    • Classes
      • Client
    • Interfaces
      • ClusterDefinition
      • RewardsSplitPayload
    • Type-Aliases
      • BuilderRegistration
      • BuilderRegistrationMessage
      • ClusterCreator
      • ClusterLock
      • ClusterOperator
      • ClusterPayload
      • ClusterValidator
      • DepositData
      • DistributedValidator
      • ETH_ADDRESS
      • OperatorPayload
      • SplitRecipient
      • TotalSplitPayload
    • Functions
      • validateClusterLock
  • API
    • What is this API?
    • System
    • Metrics
    • Cluster Definition
    • Cluster Lock
    • State
    • DV Exit
    • Cluster Effectiveness
    • Terms And Conditions
    • Techne Credentials
    • Address
    • OWR Information
  • Specification
Powered by GitBook
On this page
  • Our Vision: Pragmatic Decentralization
  • Inspiration
  • Principles We Follow
  • Governance Tools
  • Governance Sections

Was this helpful?

Edit on GitHub
  1. Community & Governance

Governance

PreviousContactsNextCollective Overview

Last updated 2 days ago

Was this helpful?

The Obol Collective is building a decentralized governance system rooted in the core values of Web3: transparency, openness, collaboration, and community-led decision making. At the same time, we recognize that decentralization is a journey, not a switch. Our aim is to progressively decentralize Obol governance in a way that is sustainable, resilient, and free of the common pitfalls that have emerged in the ecosystem.

Our Vision: Pragmatic Decentralization

We are here to stay. And we believe the only way to build a resilient and successful decentralized collective is to start by building a strong foundation. In recent months, many leading DAOs have experienced operational bottlenecks, inefficiency, and growing pains from decentralizing too fast, too early. The result? Several are now walking back toward more centralized structures to regain coordination capacity, accountability, and operational agility.

We’ve learned from these examples. Our approach is different: we are deliberately not rushing into maximal decentralization. Instead, we are laying the groundwork for progressive, sustainable decentralization over time.

At this stage of the Collective, execution matters. Proposals are already going through governance processes, but the Obol Association still holds executional authority to move quickly where needed. We see this as a temporary and necessary condition to keep building and shipping. This balance, transparent governance with accountable execution, is critical to avoid decision paralysis.

Governance at Obol is not about decentralization for its own sake. It is about enabling the best decisions for the long-term health of the network. As emphasized in the , decentralization without shared purpose or coordination leads to deadlock. We aim to build a governance model that supports rather than hinders progress.

Inspiration

We draw inspiration from both the successes and challenges of other DAOs. In particular:

  • , Introduced “Arbitrum Aligned Entities” to fix governance gridlock by assigning execution to focused teams, while keeping strategic control with the DAO. A response to over-decentralizing too quickly and losing operational clarity.

  • , Proposed the Compound Foundation to help the DAO coordinate services, manage treasury execution, and maintain continuity — moving from pure DAO toward a hybrid model with accountable support.

These initiatives reinforce our belief that progressive decentralization, aligned with clear domain ownership and accountable entities, leads to more sustainable governance.

Principles We Follow

  • Decentralization is a means, not an end. Governance exists to serve the network, not to complicate it.

  • Stakeholders should govern what they understand. Validators and technical contributors guide protocol upgrades; token holders lead incentive and treasury decisions.

  • Social consensus is paramount. On-chain votes matter, but upgrades only succeed through real-world coordination and adoption.

  • Structures must evolve with the protocol. Governance at genesis won’t look like governance at maturity. We are building toward that future in deliberate steps.

Governance Tools

To support transparent decision-making and empower active participation, here are key tools used across the Collective:

Governance Sections

The Obol governance documentation is organized into the following sections:

  • Collective Overview – framing the governance bodies, roles, and progressive decentralization pathway

  • The Token House – the token-holder-based decision-making layer of the Collective

  • The RAF – information for delegates participating in the Retroactive Funding Program (RAF)

  • Grants Program – the Obol funding mechanism for contributors and ecosystem support, led by the Obol Association

Together, we are building governance for the long term.

– for proposal discussion and coordination

– to delegate or vote on proposals

– to track voting data and delegate participation

– to stake OBOL and receive stOBOL

– to access key info and metrics about delegates

These sections evolve as the governance process matures. For any feedback, ideas, or questions, we invite you to join the discussion on the or reach out via .

Bell Curve governance roundtable
Arbitrum DAO
Compound
Governance Forum
Voting Portal
Dune Dashboard
Staking Portal
0xretro.xyz
Forum
Discord