Bounty
Treegen Testing Support
What is the nature of the proposed bounty?
Creating an independent implementation of treegen, and supporting testing for each new tree spec.
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?
It’s highly encouraged, and supported by the payment split.
Benefits - enter N/A where appropriate
If the bounty is successfully completed, how does this help people looking to stake ETH for rETH?
Errors in disbursement would damage trust in the protocol.
If the bounty is successfully completed, how does this help rETH holders?
Errors in disbursement could cause rETh holders to lose rewards. Additionally, errors in disbursement would damage trust in the protocol.
If the bounty is successfully completed, how does this help people looking to run a Rocket Pool node for the first time?
Errors in disbursement would damage trust in the protocol.
If the bounty is successfully completed, how does this help people already running a Rocket Pool node?
Errors in disbursement could cause NOs to lose rewards. Additionally, errors in disbursement would damage trust in the protocol
If the bounty is successfully completed, how does this help the Rocket Pool community?
Errors in disbursement would damage trust in the protocol.
If the bounty is successfully completed, how does this help RPL holders?
Errors in disbursement would damage trust in the protocol.
What other non-RPL protocols, DAOs, projects, or individuals, would stand to benefit from the bounty being successfully completed?
None
Will the results of the completed bounty be open source?
Work and Verification
What steps would be entailed in completing the bounty? Do successful examples of such work exist elsewhere?
The claimant SHALL make an independent version of treegen following the new spec but NOT following the new code from the RP dev team.
The claimant SHALL work with the RP dev team to confirm matching and/or track down the root causes of differences seen.
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?
The reward should be split up amongst all valid claimants.
Who will test any products submitted for claiming the bounty?
The product is test work, there is no specific output.
What is the acceptance criteria for awarding of the bounty?
There are 2 criteria:
-
The spec is live
-
The RP dev team members working on this (likely @jcrtp) is asked who both created an independent implementation and actively supported testing
Payment
How much is the applicant requesting for successful completion of the bounty?
I’d propose $1500 per spec
For simplicity, rewards SHALL be evenly split amongst those that met the criteria, with open source treegen implementations being given twice the weight when splitting.
There was consideration to do this as a grant, but in the end I preferred the bounty approach as it allows more people to become involved, or someone else to take over entirely if current individuals opt not to continue. Being technical, this might be a series of bounties (one per tree spec). It may make sense to break it out that way and fund up to 5 for the cycle or something.
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).
No.
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?
No