# \[Grant\] Minipool to Megapool Break-Even Calculator: upkeep, validation and Saturn 2 updates **URL:** \ **Category:** Grants / Bounties\ **Created:** [15 October 2026 18:35 UTC](https://dao.rocketpool.net/t/grant-minipool-to-megapool-break-even-calculator-upkeep-validation-and-saturn-2-updates/4095 "2026-10-15T18:35:48Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![satyawansingh](https://dao.rocketpool.net/letter_avatar_proxy/v4/letter/s/8e8cbc/32.png) [@satyawansingh](https://dao.rocketpool.net/u/satyawansingh)\ **Post date:** [15 October 2026 18:35 UTC](https://dao.rocketpool.net/t/grant-minipool-to-megapool-break-even-calculator-upkeep-validation-and-saturn-2-updates/4095/1 "2026-10-15T18:35:48Z")
## Name of Grant Minipool to Megapool Break-Even Calculator: upkeep, validation and Saturn 2 updates ### What is the work being proposed? A read-only web calculator for legacy minipool operators already exists and is live. It reads a node’s active minipools and the live deposit queue from the contracts, and shows whether moving to 4 ETH megapool validators pays off and how long it takes to break even. Code: [GitHub - ss1738/rp-migrate-sim: Read-only break-even calculator for moving a Rocket Pool legacy minipool to 4 ETH megapool validators · GitHub](https://github.com/ss1738/rp-migrate-sim) Discussion: [Minipool to megapool break-even calculator, and what the queue looks like right now](https://dao.rocketpool.net/t/minipool-to-megapool-break-even-calculator-and-what-the-queue-looks-like-right-now/4093) I am not asking for payment for what is already built. I am asking for the time to finish what is missing and keep it correct: 1. Check how many express tickets a node still holds, so the queue wait reflects the node’s real position. 2. Model legacy RPL rewards from chain data, instead of asking the operator to type a number. 3. Compare the model with real reward data for a sample of nodes, and publish the size of the error. 4. Fix whatever node operators report in the forum thread. 5. Update the formulas when RPIP-71, 79, 80 or 83 become final, and maintain the page and repository for 12 months. ### Is there any related work this builds off of? The RPL fee switch calculator on the Rocket Pool website models steady-state megapool RPL income. RocketDash shows queue totals. I did not find a tool that takes one node’s legacy minipools and compares staying with moving, including the queue wait. I could not load the calculator page myself, so this is the limit of what I checked. The formulas follow RPIP-42, 46, 59, 62 and 75. The specification in the repository lists the source of each number. ### Will the results of this project be entirely open source (MIT, GPL, Apache, CC BY license or similar)? If not, which parts will not be, why, and under what license will they be published? Yes. Everything is MIT licensed in the public repository, including the specification, tests and scripts. The page is static, so anyone can host a copy. ## Benefit | Group | Benefits | | --- | --- | | Potential rETH holders | A public record of how fast the deposit queue is moving, and what that means for operators who plan to migrate. | | rETH holders | Operators can plan the move with real numbers, and avoid leaving ETH idle through guesswork. | | Potential NOs | Shows what the queue and the bond curve mean in practice for a given bond size. | | NOs | One node’s answer to “should I move, and when”, with every assumption shown and changeable. | | Community | An independent view of the queue speed, with the method published and open to correction. | | RPL holders | Better information for operators may reduce avoidable churn. I make no larger claim than that. | ### Which other non-RPL protocols, DAOs, projects, or individuals, would stand to benefit from this grant? None directly. The queue measurement script could be reused by anyone who studies the deposit queue. ## Work ### Who is doing the work? Satyawan Singh (forum handle satyawansingh, GitHub account ss1738), working independently. ### What is the background of the person(s) doing the work? What experience do they have with such projects in the past? I am an independent developer based in the UK. My public GitHub account (ss1738) holds Ethereum related work: epbs-formal, a TLA+ model of the ePBS fork choice specification (its README records where an earlier version of the model was wrong), clean-poseidon2, Lean 4 work on the Poseidon2 hash, and protocol-guard-ci, a check for Solidity and Foundry pull requests. For this tool I wrote the formula module, the on-chain readers and the page. I checked every contract function name against the interface files in the Rocket Pool contracts repository, and the queue method follows the \_assignMegapools function in RocketDepositPool. ### What is the breakdown of the proposed work, in terms of milestones and/or deadlines? Award expected around 2026-11-29. Dates are counted from the award. - Milestone 1, about 4 weeks, $1,000. Express ticket check. Legacy RPL rewards from chain data. A published error table against real reward data for at least 20 nodes. Fixes from forum feedback. - Milestone 2, by 2027-02-28, $1,500. Formulas updated for any of RPIP-71, 79, 80 or 83 that have been finalised by then. The 12 month maintenance period starts. If none has been finalised, this payment covers the maintenance and a documented update path. ### How is the work being tested? Is testing included in the schedule? The repository has 19 tests that check the formulas against values taken from the RPIPs. Milestone 1 adds a comparison with real reward data, and the errors are published whatever they turn out to be. ### How will the work be maintained after delivery? For 12 months: fixes within 7 days of a reported error, and updates within 14 days after a parameter change takes effect on mainnet. Hosting is static, so there is no server to keep running. The code is MIT licensed, so anyone can fork it. ## Costs ### What is the acceptance criteria? - Milestone 1: the express ticket check and legacy RPL modelling are live, and the error table is published in the repository. - Milestone 2: a tagged release that matches the finalised RPIP parameters, or a written note explaining why none has changed. ### What is the proposed payment schedule for the grant? How much USD $ and over what period of time is the applicant requesting? $2,500 in total: $1,000 on Milestone 1 and $1,500 on Milestone 2, over about 3 months from the award, plus 12 months of maintenance. I can be paid in RPL at the price on the day of payment if the GMC prefers. ### Who will directly receive the payment? (Required: the GMC can only send grants directly to a recipient address and cannot accept invoices.) 0xAda6BB4C99bc5A20479bbb790bfb84Edd7C41e20 ### How will the GMC verify that the work delivered matches the proposed cadence? Public commits and tags from the start, and a reply in this thread at each milestone with the release tag and the evidence. ### What alternatives or options have been considered in order to save costs for the proposed project? The tool runs as static files on public RPC endpoints, so there are no servers and no paid services. I kept the request small by not asking for payment for the existing build. ### Have you already been compensated by the RP protocol in any way for this work? No. ## Conflict of Interest ### Does the person or persons proposing the grant have any conflicts of interest to disclose? (Please disclose here if you are a member of the GMC or if any member of the GMC would benefit directly financially from the grant). I am not a member of the GMC, and I have no financial relationship with any GMC member. ### Will the recipient of the grant, or any protocol or project in which the recipient has a vested interest (other than Rocket Pool), benefit financially if the grant is successful? No other protocol or project in which I have an interest receives payment, tokens or revenue from this grant.