# Round 42 - GMC Call for Bounty Applications - Deadline is November 7 **URL:** \ **Category:** Grants / Bounties\ **Tags:** gmc\_bounty\_apps, gmc\_round\_42\ **Created:** [8 October 2026 00:13 UTC](https://dao.rocketpool.net/t/round-42-gmc-call-for-bounty-applications-deadline-is-november-7/4071 "2026-10-08T00:13:33Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ShfRyn](https://dao.rocketpool.net/user_avatar/dao.rocketpool.net/shfryn/32/531_2.png) [@ShfRyn](https://dao.rocketpool.net/u/ShfRyn)\ **Post date:** [8 October 2026 00:13 UTC](https://dao.rocketpool.net/t/round-42-gmc-call-for-bounty-applications-deadline-is-november-7/4071/1 "2026-10-08T00:13:33Z")
This thread is for applications for Rocket Pool’s October 7, 2026 - November 7, 2026 bounties. Please only post bounty applications in this thread. If you would like to discuss and/or ask questions about any applications you see in this thread, we ask that you do so in this [forum thread](https://dao.rocketpool.net/t/round-42-gmc-community-discussion-of-submitted-applications/4069) which has been established for all community discussions related to this round of applications. Only those bounty applications that are posted in this thread and timestamped by November 7, 2026 at 23:59 (11:59 PM) UTC will be considered. Any bounties posted after that deadline will be carried over to the next award period. This is the expected schedule for round 42: - Application Period (October 7 - November 7) - Scoring Deadline (November 24) - Final Voting Amendments, Discussion and Finalization (November 25 - November 28) - Award Announcement (November 29) > **Differences Between Grants and Bounties** > > Grants are intended to be applied for by those who are wishing to carry out the work themselves. Bounties are open-ended goals that could be met by anyone, including those other than the proposing party. In other words, if I believed that Rocket Pool needed a fifty-foot paper mache orange rocket for publicity purposes and I wanted to be the one to build it, I would apply for a grant. If I instead thought Rocket Pool needed a fifty-foot paper mache orange rocket for publicity purposes but I wanted it to be open to whoever built it first to claim the reward (similar to a prize), then I’d apply for a bounty. To guide you in your application, the GMC has established the following goals and the following scoring rubric: > **GMC Goals** > > Grants, bounties, and retrospective awards should make it easier and/or more attractive to do one or more of the following: > > - become a node operator > > - operate a node, mint rETH > > - hold or use rETH > > - improve the quality of life for the protocol and its community. > **Bounties Rubric** > > When evaluating grant applications, the GMC takes into account the following goals: > > - If the bounty is completed successfully, to what extent does it further the GMC goals? > > - To what extent is it likely that the bounty can be feasibly claimed/completed successfully? > > - If the bounty is successfully completed, how large is the benefit to the protocol relative to the size of the proposed costs? # Bounty Proposal Template ## Guidelines - The goals of the Bounty Proposal are: - to communicate your bounty idea clearly, in general terms, such that the GMC can decide if it’s worth pursuing. - to estimate the benefits and costs attached to your proposal. - to disclose any relevant conflicts of interest. - Answers to the template questions do not need to be highly detailed. Estimates or ranges are acceptable. Brief answers are also fine. ## Template ```markdown # Bounty Name ## General Information ### What is the nature of the proposed bounty? ### Why are you writing this bounty proposal? ## Benefit | Group | Benefits | |---|---| | Potential rETH holders | If the bounty is successfully completed, how does this help people looking to stake ETH for rETH? | | rETH holders | If the bounty is successfully completed, how does this help rETH holders? | | Potential NOs | If the bounty is successfully completed, how does this help people looking to run a Rocket Pool node for the first time? | | NOs | If the bounty is successfully completed, how does this help people already running a Rocket Pool node? | | Community | If the bounty is successfully completed, how does this help the Rocket Pool community? | | RPL holders | If the bounty is successfully completed, how does this help RPL holders? | ### Which other non-RPL protocols, DAOs, projects, or individuals would stand to benefit from the bounty being successfully completed? ## 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? ### What advice would you give a bounty hunter working on this bounty? ### Should the output of this bounty be available under an open source license? ## Costs ### How much do you think the completion of this bounty is worth to Rocket Pool (in USD)? ### How much work will be needed to verify this bounty has been completed? What skillsets or knowledge will be required? ## Structure ### How would you structure this bounty, and why? * A single payout to a single team on completion? * Divided into milestones? * Multiple payouts to multiple teams? * Should this be written up as multiple bounty definitions? * Something else? ### Is this bounty repeatable? ### Are there any reasonable circumstances under which this bounty should be withdrawn? Should it expire? ## 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). ### 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? ``` # Bounty Definition Template ## Guidelines - When a single bounty proposal has parts that must be completed by different groups, it should become multiple definitions. - Where reasonably possible, bounty definitions should limit the number of distinct skillsets required for completion of the bounty. - Bounties should be defined in terms of the smallest worthwhile unit of work. IE: $25 to add/update a single relevant FAQ question rather than $5,000 to update the FAQ. - Include any information or resources that might reasonably help a bounty hunter complete the bounty. - Think carefully about which tasks are required, and which can be optional. - Clearly list any dependencies, if the bounty cannot be completed in all circumstances. - Only include multiple milestones for large bounties with natural points of division. ## Template ```markdown # Bounty Name ## Data * Repeatable? * Expiring? * Skillsets for completion? (See existing bounties and reuse where possible, new skillsets are recommended if sufficiently distinct) * Relevant tags? (See existing bounties and reuse where possible, new tags are recommended if sufficiently distinct) * Min reward (USD)? * Max reward (USD)? * Any linked definitions? (e.g. if a single bounty proposal becomes multiple definitions.) * Any dependencies? ## Summary Short 1-3 sentences describing the bounty. ## Dependencies Is there anything that must happen (outside of a bounty hunter's control) before it is possible to complete this bounty? This may be other bounties that must be completed first, an upcoming event or change, or a regular occurrence that triggers a valid bounty. This section is optional. It may later be removed from the definition if the dependency becomes permanently met. ## Required Milestones What must be completed for a bounty hunter to claim some amount of bounty. Described per milestone. ### Milestone A - **Payout:** Clear bulleted list or subheadings covering the items that must be completed and/or adhered to for this milestone to be valid. ### Milestone B - **Payout:** Clear bulleted list or subheadings covering the items that must be completed and/or adhered to for this milestone to be valid. ### Milestone C - ## Optional Milestones What tasks may be completed for a bounty hunter to earn extra bounty rewards. Described per milestone. This section is optional. Optional milestones may be less strictly defined than required milestones. You may aggregate multiple minor considerations that would contribute to a payout. ### Milestone D - **Maximum Payout:** Clear bulleted list of the items that would contribute to payout for this milestone. ### Milestone E - ## Further Notes Anything you think would be beneficial for a bounty hunter to know when working on this bounty. May be divided into subsections as needed. ## Resources Links to repositories, web pages, forum discussions, etc. Anything that the bounty hunter may be able to use to do a better job on the bounty work. ## Contacts Individuals that have agreed to act as contacts for this bounty. Include usernames + contact details for any platform on which the contact is willing to respond to requests. Any contacts are expected to fully understand the bounty definition. This section is optional. Contacts: * MAY be eligible for incentives. * SHOULD NOT assist the bounty hunter directly with the bounty work. * SHOULD assist bounty hunters via feedback, direction, and oversight upon request. ## Verification Who is expected to verify that the work delivered meets the relevant milestones? This person or group must have agreed to do this in advance of this definition being published. This person or group should have any relevant skillsets needed to properly verify the bounty work. ``` ### Join the Conversation We encourage prospective applicants to introduce themselves and discuss their ideas in the [Rocket Pool Discord](https://discord.gg/rocketpool), particularly in the GMC public discussion channel, before submitting an application. Engaging with the community is a great way to receive feedback, understand the protocol’s current priorities, and determine whether your proposal aligns with the GMC’s funding goals. While not required, we welcome the opportunity to connect with applicants and discuss ideas before the formal review process. ---
**Author:** ![RocketPoolAfrica](https://dao.rocketpool.net/user_avatar/dao.rocketpool.net/rocketpoolafrica/32/1717_2.png) [@RocketPoolAfrica](https://dao.rocketpool.net/u/RocketPoolAfrica)\ **Post date:** [8 October 2026 15:51 UTC](https://dao.rocketpool.net/t/round-42-gmc-call-for-bounty-applications-deadline-is-november-7/4071/2 "2026-10-08T15:51:50Z")
# Rocket Pool rETH Education & Onboarding Content ## Data - **Repeatable?** No, not for substantially identical content. May be repeated for significant protocol changes, substantially different audiences, or localization. - **Expiring?** Yes. Expires at the end of the applicable bounty period unless renewed by the GMC. - **Skillsets for completion?** - **Relevant tags?** - **Min reward (USD)?** $750 - **Max reward (USD)?** $2,000 - **Any linked definitions?** None. - **Any dependencies?** Access to current Rocket Pool documentation and a functioning rETH onboarding path. ## Summary Create a high-quality, evergreen educational package that helps beginners understand Rocket Pool and rETH and provides practical guidance for acquiring and using rETH. The submission should include a comprehensive written guide and a practical video or equivalent visual walkthrough, supported by current Rocket Pool documentation, clear risk disclosures, and useful onboarding resources. ## Completion Requirements To qualify for the bounty, the submission should: 1. Explain Rocket Pool and rETH in beginner-friendly language. 2. Explain the basic relationship between ETH, staking, Rocket Pool, and rETH. 3. Explain key benefits and risks of holding rETH. 4. Provide practical instructions for acquiring rETH through a supported method. 5. Explain relevant ways rETH can be used after acquisition. 6. Clearly identify third-party DeFi applications where applicable. 7. Include links to relevant official Rocket Pool resources. 8. Include appropriate risk disclosures. 9. Provide at least one polished written educational resource. 10. Provide a practical video walkthrough or equivalent visual tutorial. 11. Make all final materials publicly accessible. 12. Ensure all technical information is accurate at the time of submission. ## Quality Standards The bounty should prioritize: - Accuracy - Clarity - Beginner accessibility - Practical usefulness - Evergreen value - Professional presentation - Responsible communication of risks The submission should not rely on: - Price predictions - Guaranteed returns - Misleading financial claims - Unverified protocol claims - Excessive promotional language ## Verification Rocket Pool community/GMC reviewers should verify that the submission satisfies the stated completion requirements and that its technical information is materially accurate. The reviewer should be able to reproduce the relevant onboarding steps or verify them against current official Rocket Pool documentation. Minor formatting or stylistic differences should not disqualify an otherwise complete and accurate submission. ## Reward **Minimum:** $750 USD **Maximum:** $2,000 USD The final reward should be determined according to the completeness, quality, accuracy, production value, and practical usefulness of the submission. A basic but complete submission may receive a lower reward, while an exceptionally polished and comprehensive package may qualify for the maximum reward. ## Dependencies The bounty depends on the availability of current Rocket Pool documentation and a functioning method for users to acquire and interact with rETH. If significant protocol or interface changes occur during the bounty period, the bounty hunter should update the relevant instructions before final submission. If the required user flow becomes unavailable or materially changes, the GMC may modify, pause, or withdraw the bounty. # Rocket Pool rETH Education & Onboarding Content Bounty ## General Information ### What is the nature of the proposed bounty? This bounty would reward the creation of a high-quality, evergreen educational content package that makes Rocket Pool and rETH easier for new users to understand, acquire, hold, and use. The goal is to create practical educational resources that take a user from: **“What is Rocket Pool/rETH?” → “Why would I use it?” → “How do I get rETH?” → “How can I use it?”** The completed work should be accessible to users with limited prior knowledge of Ethereum staking and should prioritize clarity, accuracy, and practical onboarding over promotional messaging. A successful submission could consist of a structured educational guide accompanied by a practical video walkthrough and supporting visual assets. ### Why are you writing this bounty proposal? Rocket Pool has a technically strong product, but new users can face a significant information gap between hearing about rETH and actually understanding how and why to use it. Educational content can reduce this friction by explaining Rocket Pool and rETH in plain language and providing practical, step-by-step guidance. The bounty would create reusable resources that Rocket Pool, its community, educators, and other ecosystem participants can reference when introducing new users to rETH. ## Benefit | Group | Benefits | | --- | --- | | Potential rETH holders | Provides a clear explanation of rETH, Rocket Pool staking, benefits, risks, and practical steps for acquiring and using rETH. | | rETH holders | Makes it easier to understand additional ways to use rETH, including relevant DeFi use cases, while clearly communicating associated risks. | | Potential NOs | Introduces Rocket Pool’s permissionless node-operator model and provides an entry point for users who may later become node operators. | | NOs | Increased awareness of Rocket Pool can contribute to a larger ecosystem of users, stakers, and potential future node operators. | | Community | Creates evergreen educational material that community members can use when answering questions and onboarding newcomers. | | RPL holders | Greater awareness and adoption of Rocket Pool can strengthen overall protocol activity and the ecosystem surrounding Rocket Pool. | ### Which other non-RPL protocols, DAOs, projects, or individuals would stand to benefit from the bounty being successfully completed? Ethereum and projects that support rETH integrations could benefit from increased awareness and usage. DeFi protocols that integrate rETH may also benefit if the educational material introduces users to legitimate rETH use cases. Ethereum educators, community organizers, wallets, DeFi applications, and other ecosystem participants could also reuse or reference the resulting educational resources. The bounty should not require endorsement of any particular third-party protocol. ## 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? A bounty hunter would be expected to: 1. Research Rocket Pool’s current documentation and official resources. 2. Develop a beginner-friendly explanation of Rocket Pool and rETH. 3. Explain how rETH represents staked ETH and how the Rocket Pool protocol works at a high level. 4. Explain the principal benefits and risks associated with holding rETH. 5. Create a practical walkthrough showing how a new user can acquire rETH using a supported method. 6. Explain at least several relevant ways rETH can be used after acquisition. 7. Clearly distinguish established functionality from optional or third-party DeFi use cases. 8. Include appropriate risk disclosures and links to official documentation. 9. Produce a polished written guide and/or video walkthrough. 10. Make the final resources publicly accessible and easy to share. Successful examples of this type of educational work exist across Ethereum and DeFi, including protocol documentation, onboarding guides, explainer videos, tutorials, and community-created educational resources. The required skillsets include: - Ethereum and liquid staking knowledge - Understanding of Rocket Pool and rETH - Technical research - Educational writing - Video/content production where applicable - Basic wallet and DeFi usability knowledge - Ability to explain technical concepts accurately to beginners ### What advice would you give a bounty hunter working on this bounty? The priority should be **accuracy and usability rather than marketing**. The bounty hunter should use current Rocket Pool documentation as the primary source of technical information and verify any claims that could change over time. The content should assume that the reader may know very little about liquid staking. Avoid unnecessary jargon, exaggerated claims, price predictions, or language implying that rETH is risk-free. A strong submission should allow a beginner to understand the product and independently follow the onboarding process. Where third-party protocols are mentioned, they should be clearly identified as third-party applications rather than being presented as Rocket Pool products. ### Should the output of this bounty be available under an open source license? Yes. The written educational material, instructional assets, and other original materials produced for the bounty should preferably be released under a permissive license that allows Rocket Pool and its community to reuse, translate, update, and distribute the material. Video and visual assets should similarly be provided in reusable formats where reasonably possible. ## Costs ### How much do you think the completion of this bounty is worth to Rocket Pool (in USD)? I propose a maximum reward of **$2,000 USD** for a complete, high-quality submission. A lower reward could be appropriate for a smaller but still useful submission. Suggested reward range: **Minimum: $750 USD** **Maximum: $2,000 USD** The final reward should reflect the quality, completeness, accuracy, production value, and practical usefulness of the submitted work. ### How much work will be needed to verify this bounty has been completed? What skillsets or knowledge will be required? Verification should be relatively straightforward. A reviewer should confirm that: - The required educational topics are covered. - The information is technically accurate. - The onboarding instructions work at the time of submission. - Appropriate official Rocket Pool resources are referenced. - Risks and limitations are communicated responsibly. - The content is publicly accessible. - The materials meet the minimum quality requirements. - No material claims are misleading or unsupported. Verification would require familiarity with Rocket Pool, rETH, Ethereum staking, and the relevant current user flows. ## Structure ### How would you structure this bounty, and why? I recommend **a single bounty with one payout upon completion**. The bounty should define a minimum acceptable deliverable while allowing bounty hunters flexibility in how they present the material. A qualifying submission should include: - One comprehensive beginner-friendly written guide. - One practical video walkthrough or equivalent visual tutorial. - Relevant screenshots, diagrams, or other supporting educational material. - Links to current official Rocket Pool documentation. - Clear risk disclosures. - Publicly accessible final materials. A single bounty keeps the task focused while allowing different creators, educators, developers, or teams to compete to produce the strongest implementation. If the GMC believes the scope is too broad, the work could instead be separated into smaller definitions for written education and video education. ### Is this bounty repeatable? Yes, with limitations. The same bounty should not be repeatedly paid for substantially identical content. However, future versions could reasonably be created when there are significant Rocket Pool product changes, major changes to the rETH user experience, or a clearly different target audience or language. A future bounty could also focus specifically on localization into a new language or region. ### Are there any reasonable circumstances under which this bounty should be withdrawn? Should it expire? The bounty should expire at the end of the applicable bounty period unless renewed or replaced by the GMC. It should also be withdrawn or revised if: - Rocket Pool’s user experience changes substantially before completion. - The proposed deliverables become obsolete. - A separate initiative already satisfies the objective. - Technical changes make the original requirements inaccurate. - The bounty receives submissions that reveal the scope or requirements need significant modification. ## Conflicts of Interest ### Does the person or persons proposing the bounty have any conflicts of interest to disclose? The proposer is not a member of the Rocket Pool GMC and does not have a direct financial interest in the GMC’s decision to fund this bounty. Any GMC member with a direct financial interest in a successful submission should disclose that conflict and follow the relevant governance procedures. ### 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? The proposer does not require the bounty to be completed by themselves and is not requesting payment for personally completing the work. The bounty is intentionally open-ended so that any qualified bounty hunter can submit the required work and claim the reward. If the proposer or an affiliated project later submits work for the bounty, that relationship should be disclosed at the time of submission.