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
      • Delegate Guide
      • RAF1 Guide
    • The OBOL Token
      • Token Utility
      • Token Distribution & Liquidity
      • 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
  • Overview of the Obol RAF:
  • Step 1: Scoping
  • Step 2: Application Registration
  • Step 3: Application Review
  • Step 4: Voting
  • Step 5: Tallying Results
  • Step 6: Compliance
  • Step 7: Funding distribution
  • Step 8: Community retrospective
  • Guides for each Round
Edit on GitHub
  1. Community & Governance
  2. Governance

The RAF

The RAF

PreviousThe Token HouseNextDelegate Guide

Last updated 5 days ago

Obol’s Retroactive Funding (RAF) mechanism is designed to strengthen and promote the decentralisation of Ethereum's settlement layer by rewarding projects that add value and drive impact for Ethereum’s decentralisation. Read more about the Obol RAF .

Voting and funding distributions occur over a series of Obol Retroactive Fund (RAF) rounds, with OBOL token Delegates determining how funds from the RAF are allocated. The first RAF round will open in February 2025.

Overview of the Obol RAF:

  • Any project that meets the RAF round’s criteria can make an application.

  • OBOL Token Delegates vote on applications proportional to their delegated power and using .

  • The Obol RAF rounds occur at intervals and include phases for scoping, application creation, application review, voting, and funding distribution.

  • The Obol Association will collect information from projects to distribute grants, including KYC, where required.

Below is described the steps within each RAF round. Each step takes approximately one week.\

Step 1: Scoping

The scope of the round’s impact and the amount of funding to be allocated is defined by the Obol Association at the outset of the round and posted on the Obol Forum.

Step 2: Application Registration

  1. Describe Impact: Specify the category of the project and its impact.

Step 3: Application Review

A subset of OBOL Delegates appointed by the Obol Association reviews applications to ensure compliance with the application rules.

The Obol Association will also review applications to filter out spam or applications that do not align with the mission of the Obol Collective.

Step 4: Voting

OBOL Delegates vote on projects in proportion to their voting power. Here’s how it works:

  1. Eligibility: Every address that has been delegated voting power by OBOL Token holders can submit votes.

Step 5: Tallying Results

Step 6: Compliance

The Obol Association will review the list of selected projects, adjust if necessary and collect information from them to distribute the grant legally compliantly (including completing KYC if required).

Step 7: Funding distribution

The overall reward amount for the round is divided among the winning projects based on the delegates' vote and allocation according to the quadratic funding mechanism.

Step 8: Community retrospective

After each round, The Obol Association will conduct a retrospective and gather community feedback.

Guides for each Round

Projects are invited to create an application on the . Any project or team can apply, but in the future, governance may decide that an application needs to be made by someone holding a minimum amount of OBOL tokens.

Once a RAF round is opened, to apply for the Obol RAF, projects can create an application on by following these steps:

Create an Application: Fill out the application form using the .

Voting Process: Delegates vote using the app. Depending on the type of application being reviewed, a specific set of criteria should be used to judge a project's contributions to the Obol Collective.

The Obol Association will monitor votes to ensure contributors are not voting for projects they are directly involved in or where a substantial conflict of interest may be present. Delegates are expected to act in accordance with the Delegate and the general for the forum.

The voting power of each OBOL Token Delegate is proportional to the amount of OBOL tokens delegated to them. However, the funding results are calculated using , meaning that the square root of the votes is used to determine the final allocation. This approach ensures a broader distribution of funding across the Obol Collective, rather than allowing a small number of winners to dominate.

RAF1: see the in the forum.

RAF App
raf.obol.org
RAF App
raf.obol.org
Rules of Engagement
Code of Conduct
quadratic funding
RAF1 guide
here
quadratic funding