Validator Performance Data Feed
General Information
What is the nature of the proposed bounty?
A small, open-source tool that pulls raw per-minipool validator performance data (attestation effectiveness, missed proposals, sync committee participation) from the beacon chain and publishes it as a structured, queryable JSON/API feed. This is a narrow, well-bounded data-pipeline task — not analysis or alerting, just clean, reusable data export.
Why are you writing this bounty proposal?
The Saturn 2 scoping discussion identified protecting rETH yield from underperforming validators as a current community priority. A clean, public performance data feed is a small but genuinely useful building block toward that goal — usable by dashboards, alerting tools, researchers, or individual node operators, regardless of who builds it. I am separately proposing a related grant this round (rETH Yield Guard) for the analysis/alerting layer, but this bounty is independently useful and not dependent on that grant being funded.
Benefit
| Group | Benefits |
|---|---|
| Potential rETH holders | Supports the broader goal of protecting rETH yield by enabling better visibility into validator performance network-wide. |
| rETH holders | Indirectly benefits from any tooling built on top of this data that helps catch yield-eroding underperformance sooner. |
| Potential NOs | Public performance benchmarks give new operators a clear reference point. |
| NOs | Can self-check their own minipool performance against network data without building custom tooling. |
| Community | A reusable, open data feed lowers the barrier for anyone building future monitoring/analysis tools. |
| RPL holders | N/A — indirect benefit only via broader rETH yield protection. |
Which other non-RPL protocols, DAOs, projects, or individuals would stand to benefit from the bounty being successfully completed?
Any developer or researcher studying Ethereum validator performance broadly could reuse the data pipeline pattern.
Work
What steps would be entailed in completing the bounty? Do successful examples of such work exist elsewhere? What skillsets or knowledge will be required?
Steps: query beacon chain data (via a public beacon API or existing indexer) for all Rocket Pool minipool validators, compute standard performance metrics (attestation effectiveness, proposal success rate, sync committee participation), and publish as a structured JSON feed with a simple query interface. Similar validator performance dashboards exist for the broader Ethereum network (e.g. beaconcha.in), but none are scoped specifically to Rocket Pool minipools as an open, reusable data feed. Requires familiarity with beacon chain APIs/data structures and basic API/data-service development in any language.
What advice would you give a bounty hunter working on this bounty?
Reuse an existing beacon chain indexer or public API where possible rather than building chain-indexing infrastructure from scratch — the value here is in the Rocket Pool-specific aggregation and clean export format, not in re-implementing indexing.
Should the output of this bounty be available under an open source license?
Yes, MIT or similar permissive license.
Costs
How much do you think the completion of this bounty is worth to Rocket Pool (in USD)?
$1,200 — reflects a small, well-scoped data pipeline task achievable in roughly 3-5 days of focused work by a developer with beacon chain API familiarity.
How much work will be needed to verify this bounty has been completed? What skillsets or knowledge will be required?
Straightforward — spot-check the feed’s output against a handful of known minipools’ actual on-chain performance data. Requires basic familiarity with beacon chain data to sanity-check; roughly 30-60 minutes of review.
Structure
How would you structure this bounty, and why?
A single payout to a single team/individual on completion. The scope is small enough that milestones would add overhead without meaningful benefit.
Is this bounty repeatable?
No — a single canonical data feed is the goal. Ongoing maintenance/hosting could be proposed separately later if the feed proves useful and needs long-term support.
Are there any reasonable circumstances under which this bounty should be withdrawn? Should it expire?
Yes — if no submission is received within roughly 2 months, or if an existing tool is identified that already adequately serves this need, the bounty should be withdrawn or reconsidered.
Conflicts of Interest
Does the person or persons proposing the bounty have any conflicts of interest to disclose?
I (Mahmud Bello, GitHub: mahmudsudo) am proposing this bounty and may also attempt to claim it myself. I am also proposing a related but independently-scoped grant this round (rETH Yield Guard). I am not a member of the GMC.
Will the applicant, or any protocol or project in which the applicant has a vested interest (other than Rocket Pool), benefit financially if the bounty is successfully completed?
Only insofar as I may claim the bounty payout myself if I complete the work, consistent with the open, first-to-complete nature of the bounty structure.