[GCP-002] - PASSED - RocketPool oDAO participation

[Gitcoin Community Proposal] - RocketPool oDAO participation


Gitcoin was recently invited to participate in Rocket Pool’s oDAO, to do so we need to stake 1750 RPL (which we have from an airdrop from the Rocket Pool community in our Matching Pool) and ensure we have a validator running to perform oDAO required tasks. If we are selected, we will earn rewards for participation which will go back to the Matching Pool. I am asking for permission to use 1750RPL to post a bond for our participation, set up a validator with 16Eth, and foster a relationship with Rocket Pool where we support the decentralization of Ethereum.


Rocket Pool is one of the leading staking protocol providers for individuals to stake at home. You can read more about Rocket Pool here. Essentially individual node operators can stake ETH to secure the beacon chain using Rocket Pools’ protocol and in doing so, they earn RPL rewards. So I, Kyle, would stake 16Eth to run a validator node and my Eth is paired with Eth from another community member who wants to stake their Eth, but doesnt want to run a node themself. Often the rewards are pooled to increase the total rewards of those staking.

Rocket Pool has an Oracle DAO (oDAO) that ensures those who are participating in the Rocket Pool network are good actors. This oracle membership in oDAO provides the Rocket Pool network assurances that the rewards paid out are fairly and accurately and essentially helps confirm the Rocket Pool protocol is running as it should. Gitcoin has been invited to run an Oracle node, and join oDAO. You can read more about oDAO in this post.

oDAO members are rewarded for participating, and offered a seat at the governance table with Rocket Pool. You can review past proposals and learn more about participation in oDAO here. A number of other great communities already participate in oDAO (Fire eyes, Eth Staker community, Nimbus, Etherscan, etc.)


As discussed in past posts, finding recurring and sustainable funding models for funding public goods is high on our priority list. At the same time, growing and continuing to be good stewards and partners to other protocols in the space has long been in our Ethos. I love the idea of supporting a fellow protocol as it continues to grow, and it is with our support we can also secure the Beacon chain. Partnering with Rocket Pool enables the DAO to accomplish a few key tasks:

  1. We can help secure both the Ethereum network by running a validator, and also help secure the Rocket Pool protocol via their oDAO participation.
  2. We can partner with a leading Ethereum Validator protocol, and earn rewards by doing so.
  3. Those rewards can be used to participate in governance in the Rocket Pool community, and if desired, fund public goods.

By participating in Rocket Pool’s oDAO we will play our part in a broader ecosystem while being rewarded for that action. This will further the good will of Gitcoin, and also broaden our participation in securing the Ethereum Network.


In order to participate a few things need to happen:

  1. We need to run a Rocket Pool validator Node
  2. We need to be formally invited by Rocket pool
  3. We need to post a bond of 1750 to confirm we will perform our validator duties adequately
  4. Once we are formally invited, and the bond is posted, we can begin our oDAO membership and services.

I Have been running a validator node since genesis at home, and have recently stood up a (brand new) Rocket Pool validator node on spare hardware for this task. Taking on the Oracle verification steps required by oDAO should be straightforward and easy to keep up with as the software mostly runs on its own.

I am requesting to use the 1750 RPL that was airdropped to the DAO and put it to work back in the community that entrusted us with those tokens to begin with.

The full documentation for how to set up a node can be found here, and the oDAO details are here.

Some of the key account details can be found here to ensure transparency on the token accrual.

I would also like to stake 16 Eth from the Matching pool to run a validator and earn rewards for the DAO. That earned Eth can be withdrawn at any time (after the Shanghai hard fork), and will continue to grow at a rate of around 7% annually.


This proposal enables us to support a growing protocol, earn rewards for doing so, and also gives us an opportunity to participate in governance with Rocket Pool’s oDAO.


This participation gives us a responsibility with another community, and it is important we take that to heart when committing. This means, we will need to ensure we have a node running and are able to perform our duties with the highest up time possible. One potential drawback is in the event our node is no longer operational (power outages, hardware outages, etc.) we may be asked to leave the oDAO and lose part if not all of our bond.

The current value of the RPL tokens and Eth being requested is worth just under $114K USD. These funds could be sold and used in other places. Though we don’t have a need for them today, I want to call out this is a drawback in the immediate term.


For this vote, I am proposing three options:

1 - Yes to joining oDAO and posting the 1750 RPL bond, and also establish a validator on Rocket Pool with 16 Eth

2 - Yes to joining oDAO and posting the 1750 RPL bond, but do not create a validator node with 16 Eth

3 - Do not use the 1750 RPL and 16 Eth to take these actions

I am looking forward to hearing from the community on what they think :slightly_smiling_face:

Revision history

  • [placeholder]

I vote Yes with the first option of joining oDAO and posting 1750 RPL bond, and also establishing a validator on Rocket Pool with 16 ETH.


This is the kind of experimentation we need. Even with the risks, I’d like to see this move forward.


Thanks, Azeem. This is yet another GCP opportunity you have been cultivating! Huge thanks :pray:

1 Like

I’m supportive of this, and would go with option 1 as well.

Just for transparency, I spoke with Kyle about the process for unwinding this if we wanted to continue for whatever reason, and feel confident that this would be a painless process. I’d love to normalize documenting the failure case in our future GCPs so that we can consider the full scope of these proposals.


If we join the oDAO, what is the continued expectation? Is it relatively passive with minimal maintenance? Or does someone from GitcoinDAO have to actively involve themselves with the Rocketpool community?

Generally speaking yes. Though I am excited to be a good steward and participate in their governance as well. Rocketpool usually has a couple proposals a month for their oDAO members, and they are usually not very contentious.

I’m supportive for the reasons articulated here and, tbh, because of the enthusiasm expressed as well.

Living our values by helping to defend the commons seems right on every level.

Secondarily - if running these nodes becomes challenging then either we unwind (as @kevin.olsen mentions it wd be nice to see this unwind or exit option briefly articulated) or gitcoin can build a little more devops muscle to address, which seems like a capability we need for passport and otherwise.

I’d vote for option 1.


Give the five steward comments, I am going to move this to the proposal section for us to get more comments before posting to Snapshot.


Also supportive. Where is the new place to comment? I don’t think I see another location?

1 Like

I support the ODAO participation wholeheartedly due to its decentralized structure, relative ease of implementation, and potential for generating income.


This is the right place. I moved the conversation from #open-discussion to #governance-proposals

It feels like we should have quorum to get a vote live :raised_hands:


hi Annika, this is THE place :slight_smile:

1 Like

I agree with option 1. This seems like a good experiment and opportunity to participate across the ecosystem & earn rewards.

I’m in support of this proposal (Option 1) but I’d like to see this risk evaluated a bit more. How long does the node need to be offline in order to be kicked out of the oDAO? Can we quantify this risk and implement some mitigation strategies?

Great question! I think another oDAO member was down for over 60 days before a proposal went live to kick them out… Although outages happen, I highly doubt we would ever have an outage that long.


I support option 1, thanks a lot for your new and creative proposal, Kyle.

1 Like

Hey everyone - this is now live on Snapshot!


Would love for you to get out and vote!

1 Like

Awesome - I assumed it was a much lower threshold. I’m fully in support of option 1!

1 Like

I agree with option 1. This is a net positive for the overall industry as well as the DAO

1 Like