| rpip | title | description | author | discussions-to | status | type | created | vote-to | vote-date | vote-result |
|---|---|---|---|---|---|---|---|---|---|---|
38 |
Modify or Decline Eigenlayer Integration (BA082401) |
Appeals GMC decision on BA082401 and seeks the opinion of the pDAO |
Patches (@jshufro) |
Final |
Meta |
2024-02-06 |
2024-03-19 |
Rejected |
This proposal looks to challenge the GMC decision on application BA082401, the funding of an integration with Eigenlayer.
The pDAO SHALL vote twice:
- SHALL the bounty be rejected?
- If not, SHALL the bounty be reduced to Milestone 0 (Research informing the implementation)
- If the first vote passes, the bounty SHALL be voided.
- If the first vote fails, the bounty SHALL be modified according to the result of the second vote:
- If the second vote passes, the bounty SHALL be modified to remove milestones A, B and C, and to change the overall funding to $10,000.
- If the second vote fails, the bounty SHALL be upheld as written.
Funding an integration with Eigenlayer has the potential to attract many node operators, but also the potential to create additional risks to rETH holders. Arguments both that Rocket Pool will suffer if it does and suffer if it does not integrate with Eigenlayer are prevalent in community channels. This decision is important and contentious enough to warrant involvement of the whole pDAO.
Copyright and related rights waived via CC0.