LogoLogo
SDKAPI
Next
Next
  • 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
  • Token Contract
  • Official Uniswap Pool
  • Verified Contract Addresses
  • Learn more about...

Was this helpful?

Edit on GitHub
  1. Community & Governance

The OBOL Token

PreviousGrant Track for Establishing OBOL Token’s Role in DeFi & GovernanceNextToken Utility

Last updated 5 days ago

Was this helpful?

The OBOL Token is central to the governance and operation of the Obol Collective. It serves multiple purposes that are essential to its functioning.

OBOL Token Transferability: With the approval of, the OBOL Token is set for a strategic and well-planned unlock. The tokens will be unlocked on the 7th May 2025 at 11:00 UTC, following the completion of centralized exchange listings. Please go to to unlock airdrop tokens.

Token Contract

The official token contract address of the OBOL Token is

Official Uniswap Pool

The official Uniswap Pool for the OBOL Token is

Verified Contract Addresses

The following smart contracts power OBOL staking, governance, and reward distribution on Ethereum mainnet.

Governor Contract
  • Address:

  • Purpose: Manages onchain proposal lifecycle and voting logic for Token House governance.

  • What you can find onchain:

    • Voting thresholds

    • Quorum settings,

    • Delay/period configs,

    • Proposal and vote history.

Obol Staker
  • Address:

  • Purpose: This is the base layer of the Obol staking system. It facilitates the basic mechanics of staking, such as managing deposits, forwarding governance delegation, and streaming rewards based on earning power.

  • What you can find onchain:

    • Total OBOL staked in the contract

    • Stake, earning power, rewards and balances on a granular, per-deposit basis

    • Current reward rate and configuration

    • Contract events (e.g. Staked, Withdrawn)

    • Interactions for staking/unstaking

stOBOL (ERC-20 Token Contract)
  • Purpose: A liquid ERC-20 representation of staked OBOL built on top of the Obol Staker. It adds features like transferability, reward auto compounding, and the ability to use a staked OBOL position in other protocols. Holders retain the ability to delegate their staked tokens to the governance delagate of their choice.

  • What you can find onchain:

    • ERC-20 metadata (name, symbol, decimals)

    • Total supply and balances

    • Transfer history

    • Allowances / approvals

    • Voting power interface (via getVotes and delegates)

    • Event logs for delegation changes

Reward Notifier
  • Purpose: Manages the distribution of tokens to the staking contract so they can be streamed as rewards to stakers.

  • What you can find onchain:

    • Current and past reward rate values

    • Administrative role settings (who can push updates)

    • Timing/config changes made through proposals

    • Events like RewardRateUpdated

Auto Delegate (Overwhelming Support Strategy)
  • Purpose: Implements the “Overwhelming Support” auto-delegation strategy. This contract casts votes on behalf of un-delegated or transferred stOBOL when proposals receive strong community support. This mechanism uses tokens that would otherwise not be available in governance to ensure uncontroversial proposals will meet quorum.

  • What you can find onchain:

    • Parameters like supportThreshold, subQuorumBips, and votingWindow

    • Proposals voted on by the strategy

    • Vote power amounts cast

    • Event logs showing execution activity

    • Wallets or protocols interacting with auto-delegation logic

Learn more about...

Address:

Address:

Address:

OIP-2
claim.obol.org
0x0B010000b7624eb9B3DfBC279673C76E9D29D5F7
https://app.uniswap.org/explore/pools/ethereum/0x57F52C9faa6D40c5163D76b8D7dD81ddB7c95434
0xcB1622185A0c62A80494bEde05Ba95ef29Fbf85c
0x30641013934ec7625c9e73a4D63aab4201004259
0x6590cBBCCbE6B83eF3774Ef1904D86A7B02c2fCC
0x384dd81047F88eE35DE75DA1149943B8e62d8802
0xCa28852B6Fc15EbD95b17c875D5Eb14b08579158
Token Utility
Staking & stOBOL
Token Distribution & Liquidity
Token Holders FAQ
TGE FAQ