DAO Engagement Documentation
General Information
What is the nature of the proposed bounty?
The idea for this bounty is to expand the existing Rocket Pool official documentation with easy-to-consume explainers of the current Rocket Pool DAO structures, and how to engage with them positively and effectively. This section should be targeted at individuals new to the Rocket Pool DAO, whether node operator or otherwise. The author should assume familiarity with crypto communities generally. This should include pages like:
- A page describing the pDAO and the oDAO, their responsibilities, and differences.
- A page listing some of the key RPIPs that govern the Rocket Pool DAOs, likely candidates listed below. The page should include two brief paragraphs for each, the first describing what it does/defines / etc. And the second describes why this is important/useful/significant for Rocket Pool.
- RPIP-1: RPIP Purpose and Guidelines
- RPIP-4: Community Resolutions and Voting
- RPIP-10: pDAO Budget Allocation / Committees
- RPIP-17: Self-limiting Rocket Pool
- RPIP-23: pDAO Charter
- RPIP-24: oDAO Charter
- RPIP-30: RPL Staking Rework (optional)
- RPIP-33: Implementation of an On-Chain pDAO
- RPIP-36: Committee Membership Record (optional)
- RPIP-37: Protocol Development
- If other significant RPIPs are ratified or accepted by the RPIP editors, they should also be included.
- A page describing the GMC, their role in the Rocket Pool DAO, and links to find more information.
- A page describing the IMC, their role in the Rocket Pool DAO, and links to find more information.
- A page summarizing the best ways to engage with the community and the DAOs productively, should include summaries and links to the following pages:
- A page on Discord, the trading channel, and the support channel, any other relevant channels. Care should be taken to highlight the presence and importance of threads, with some prominent examples.
- A page on voting targeted at Node Operators. How to vote, how to delegate, why it’s important to vote, how often should they check-in, etc.
- A page on DAO engagement via feedback, highlighting how and where to find proposals that are looking for feedback, how, where, and when to find grants, bounty, and retro proposals looking for feedback.
- A page on DAO contribution via work, volunteer committee positions, bounty board, how grants and retros work, etc.
- A page listing the crucial resources that exist and are used frequently by the community, complete with a short paragraph description of what they are and why they are useful.
There may be other pages that should also be present in such a section, bounty hunters should be free to adjust.
Why are you writing this bounty proposal?
This doesn’t exist and it should. The Rocket Pool community is fairly cohesive, and also fairly inscrutable to outsiders. As with all crypto communities, it has its own inside jokes, terminology, conventions, etc. It’s very hard to get up to speed with what’s going on if you’re completely new. There is no ‘friendly’ introduction to the DAO / community (as opposed to the protocol) that I’m aware of.
Benefit
| Group | Benefits |
|---|---|
| Potential rETH holders | Potential rETH holders would be better able to find information about how Rocket Pool works as a DAO and a community, which could positively impact their willingness to choose rETH. |
| rETH holders | Existing rETH holders are unlikely to benefit. |
| Potential NOs | Potential NOs would be better able to integrate with the DAO and community. They would better understand what sort of DAO contributions were useful, and how to put those into action if desired. |
| NOs | NOs that are less engaged in the community would better be able to learn what sort of DAO contributions were useful, and how to put those into action if desired. |
| Community | It can help convert potential community members into community members, benefiting everyone as the pool of talent and perspectives increases. |
| RPL holders | RPL holders are unlikely to benefit directly. |
Which other non-RPL protocols, DAOs, projects, or individuals would stand to benefit from the bounty being successfully completed?
Professional service organizations in the crypto space may find it easier to engage with Rocket Pool, but this is a fairly obscure benefit.
Work
What steps would be entailed in completing the bounty? Do successful examples of such work exist elsewhere? What skillsets or knowledge will be required?
Steps
- Produce or gather documentation content (some may already exist outside of the official documentation.)
- Run the official documentation site locally, test, and integrate changes.
- Have new content reviewed by the community and core team.
- Content is merged and author + reviewers are paid.
I spent a fair bit of time producing this sort of documentation at Maker. Can find some examples here: https://github.com/LongForWisdom/governance-manual, though the pages don’t map one-to-one. Looking at older versions of that repository may be more useful.
In terms of skillset bounty hunters need general writing ability, a good sense of priority, how to present information, and fairly deep knowledge of the Rocket Pool community and structures.
What advice would you give a bounty hunter working on this bounty?
Focus on making this useful. Try to put yourself in the shoes of someone who knows very little about the protocol or its DAO. Find a few people who know nothing about the protocol and DAO, and get them to read, and see if it’s useful.
Should the output of this bounty be available under an open-source license?
Yes. No reason not to, it’s only relevant for RP, and will mean the community can mirror it on other documentation sites if they want.
Costs
How much do you think the completion of this bounty is worth to Rocket Pool (in USD)?
Maybe 6-8k for authoring, perhaps more. Doing this well is harder than it sounds, and documentation bounties have not seen significant uptake.
1-2k total for reviews.
2k for a maintenance plan that will actually result in this section of documentation being maintained. Could be a repeatable bounty, could be a stipend, could go to a committee, etc. Paid half now, half when the first instance of serious maintenance happens.
How much work will be needed to verify this bounty has been completed? What skillsets or knowledge will be required?
In terms of verification, anyone active in the Rocket Pool community for a decent amount of time should be able to confirm that this covers the important areas.
Someone relatively new to the protocol could be found and compensated to verify that the concepts are reasonably easy to grasp for a newcomer.
Structure
How would you structure this bounty, and why?
Milestones for the following:
- Baseline Authorship - Content listed above
- Additional Authorship - Up to three(?) pages of additional content that the verifiers agree is a strong value-add.
- Review - Contribute to reviews, split between reviewers, min payout of like $100
- Maintenance Plan - Provides a concrete maintenance plan. Either a written and accepted perpetual bounty for maintenance, a commitment from a committee to maintain it, or a grant for the author to maintain it in the future.
- Maintenance Success - The maintenance plan has an instance of succeeding. (should be fairly small, this shouldn’t be the incentive to maintain once and then ignore.)
Is this bounty repeatable?
No, not in and of itself.
Are there any reasonable circumstances under which this bounty should be withdrawn? Should it expire?
I don’t think so.
Conflicts 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).
Not a member of the GMC, GMC shouldn’t directly financially benefit from this bounty.
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?
Nope. I will write the definition if the GMC is interested in this proposal.