Name of Grant
Megapool Cross-Layer Checker
What is the work being proposed?
ILE Labs proposes to complete and publish an open-source, read-only evidence tool for Rocket Pool Megapool operators.
The tool compares execution-layer Megapool contract state with consensus-layer Beacon Chain validator state and produces structured reports showing:
- validator identity;
- Megapool contract state;
- Beacon Chain validator state;
- withdrawal credentials;
- validator lifecycle status;
- supporting evidence and block references;
- whether operator review may be required;
- whether the result is healthy, actionable, or inconclusive.
The current MVP already performs live Hoodi reads, correlates validator pubkeys across both layers, verifies withdrawal credentials, handles incomplete data conservatively, and produces replayable evidence reports.
The grant would fund the completion of the operator-facing CLI, additional lifecycle coverage, batch reconciliation, evidence capture, testing, and documentation.
Is there any related work this builds off of?
Yes. The project builds on Rocket Pool Megapool contract interfaces, Beacon Chain validator APIs, current Megapool deployment data, and the existing open-source MVP.
Repository: [ REPOSITORY URL]
The current MVP includes live Hoodi captures covering:
- an active validator with matching Megapool and Beacon state;
- a completed-withdrawal state correctly classified as inconclusive where the available contract data is insufficient to prove final accounting.
Will the results of this project be entirely open source?
Yes.
The source code will be published under the repository’s existing Apache-2.0 license.
Benefit
| Group | Benefits |
|---|---|
| Potential rETH holders | Better operator diagnostics can support reliable node operation and the infrastructure underlying rETH. |
| rETH holders | Cross-layer evidence can help operators identify validator or Megapool conditions requiring review before they become operational problems. |
| Potential NOs | Clearer validator and Megapool state reporting can reduce the difficulty of understanding operational conditions when running a Rocket Pool node. |
| NOs | Operators receive one structured report combining execution-layer and Beacon Chain evidence instead of manually comparing separate systems. |
| Community | The project provides transparent, replayable evidence and clearly separates healthy, actionable, and inconclusive results. |
| RPL holders | Improved node-operator tooling supports the reliability and continued operation of the Rocket Pool protocol. |
Which other non-RPL protocols, DAOs, projects, or individuals would benefit?
The primary beneficiary is Rocket Pool.
The underlying evidence format may also be useful to Ethereum Beacon Chain tooling, node-operator dashboards, and other open-source validator monitoring projects. No external integration is being claimed as part of this grant.
Work
Who is doing the work?
Charles Emmanuel — Project Lead and Integration Architecture
Open-source blockchain infrastructure developer focused on protocol tooling, JSON-RPC integration, smart-contract data analysis, and technical documentation. Leads ILE Labs’ cross-ecosystem grant and engineering program.
GitHub: CodexEmmzy
Gideon Bature — Core Implementation
Software engineer and DevOps specialist with proficiency in Rust, Go, Solidity, JavaScript, and Python. Experience in systems engineering, EVM smart-contract tooling, and production infrastructure. Primary engineer on the existing MVP demonstrating live EVM contract calls, current Megapool ABI decoding, Beacon REST integration, and deterministic replay.
GitHub: GideonBature
Onyekachukwu Nweke — Protocol Layer and Verification
Blockchain engineer with deep experience in Rust systems programming, cryptographic protocol implementation, and adversarial verification. Led the lightning-payjoin-kit protocol implementation including rigorous empirical testing and public documentation of a negative verification result — demonstrating the team’s commitment to conservative, evidence-first engineering over optimistic claims.
GitHub: Onyekachukwu-Nweke
What is the background of the person doing the work?
The work is being carried out by an open-source developer focused on blockchain infrastructure, protocol tooling, Rust and JavaScript development, JSON-RPC integration, smart-contract data analysis, Beacon Chain data, test harnesses, and technical documentation.
The existing MVP demonstrates:
- live EVM contract calls;
- current Megapool ABI decoding;
- Beacon REST integration;
- validator pubkey correlation;
- withdrawal-credential verification;
- deterministic replay;
- mock-RPC integration tests;
- structured JSON and terminal output;
- conservative handling of incomplete evidence.
What is the breakdown of the proposed work?
Milestone 1 — Evidence and reconciliation
Weeks 1–3
- Add another live validator lifecycle scenario.
- Improve execution-layer and Beacon Chain evidence capture.
- Add batch validator reconciliation.
- Finalize healthy, actionable, and inconclusive classifications.
- Add tests and replayable evidence.
Milestone 2 — Public release
Weeks 4–6
- Complete the CLI workflow.
- Add clean-install CI verification.
- Publish documentation and the evidence schema.
- Package replayable reports and fixtures.
- Publish the release and maintenance guidance.
How is the work being tested?
Testing is included throughout the schedule.
The project will use:
- automated unit and integration tests;
- mock execution-layer and Beacon endpoints;
- live testnet captures;
- deterministic offline replay;
- malformed and incomplete-data fixtures;
- CI checks;
- manual review of generated evidence reports.
The tool will not classify missing or conflicting information as healthy. Such cases will be reported as inconclusive unless the available evidence supports a stronger conclusion.
How will the work be maintained after delivery?
The repository will remain public and open source.
Maintenance will include:
- keeping the supported ABI and network configuration documented;
- accepting issue reports and pull requests;
- updating fixtures when protocol interfaces change;
- preserving replayable evidence for regressions;
- clearly marking unsupported protocol versions or incomplete data.
Costs
What is the acceptance criteria?
The grant will be complete when:
- The public repository contains the finished read-only auditor.
- The tool supports at least two live Megapool/Beacon scenarios.
- Reports include network, block, validator, contract, Beacon state, evidence source, and limitations.
- Healthy, actionable, and inconclusive states are clearly separated.
- Evidence can be replayed offline without network access.
- Batch reconciliation is implemented.
- Automated tests and CI pass.
- Documentation explains installation, usage, evidence format, and limitations.
- No private-key handling, transaction signing, or transaction broadcasting is introduced.
What is the proposed payment schedule?
ILE Labs requests $6,500 USD, payable in the equivalent RPL amount at the time of payment if preferred by the GMC.
The proposed delivery period is six weeks:
- Milestone 1: $2,500 equivalent
- Milestone 2: $4,000 equivalent
Payments will be requested after acceptance of each milestone, not upfront.
Who will directly receive the payment?
Ethereum address: 0xaE6EAd7e192ea83D8c90DE85a7354063Daf6bAF0
The payment should be sent to the recipient address specified above.
How will the GMC verify delivery?
Each milestone will produce public repository evidence, including:
- code commits;
- test results;
- redacted live reports;
- replay commands;
- updated documentation;
- CI results;
- release notes.
What alternatives or options have been considered to save costs?
The project deliberately avoids:
- a hosted dashboard;
- transaction execution;
- private-key management;
- protocol changes;
- duplicating the entire Smartnode stack;
- operating paid infrastructure.
Have you already been compensated by the Rocket Pool protocol?
No. ILE Labs has not received Rocket Pool compensation for this work.
Conflict of Interest
Does the person or persons proposing the grant have any conflicts of interest?
No conflict of interest exists between ILE Labs and the Rocket Pool Grants and Bounties Management Committee.
Will the recipient or another project benefit financially if the grant succeeds?
The recipient will receive the grant payment for completing the open-source work.
The main benefit is the development of reusable open-source infrastructure for Rocket Pool operators and the wider community.