Author(s): Enti (@entigd on telegram)
To: RocketPool Grants Management Committee & EthStaker
Purpose
With this proposal we hope to reach an agreement for node operators in the Community Staking Module at Lido to have access to the RescueNode service.
Why
Ethereum benefits from a strong and viable set of operators, and after the launch of the Community Staking Module we’ve seen a steady growth of independent operators in the protocol, many of which have asked for a RescueNode-like service to offset possible downtime while doing maintenance to their servers, or during unforeseen events, etc.
Given RescueNode is already working and there’s less work involved to integrate a new protocol vs setting up brand new infrastructure, and provided that LEGO is wiling to fund the grant necessary for the proposed integration of CSM to RescueNode (and potentially any work needed by RescueNode maintainers to review and integrate the PR), I believe that integrating CSM to the service is a net-positive.
How
- Cost Sharing Options
- 50/50 Split: LEGO and RocketPool each pay half of the total monthly cost.
- Match Contribution: LEGO matches RocketPool’s contribution to the service. Given RP’s GMC covers the costs, our contribution would be a small support to the maintainer’s work.
- Prorata: We look at usage metrics per service every month or quarter, and split the bill accordingly. Note that we’re happy to split solo stakers 50/50.
- Quotas and technical integration
- Assuming an even split of the costs of the service, I would expect CSM operators to have the same terms as RocketPool’s: up to 4 sessions per year, 15 days each.
- A Pull Request will be pushed to the RescueNode repository upon reaching agreement.
- Branding
- Transparency is at our core, we would expect the website and any other relevant channel to communicate we’re helping cover costs. Other than that we do not expect RescueNode to change any of its current branding or messaging. We recognize this is a project incubated in the RocketPool community, and are very happy supporting it.
In failing to reach an agreement, Lido contributors consider deploying a fork respecting the AGPL license of the project.
Budget
It is my understanding that the service currently costs $508 every month, with ocasional extra expenses.
All costs associated with the community-led pull request for the integration, and ongoing service maintenance would be covered by the Lido Ecosystem Grants Organization (LEGO), as long as they stay within reason.
In failing to reach an agreement, Lido contributors consider deploying a fork respecting the AGPL license of the project.