Non-custodial Staking as a service
What is the nature of the proposed bounty?
Allnodes are great – it’d be better to have one or more competitors out there. In a worst-case scenario, the RP validators could act as part of a cabal or self-slash to grief. Limiting that set is useful. Note also that allnodes has quite a lot of stake, eg from Lido.
It need not be identical. For example, it could require running something very lightweight on a home computer, which could be run on a primary machine (as opposed to dedicated hardware).
Must 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?
Not necessary, but cool.
Benefits - enter N/A where appropriate
| Group | Benefits |
|---|---|
| Potential rETH holders | Lowers one potential tail risk. |
| rETH holders | Lowers one potential tail risk. |
| Potential NOs | Competition in this space can essentially only be good for NOs. Disparate features would let them choose based on preference, or perhaps they apply price pressure? |
| NOs | Competition in this space can essentially only be good for NOs. Disparate features would let them choose based on preference, or perhaps they apply price pressure? |
| Community | Having less centralization in this vector better fits the RP ethos IMO. |
| RPL holders | Given that part of our value is our brand, strengthening it in this way is likely to be beneficial to RP and RPL. |
What other non-RPL protocols, DAOs, projects, or individuals, would stand to benefit from the bounty being successfully completed?
The hypothetical project itself. And maybe other pools (eg, Stader), since the project could add support.
Will the results of the completed bounty be open source?
Need not be.
Work and Verification
What steps would be entailed in completing the bounty? Do successful examples of such work exist elsewhere?
Allnodes is the successful current example. I don’t think we should go by exact featureset so much as usage for rewarding.
How long is the proposed bounty available for? Is it awarded to the first team to successfully claim it, or is it in some way divided among all such successful claims in the proposed availability period?
This funds just one iteration, but I’m probably cool with funding more here. We don’t need 50, but 3-5 would be sick.
For each of the 2 milestones, I’d suggest one winner.
Who will test any products submitted for claiming the bounty?
No testing specified – the proof is in the pudding here based on usage.
What is the acceptance criteria for awarding of the bounty?
- Must be non-custodial (can have validator key shared, but not node wallet or withdrawal wallet)
- Graffiti must label the users of the service
Milestone 1: 10 users and 100 minipools
Milestone 2: 5% the size of allnodes (within RP) – measured by block proposals across a week
Payment
How much USD $ is the applicant requesting for successful completion of the bounty?
Milestone 1: $20k
Milestone 2: $60k
This is not at all meant to be enough. The service should charge and self-sustain. This is a bonus to make it a little more attractive, and a show that the RP community wants this.
Is the applicant requesting RPL or LUSD?
RPL? If bounty-doer wants LUSD and we have it, we should probably accommodate?
Conflict of Interest
Does the person or persons proposing the bounty 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 successful completion of the bounty).
I use Allnodes and like them. I help on their discord.
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?
Nothing significant.