[Request for feedback] Proposed Future for the Grant Programs and GR16 as we Transition to the Protocol

đŸŒ± Gitcoin Grants
, , ,
2

Thank you, @J9leger for this thorough recap. The Gitcoin DAO team has spent an immense amount of time going deep and wide on this decision and considering all the nuances and complexities of the best next move. I have appreciated the strong leadership and commitment from across the team on this topic.

As a workstream lead of the Gitcoin Product Collective (GPC) and the former VP of Product at Gitcoin Holdings where the protocol was incepted, I’m very supportive of the organization sunsetting the centralized grants program and spending a short season focused on the transition to full decentralization. The protocols are now in closed beta and ready for active testing through production use. This means we are at the point of being ready to execute on any unique features for the Gitcoin Grants program and begin scaling up adoption.

While we have been collaborating cross-functionally over the last several months of design and implementation, all the other workstreams have had a main focus quarter over quarter on running the next centralized grants round. Having the full focus of the rest of the DAO (marketing, PGF ops, support, FDD) on the design and implementation of a large scale, decentralized grants program is critical to our collective long term success.

I couldn’t be more bullish on the future of more effectively allocating capital and enabling communities to fund their shared needs. Let’s make this turn together!

14 Likes
3

Thanks for this writeup Janine, and the team for all the really thougtful work that has gone into this. As a Gitcoin Contributor and Steward (and Donor although I’m not sure if my quarterly $100 donations count lol), I lean towards directing our efforts to ensuring the Grants Protocol, the product that the entire DAO is now aligned towards building with the ratified Purpose and Essential Intents, gets all the attention it needs.

However I share the main fear identified by this group that going full-tilt on Option 1 could have detrimental impacts on the community’s perception of Gitcoin and the excitement + momentum we build during each Grants Round. Six months (or potentially longer) is a very long time in this ecosystem, and as a team we need more time (and capacity) to re-jig our engagement and marketing + education efforts, which are currently mainly focused on the Grants Program, towards the Grants Protocol. The one thing that Gitcoin decidedly does better than other grants programs in the ecosystem is the hype that our Grants Rounds generate (and this is no doubt due to the massive effort made by the team during these rounds). I believe six months is enough time for both our brand to lose that central place it holds in web3 as well as competitors to catch up in terms of narrative/product.
And there’s no point focusing our efforts in developing a product that people aren’t excited about. It’d be one thing if we were starting from scratch in terms of community buy-in, but to lose this credibility after all the work we’ve done to build it would be a huge loss.

My suggestion would be to meet somewhere in the middle of even these two options (even though Option 2 is sort of offered as a “middle option”). Over the next few months, we will have a better-defined engagement and product marketing strategy geared towards the Protocol, and having a small Grants Round as scheduled could be the buffer we need to maintain momentum. Option 2 as offered still includes six rounds - what if we just had 2-3 of the most popular of these options (OSS, Climate)? I think our Partners will be more understanding if their rounds end up getting delayed due to this (they run on longer timeframes and don’t lose interest as quickly), but users (donors/grantees) may be less forgiving - running a small GR16 can help provent a complete collapsing of narrative/interest.

Whatever direction we choose, I fully believe in this team’s ability to deliver a fantastic product. I know this because we already have one, and I’d like us to make sure we give it the thoughtful farewell that it deserves.

12 Likes
4

I agree on the central thesis of this post. The protocol is launching, cGrants is more hurtful than helpful, and we need a transition plan that best prepares us for the launch of the protocol.

I do not like option 1 at all. A decision to not do any grants round, especially without doing one for the Ethereum ecosystem, is a decision which means people getting laid off before Christmas across the ecosystem. There are projects that live and die by our quarterly cadence. I can’t support surprising them with only 2 months notice.

I do think there is an option that could get the best of both worlds. Perhaps even more limited than your option 2.

One round, only those which fit the main round criteria.

We would need to clearly define the QPQ, token, and other policy items, but the learning would be priceless. Additionally, the Ethereum ecosystem would continue receiving their quarterly support.

I’d push to say the long held Ethereum/OSS norms for inclusion in this round rather than all public goods. Maybe two rounds where grants must choose between the Ethereum/OSS round or all public goods round?

If you accept my reasoning for having a round or two as a must, then let’s think about why my suggestion would be different than your option 2.

  • Only 1 or 2 rounds
  • We close applications 1 week before the round starts
  • No change to manual review process
  • No change to speed of round
  • Avoid using the things that have the biggest issues

Reduced complexity saves time spent reviewing grants

The one or two round option makes it a much cleaner review process which doesn’t involve the many ecosystem and cause round owners!

Unique learning opportunity

We don’t have any study on the effect of having so many rounds which impact each others matching pool. It would be extremely useful to see what happens when all the rounds are in one (or two but mutually exclusive) pool(s).

Potential to run more parts on the Protocol

Perhaps there is an opportunity to run more parts on the protocol to progressively test it as we have with Passport.

15 Likes
5

There’s a helpful harm construct in contract law called detrimental reliance.

Just the construct here. Not applying the construct to contract law, since that’s out of scope here.

The important insight is individual reliance, and how that relates to community responsibility. Precedent/convention, expected patterns of repeated generosity are important factors.

To put this ethics another way far from a ‘liabilities’ narrative, say you feed the birds so long that they forget how to hunt. Then you stop feeding the birds all of a sudden. The birds might starve to death before they remember how to hunt. Or their population has grown so large from your free food that there’s not enough food they can hunt to feed their expanded population size. If you plan to feed them again, how long can each bird starve before starving to death?

I suspect the projects that have already quarter-after-quarter received material grant distributions from Gitcoin might incur a dramatic shock if they too severely miss a quarter’s anticipated cash flow. This is more likely given the depressed market in general.

1) With more notice time of cancelled or materially changed GR16, the more chance community projects will properly decide their Q4-2022/Q1-2023 costs and not accidentally overspend.

=> Mitigate risk of insolvency caused by community projects expecting a reasonable range of capital in Q4 2022 from GR16, based on their GR15, GR14, GR13 track record.

2) I suggest still running GR16 but only offer it to existing grants that have received at least X amount of donations.

=> Lower GitcoinDAO’s administrative overhead a lot while managing the Web3 community cash-flow “detrimental reliance” ethical concerns as much as possible.

:robot: :heart:

7 Likes
6

Thank you for the excellent write-up.

This is a bet the DAO type of decision - if we decide to burn the boats today to shift to our protocol future.

I have been involved in companies shifting from SaaS and more or less proprietary approaches to software delivery to one based on community adoption. In my experience it is always more difficult than anticipated; done right, this shift impacts almost everyone and all activities. I believe this shift towards community adoption of grants protocol ++ poses a risk to us at least as significant as the risk expressed in the write-up of whether our grants protocol launch will immediately hit PMF and sufficient stability at 1.0. For instance, I’m somewhat tangentially exposed to our efforts to potentially build a DevRel motion and while I’m likely missing a lot of effort that has occurred and not been publicized yet - I think we inevitably have quite a ways to go to shift teams around and onboard them and so on, to get developer docs & a community going, and much more including cultural shifts.

Net/net I don’t think we fully appreciate how large a transition this is; if we do, it might make sense to publicize what that plan would look like to transform the DAO to be focused on the community self-adoption of Grants protocol as it would impact nearly everyone in the DAO and others in the community. If we don’t have that plan yet then we may not be quite ready to decide to bet on that plan.

We have incredible talent in the DAO and people emerge from the broader web3 world all the time looking to help. We can and will make a transition to a protocols future grounded on community self-adoption - in time.

Finally, I like the suggestion from @DisruptionJoe to focus on the open-source aspects of our grant rounds. We could then use this round as a means to further cement ties to developers, who are becoming our key persona as we shift to the protocol future.

6 Likes
7

Updated: Given Ive been out of town for a week I know I missed a fair amount of discussion of this. Im down to work together to make things work regardless ofcourse, this was just my initial reaction to the idea.

I believe a stripped down version of the grants round on the existing platform for a round or two is the best way to go.

The cause rounds all have very active communities that can increasingly be involved in running these rounds as we transition to protocol. It would be a real shame to lose momentum with this work and also slow down our partnerships conversations.

Unless we think we will be ready to roll things out early in the new year at the latest I think we need to ride it till the wheels fall off with what we still have. To continue the metaphor that would mean slowing down and being careful to maximize the chances things wont break down.

It would be great if we could do a small intake of any new grantees for only 4 rounds before the round starts. Which would mean mid November.

DEI, DeSci, Climate and MainRound. Sounds good to me.

9 Likes
8

Thanks for raising this important topic to the community, @J9leger. I think this thread is an important discussion for our community as whole to engage with, and I hope we are also exploring how to extend the reach of this post to meaningfully engage our grantees, partners, and donors to validate some of the risks and benefits mapped out above so that we are not setting strategy in a vacuum.

It can’t be overstated the massive team effort required to run our program on cGrants. In GR15, contributors worked very long hours each day to review and approve grants, answer support questions, and troubleshoot/fix bugs that arose on the platform. That’s on top of all of the work that went into onboarding new grantees and donors, creating support documentation for our knowledge base, and socializing the grants round. Essentially, for four weeks (the 2 weeks before the grants round and the 2 week of) these teams slow all other work to focus on making GR15 as successful as possible. I wonder what it would be like if instead all these contributors were focused wholly on preparing for the protocol launch.

But as tempting as Option 1 is, ultimately, I think it’s a bit risky when we have the option and opportunity to socialize the future state of our grants program in a much smaller, more manageable GR16.

My main concern in pursuing Option 2 is a failure to message all changes early, which has the potential to be doubly damaging to our brand, with the teams involved failing to prepare our community for the launch and failing to serve our grantees and partners meaningfully on cGrants. Ultimately, this risk is manageable with the development of a robust engagement strategy as a core component of any planning effort.

As an important player in the ecosystem, it’s the DAO’s responsibility to handle changes like this with care. Engaging and over-communicating will be a necessary component of the transformative future state we’re building.

7 Likes
9

couldnt agree more about the need to over communicate this.

making this decision relatively quickly and decisively will be important.

4 Likes
10

Thanks for the response Saf and for sharing your concerns. To share some context on your concerns. We will be running design partner rounds on the protocol before we transition over the program so there will still be momentum and excitement around programs on the protocol.

Six months (or potentially longer) is a very long time in this ecosystem, and as a team we need more time (and capacity) to re-jig our engagement and marketing + education efforts, which are currently mainly focused on the Grants Program, towards the Grants Protocol.

I’m unclear about this sentence. The reason we would be refocusing our energy on launching the protocol is due to the necessity of prioritizing our time around marketing + education efforts, engaging the community in choosing what areas of focus we prioritize to fund as the program and more. This wouldn’t mean going silent for 6 months, it would mean engaging our community of grantees, donors and funders around the transition to the protocol. During this time we’d also be prioritizing delivering something that our community would be excited about.

what if we just had 2-3 of the most popular of these options (OSS, Climate)? I think our Partners will be more understanding if their rounds end up getting delayed due to this (they run on longer timeframes and don’t lose interest as quickly), but users (donors/grantees) may be less forgiving - running a small GR16 can help provent a complete collapsing of narrative/interest.

To this point, running any round will still require a similar investment in effort as a the option 2 suggested, taking time and energy from the transition to delivering the protocol faster and potentially cause more upset grantees for the many that wouldn’t be in the round.

5 Likes
11

Thanks for the thoughtful suggestion here Joe.

A decision to not do any grants round, especially without doing one for the Ethereum ecosystem, is a decision which means people getting laid off before Christmas across the ecosystem. There are projects that live and die by our quarterly cadence. I can’t support surprising them with only 2 months notice.

Thanks for sharing your concerns. I think it important to look at some data analysis here. Less than 200 grantees from the previous round received above $5K and only 105 received more than $10K. It’s unclear to me how many projects solely rely on Gitcoin to fund their contributors salaries given the volatility around match amount round after round.

Option 1 also doesn’t negate the opportunity to still fund a small number of existing grantees in the time we would have run GR16.

  • We close applications 1 week before the round starts
  • No change to manual review process

If we ran GR16, not changing the manual review process feels extremely detrimental to our community given how painful this process was for grantees, funders and our team. Not to mention the huge number of sybil attacks and fraud we saw and almost let fall through the cracks this season due to this manual process.

Perhaps there is an opportunity to run more parts on the protocol to progressively test it as we have with Passport.

There is 100 percent an opportunity to run rounds with design partners on the protocol in the interim and should be where we are prioritizing our time.

Appreciate your thoughtful perspective Joe and your hope to see something happen to support our core community of grantees in GR16.

8 Likes
12

Thank @J9leger for your summary!
From my Steward perspective, what I mostly am concerned is the development progress, so based on @lthrift updates, I strongly support Option 1.

Suggest to update the Option 1 with timeframe like “Sunset CGrants by the end of 
 and Launch 
”

From the risks, I’d focus on the risks from Grantees and Partners!

If we still keep the current grant review process with limited improvement, what’s the benefit for the grantees with the new grant platform?

I am not convinced by the following points if I was a grantee.

Are these benefits for the partners? I cannot get them.

All in all, it seems really challenging for both options.
so my last question is

do we have the 3rd option?

3 Likes
13

Coming from the perspective of the WS Lead at MMM, I am in support of option 1.

As mentioned before, the cost of marketing a smaller round vs. a larger rounds will require the same lift from the MMM team in terms of assets developed, coordination efforts, etc.

It costs MMM an estimated $150,000 to run the marketing efforts of a Grants Round. This includes:

  • PT Ecosystem round coordinator
  • PT Cause round coordinator
  • Art direction + asset design and development
  • Content development (for blog and social media)
  • Strategic oversight
  • Operations oversight
  • Analytics analysis during and post-grants round
  • Social media monitoring and support

There are about 10 people who are on the MMM team that will be diverting our attention from the Protocol launch to promoting the grants round. Note: this also does not include the cost of PGF Grassroots efforts around Twitter Spaces (running 3x per week, which is no small task).

What I would prefer to see is our efforts redirected toward our maximizing:

  1. the impact of our protocol launch AND
  2. a deep dive into impact reporting

We have monumental task ahead of us to launch the Grants Protocol successfully. From a well thought-out content strategy to a fulsome communication & public relations plan, and creating an impact report + repository of success stories to determining a marketing services launch plan, MMM has its work cut out for itself. Promoting a Grants Round in December will serve mostly as a distraction for our team.

By not running a Grants Round and focusing on our Protocols Launch (and all its associated activities), MMM is poised to request around $50,000-$75,000 less in budget in S16.

On a separate note, I think above all our #1 goal as a DAO is to get the Grants Protocol launched ASAP. If we think from this first principle, our goal should be to support the GPC team in every way possible to get this thing shipped. By running ANYTHING on cgrants, we distract them from this goal and jeopardize the success of Gitcoin regardless of the risks of not running a Grants Round in December. This is why, once again, I am in support of Option 1.

Other options I would consider:

  • Running a small grants round ON the Grants Protocol prior to our intended launch in S17
  • Doing minimal marketing and promotions during a GR16, which allows the MMM team to focus resources and efforts on the Protocol launch
11 Likes
14

Thank you for this fantastic writeup @J9leger, it summarizes in such a transparent way the risks and benefits we see in the various approaches. I have read up on most responses and although I understand the strain option 2 will continue to put on the team, I share the concerns expressed by @safder, @DisruptionJoe, @Jodi_GitcoinDAO and others, as well expressed by @bestape:

I do understand that this will indeed still require a similar investment in effort as the previous rounds, but hope we can mitigate this a bit by more efficiently allocating resources for this upcoming season, through cross-workstream collaboration, to lighten the burden on PGF, specifically by MMM taking over more tasks (already on the way) and FDD helping out wherever necessary. From the side of DAOops (speaking as a WS lead) I hope we can also support here by lowering any ‘overhead’ by extra meetings that can currently be seen as a distraction in these times of hyperfocus on the launch. (as also discussed live)

I definitely like the idea by Joe and echoes by others to focus on OSS and a very minimal approach. I also really like this suggestion to limit new grant creations for this upcoming round as expressed by @bestape, which could further free up resources on FDD’s side but no idea if this is practically and technically feasible.

In any case, I will fully support whatever the team decides, and once again, inspired by all the progress that has been made over the past few months, and the transparency in decision making. Would love for more Stewards - especially Stewards not active in the DAO - to chime in here.

4 Likes
15

This was meant only in context to having one or two mutually exclusive rounds. This would eliminate all the complexity of tags and the dependencies on round managers & external partners which are normally needed for side round decisions.

Overall, I hope you get the feedback you need, the community feels heard, and PGF is empowered to make the decision as owners of the program accountability.

I’m very torn because as much as I’d like to see at least one round, I think it is much more important that this decision is made by the operators who are closest to the problem, PGF.

4 Likes
16

I believe it is essential for Gitcoin to maintain our current momentum and the community’s confidence and we should proceed with smaller rounds in December.

I support @DisruptionJoe with the suggestion of running at least one round for those who closely fit the main round criteria.

4 Likes
17

This is a really tough call. As highlighted above every option has its risks.

After considering all the factors, I vote that we pursue option 1.

A big factor that has me leaning towards option 1 is that every time we run another round on the buggy & fragile c grants platform we lose legitimacy in the community and frustrate a lot of our users/community. I realize we also run the risk of losing even more legitimacy if we choose option 1 and fail to deliver. However, I believe our current team can deliver if we focus all of our attention and energy on getting the grants protocol launched.

2 Likes
18

Really appreciate the transparent and detailed summary highlighting the pros/cons/logistical needs of each option @J9leger. As someone directly involved w/ the funding conversations w/ partners, I foresee a loss of credibility if we were to announce dropping GR16 completely w/ minimal advance warning.

Would hate to see our hard-earned goodwill to tank from rugging our main offering; regardless of grantees financials truly rely on our funding, Gitcoin’s grants program is our bread and butter QoQ and its absence in Q4 will certainly be noticed.

I think there are a couple more ways we can reduce the friction from running/transitioning Cgrants to the Protocol:

  • Reducing our focus to 3-4 top performing relevant cause rounds to maintain our level of QoQ consistency
    • No main round, no ecosystem round–apart from our select Design Partner trials
    • Selected PGF cause round leads to focus on GR16, while the PGF contributors who normally focus on a round that wasn’t selected can focus on the Protocol transition
  • Reducing time window for grant applications to mid November
  • Reducing the # of new grant applicants we accept, prioritizing returning quality grantees–also increasing funding for high-value/signaled projects
  • Finally: wondering how large of a lift it would be involve Passport usage into GR16 Cgrants to bolster sybil resistance?
    • Not talking product integration for Cgrants–can imagine running an Excel matching formula on a spreadsheet to cross reference verified Passport users w/ grant applicants by November X could suffice to knock out low-effort attacks, while giving us decent time to review the remaining.
    • Give audience a heads up that w/ increased sybil attacks–grant applicants must also have verified Passport
    • Not as decentralized as people imagine us to be–but free money simply can’t be handed out this easily without trust, and reasonable people should understand.

From PGF’s conversations, I’ve observed that funders are more excited over our cause rounds that relate to their interests/pillars, because it shows how closely Gitcoin is listening, while supposedly benefitting their business. Although funders recognize the impressive legacy of our main round & are impressed by our early successful grantees–as the Ethereum ecosystem currently stands–it’s extremely saturated at this point w/ even the Merge not creating much effect in this market. My conclusion is less people are building on Eth, and money is going towards specific interests/niches and other chains. Although Main Round is easiest to verify tags, I think a few specific Cause Rounds are the way to go here, axing Main and Ecosystem during GR16.

Not many orgs offer what we offer so consistently, and the potential complaints about the reduced funds/focus can be countered pretty easily by revisiting our Vision of “empowering communities to fund their shared needs.” Although it doesn’t feel very empowering to reduce rounds, raise requirements, and tighten deadlines, it’s even less empowering to rely on a manual, centralized system that can lose grant money to sybil attackers. Like any good public infrastructure, systems are generally forced to temporarily restrict access to make improvements, like roads and operating systems.

Regardless of what we decide, I foresee pushback any way we do it. But rugging GR16 100% worries me about people’s belief in Gitcoin, which will reflect in our token price lol. Humans hate change, even when it’s good for them, so imo the best thing we can do is preparing our counters / documentation / explainer threads to remind them that what we are doing is still extremely true to Gitcoin’s founding vision.

TLDR; Reduce rounds from 7+ main/eco/cause to ~3 top cause. Move grantee application cutoff date in November, increase barrier to entry for safety. Ensure we have materials revisiting our original Vision prepared to counter potential dissent. Allow Cause Round leads for selected upcoming cause rounds focus on GR16, while allowing rest of team to focus on Protocol transition.

PS: Definitely talking very theoretically–only joined Gitcoin a couple months ago so GR15 was my first round here. Please take my words with a pinch of salt.

5 Likes
19

Huge thanks to @J9leger and to everyone that participated in all the heavy work done here. I’m sure this is not an easy task. Just by reading all the comments I can honestly say I feel overwhelmed by the energy and strategic discussions that are taking place in this post.

If all the workstreams focus on preparing the best possible version of G2.0 I’m sure it will help a lot in retrospective. I’m only an initiative lead, but my personal feeling is that there are a lot of areas that require more DAO wide coordination to ensure an optimal protocol launch.

Because examples always help: mandatory twitter verification always helps and it could help “block” a large percentage of “bad actors”. I know that this is optional and up to the round owners to decide => we could create guides/tutorials/articles on how to “Create the best possible rounds from a GPG, PG, FDD perspective and also based on historical facts”

4 Likes
20

I honestly believe the policy should be changed or more clearly defined and we should all be very open to evolution(my self included
I got stuck reviewing grants because we got so many of em
that wasn’t my intent when I joined the DAO).

Almost all of of the grants that were involved in malicious activities were caught before the payouts(just like previous seasons and ~ 250k was saved- not talking about the ring connor spotted, but about grant investigations, which end after the round).This round the grant investigations which I’ve started in season 13 delivered just like every round even if we’ve had a huge workload to handle during the rounds because of platform/main round eligibility

I feel that what was never understond about the manual reviews was that by decentralizing grant reviews we actually leveraged the collective intelligence of our community even if at a small scale, even if they are manual.

The difficult part is that without clearer policy or a “different review system” (which no one currently has a solution 4 and which will not 100% prevent bad actors) we couldn’t deny grants that are just the same as the others before the round begins. After the GR15 begun they sybil attack and engage in all kind of clearly extractive and malicious activities which cannot be prevented by the review process without creating a large amount of double standards and basically making a bad name for Gitcoin.

We are working towards the protocol future though and a small round in GR16 would make a lot of sense. I love @DisruptionJoe 's view on running a two round GR16 which would allow everyone to learn more while preserving the ethos of Gitcoin.

In my POV not running a round will clearly kill the “hype” around Gitcoin and after personally talking with over 1000 grant creators myself I think that I have a real sense of what people want from Gitcoin and they want funding, excitement and to continue buidling.

In the end I’m sure the best option will be chosen in the end because I trust the DAOs collective brain power :brain: :robot: Congratulations everyone!

3 Likes
21

This is a phenomenal discussion and makes a lot of our implicit protocol transition much more explicit – thanks so much @J9leger and team for the thoughtfulness and clarity put into this writeup.

Initially, I was very much pro-Option 1 – put our money where our mouth is, and go all-in protocol.

But as I read through the responses and think through things further, a couple things strike me that push me to try and get a bit creative here. The two main consideration points making me doubt my initial support for Option 1 are:

  • @juanna’s point on timeframe here - the round is less than two months away; if we’ve already set expectatations with lots of funders that GR16 is happening, rugging it completely does feel a bit late.
  • My further thinking on timing, and your callout of the main risk under Option 1 – that even with a pause (Option 1), the protocol is still not ready and we lose further credibility. Now through January just may not be enough time to move the needle on protocol advancement, even with 100% focus.

As a result, I would propose an “Option 3”: Run a “Main Round Only” GR16 and GR17.

Based on my experience running grants programs over the past year, my finger-in-the-air assessment is that this would reduce operational complexity by about 80% vs. running our usual rounds. There’s still work to be done – but it’s much more manageable from every angle (CLR setup, policy, grant review, marketing, payouts
 all of it).

Adding any sort of cause or ecosystem rounds - even if it’s just two or three - substantially increases complexity and distracts from focus. So, personally, I would err towards setting the expectation now that we run two really bare bones rounds that are still the Gitcoin Grants everyone knows & loves on the familiar quarterly cadence, keeping the program alive but giving the team the next six months to focus on protocol in a much more dedicated fashion.

This would probably require an interim re-definition of the “Main Round” and what’s in for these two special rounds in GR16 & GR17 (IMO, it should be pretty broad and include all the archteypes of ecosystem/cause round grantees that have been on the platform prior).

Pros of my Option 3 proposal:

  • Maintains familiar quarterly cadence, grantees still get funding
  • ~80% less work than status quo (And six months of this ‘downtime’ vs. three)
  • A new opportunity to test quadratic funding in its purest form in the context of just a main round - how do all the climate, DeSci, etc. grantees that we’ve garnered in the last couple rounds now stack up funding-wise in absence of dedicated rounds?

Cons of my Option 3 proposal:

  • This still kind of sucks for any funders who were hoping to fund a specific cause or ecosystem round for GR16/GR17 - and, TBD if we could even fundraise sufficiently to make this work (would require a re-framing of expectations/offerings with partners, but I think it’s doable)
  • Doesn’t give the team the 100% protocol focus that Option 1 gives

Lastly, I will say that if a proposal like the Option 3 I’ve outlined isn’t workable or worth considering for whatever reason, my strong support would be for Option 1 over Option 2. I really think we’re kidding ourselves if we think we can run any form of Ecosystem/Cause Rounds and ramp up the focus on the protocol to where it needs to be.

7 Likes