Coordination.Party Kit

Hey everyone, I wanted to give ya’ll a heads up about a tool that Moonshot Collective is working on right now, we are aiming to launch in February at Schelling Point.

It’s called Coordination Party Kit.

The objective of this post is to

  1. share the deep strategic context for the build out of this toolkit.
  2. invite you to join us in it’s build out or marketing.

Coordination.Party Kit

North star opportunity: Coordination Tooling for DAOs

The Moonshot Collective is building built Coordination.Party Kit (hereforth CPK) - a tool suite that helps recruit, recognize, reward, and retain contributors to DAOs. We believe that web3-native coordination technology is a massive game-changer for how tokens + talent combine to push forward the mission of GitcoinDAO, and also other DAOs.

The Coordination.Party Kit is like a toolbox. You might buy it because you want a screwdriver, but its useful to have a wrench + pliars + a hammer when you need it too.

The Coordination.Party Kit augments Gitcoin’s existing product suite (Grants + Hackathons) in the following ways.

  1. The existing products are high TTV (cost $10k+ + take weeks to realize value) whereas the CPK is low TTV (costs $10+ + takes minutes to realize value)
  2. The existing products are monolithic + laden with tech debt, making them costly + difficult to maintain. The CPK is a series of Simple, Antifragile, and Modular tools, making them easy to maintain (if they are successful) or easy to throw away (if they are not successful). The Coordination.Party kit is bottoms up collection of tools, not a top down monolith.

Tools in coordination party kit

Lets get into the specifics of each Coordination.Party Kit tool.


The hypothesis with is that by recognizing+ rewarding participants in calls or other live events in a lightweight way, we can create deeper engagement between the call hosts + attendees.

The core use cases that need to work great are:

  1. Call hosts can reward participants to call without a lot of UX or financial overhead.
  2. Call attendees can easily participate
  3. Call atteendees are aware of their rewards when they are received.
  4. It needs to be easy to add my own DAO’s token to the tool.

What success looks like at Schelling Point: 10 tip.parties with aggregate 100+ participants have been held, and at least 10% of those participants take back to their own DAOs.

Play with the alpha at


The hypothesis for is that we can decentralize the recognition + rewarding + retainment of participants of teams in a lightweight way. And that by decentralizing this process, we can push power to the edges, away from “bosses”, creating higher morale.

The core use cases that need to work great are.

  1. Hosting a pay party is easy, not a lot of UX or financial overhead.
  2. Participating in a pay party is easy, not a lot of UX or financial overhead.
  3. Participants are aware of their rewards when they are received.
  4. It needs to be easy to add my own DAO’s token to the tool.

What success looks like at Schelling Point: 1 with aggregate 25+ participants have been held, and at least 10% of those participants take back to their own DAOs.

Play with the alpha at

The hypothesis for is that DAO-native talent is the scarcest resource in the space, and that by giving talent upside in the process recruitment, we can build a better candidate tracking + candidate system than those that have existed in the past.

To accomplish success in the long term for we will need to create network effects for the tool
To accomplsih success in the short term, we need to make it easy to upload a resume or to search for a resume.

The core use cases that need to work great are.

  1. Searching for + contacting talent in bulk needs to be easy + high ROI (eg I’m finding candidates I’d actually want to work with.)
  2. Uploading my information to the system is easy + high ROI (eg I make connections I want or make $$$ from the connections)
  3. There are no major friction points in the funnel where 60% or more of the traffic falls off.

What success looks like at Schelling Point: 50 people upload their resume to, and at least 50% of those participants make $$$ from doing so (and are aware they made $$$).

The hypothesis for is that DAO contributors want a steady source of income, but DAO administrators want downside protection if thet DAO contributor goes away for a while. The way TSP solves this is by creating streams of tokenized payments which only continue to flow if they are withdrawn (and a status report is submitted once a week).

The core use cases that need to work great are.

  1. Setting up a stream is easy, low overhead, and high ROI.
  2. Receiving a stream is easy, low overhead, and high ROI.
  3. It needs to be easy to add my own DAO’s token to the tool.

What success looks like at Schelling Point: We get 100 participants to agree to help GitcoinDAO’s mission + put them on token streams. At least 50% of them withdraw within 1 month and at least 25% of them are still contributing to GitcoinDAO within 3 months.

Play with the alpha at

PGP is a fork of Gitcoin’s dGrants product. The hypothesis for PGP is that DAO’s want to run their own Quadratic Funding rounds. The meta-hypothesis is that Moonshot Collective running experiments + submitting upstream PRs to dGrants will make the QF tool even more successful (eg more $$$ raised for more DAOs)

The core use cases that need to work great are:

  1. setting up a round is easy / high ROI
  2. seeing how a round is going easy / high ROI
  3. creating a grant is easy / high ROI
  4. contributing to a grant is easy / high ROI
  5. It needs to be easy to add my own DAO’s token to the tool.

(note: most of the UX of this is handled upstream by dGrants already - but its possible by forking these tools + marketing them ourselves well discover upstream issues )

What success looks like at Schelling Point: We run a one day QF round at SP, in which at least 50 participants have contributed to speakers. At least 5 people take dGrants back to their own DAOs to run QF rounds. is Moonshot Collectives’ Retroactive Public Goods Funding starter kit. The hypothesis for FP is that as more and more public goods in the Ethereum space are well funded (by Quadratic Funding, Retroactive Public Goods Funding, or similar), projects will want to be oriented to receive those rewards. Fund.Party provides an easy way of tracking who has contributed to what, so that future retroactive distributions are easy.

The core use cases that need to work great are:

  1. setting up a is easy / high ROI
  2. awarding contributors via a is easy / high ROI
  3. future retroactive distributions to users is easy + baked into the Optimism RGPF process

What success looks like at Schelling Point: Karl Flouresch is really excited about + shills it on stage at SP.

GreenPill.Party is a simple tool that allows anyone to pledge a portion of their wealth to public goods.

The core use cases that need to work great are:

  1. its easy to make a giving pledge via GPP
  2. when someone sees a giving pledge, they go to + find it easy/compelling to complete a giving pledge themselves.

What success looks like at Schelling Point: 5 Tier A DAO contributors complete a giving pledge.

Play with the alpha at

Consistency across tools.

We are aiming to make the whole of these tools greater than the sum of their parts. Each tool could be:

  1. Listed on to allow easy discoverability.
  2. Have a backlink to somewhere prominent (perhaps in its header) in order to allow cross-discovery between tools.
  3. Have a common color scheme to create brand consistency.
  4. Have a “built by the Gitcoin community” button in the footer.
  5. Have a navigation & onboarding structure oriented around educating the end-user about how it solves for the users’ JTBD (Job to be done).
  6. Consistent network deployment. Each tool in the CPK should support the same L1s/L2s + it should be easy/clear which ones are supported.

Where things stand now and are still in active development.

Given that and are already built technology wise I hope the technology risk for these tools is minimal.

Ux love needed tho, just because the major dev lift is done doesn’t mean it solves the customer needs (yet). We really need people who can think like product managers and iron out these kinks by trialing them with customers and working with designers to write clear tickets about how to tweak the products.

Go to market strategy


We are presently dogfooding these tools within the moonshot collective, and have begun sharing them with other GitcoinDAO workstreams (specifically the FDD and MMM). As part of this dogofooding, we are going through an iterative cycle of hypothesis => experiment => results => learning (repeat if success is within sight, shut down the tool if not)..

The goal of dogfooding is to make the tools as useful for our own needs (but keep in the back of our minds the need to generalizable to others’ needs)

The 2/17/2022 launch

We are launching Coordination Party Kit at Schelling Point on 2/17/2022; a one day GitcoinDAO conference about coordionation. GitcoinDAO is putting on this event and has sourced prominent speakers across the industry (Vitalik Buterin, Santi Siri, and others) to create a “Schelling Point for the Hopeful” - a contingent of Ethereans who want to build a better world with coordination technology. There is an opportunity to imbue the CPK into the event in ways that SHOW not TELL how powerful coordination technology can be. There is an opportunity to market our tools to the top DAOs in the space at this event.

The criteria for success of this launch is simply the following: 10 attendees at schelling point take home the CPK + trial them in 10 unique DAOs.

Some proposed experiments of how this could be done:

  1. a for every talk could reward attendees for coming to talks of speakers they love.
  2. run a one day QF round for the Schelling Point event ( could help fund causes that speakers & attendees care about.
  3. ask everyone at the event to “take the green pill” ( creating lots of funding for public goods.
  4. launch, gathering 100s of resumes of web3 native talent + creating income for the top contributors in the space.
  5. run a at the end of the event to reward those who made the vent great.
  6. we put talks from the moonshot collective members on stage during the day to give demos.

Of course, these are all just experiments we could do. They are not canon, I’d love to see more ideas bottoms up.

How to get involved

If you are a dev, designer, or PM who wants to help would with the launch say hi in the 2/17 launch telegram group.

If you would like too try out the CPKP in your own DAO, please also join the 2/17 launch telegram group.



The GreenPill.Party look so great!

And I really like Coordination.Party Kit!

:heart_eyes: :star_struck:


Looks really great!
Looking forward to it!


Will these tools plan to launch in Matic or other EVM supported Chain? Or Will it allow participate choose different token/chain they prefer.

1 Like

Really awesome tools here. These are fantastic.


In the month of January, 100% of moonshot pay was made using moonshot built products. This is a major milestone; all of our payment products are in a working state!

At the Collective we currently have 16 active contributor tokenstreams. While our compensation policy has not been completely ratified (see OKR’s and planned accomplishments here) these streams serve as basic income for our contributors. We target ~20% of total compensation with these streams. The other 80% of contributor pay comes from another product:

We have successfully coordinated and held many pay party elections, or voting periods where contributors select candidates and cast their votes. These votes serve as the peer to peer voting mechanics of and determine what the payout will be to any given contributor in that election.

One property that was baked in is the ability to add voters that are not candidates, i.e. they can only vote on other candidates and not themselves. This allows us to add voters that may not be contributing to that product but have great insight into who did what work in the specified time period.

These elections can be tricky in an async, dao native environment. What makes this difficult? One major hurdle to overcome was the differing time zones of our contributors, it was hard to get everyone in the same place at the same time to nominate the ‘candidates’ to be voted on. As a workaround, we leveraged another one of our products, tip party, to aggregate all the appropriate contributors on a per project basis.

Elections can be created by any EOA (externally owned account; not contract wallet) rather than having to use the multisig and dealing with the complexities of asynchronous message signing.

Once everyone votes, which is usually capped at around 24 hours, we then connect the treasury multisig or the ‘baby sig’ and distribute the funds. It’s important to note that the description of the election should contain how the payout will be distributed i.e. quadratic vs linear. We have chosen to use linear payouts as quadratic tends to tighten the pack and that is not the intended outcome when looking to identify and compensate the ‘damage dealers’ of any given project.

In December, as we first started to form what our compensation would look like, a gap was exposed in that we would have to batch send transactions to settle up where the elections and streams fell short of total compensation commitments.

At moonshot we don’t target hourly rates per se, but behind the scenes we use spreadsheets to track how much USD our contributors are being ‘paid’ for their time. This is done to ensure that we are rewarding them fairly. To get these payments out, we had to use multisender(dot)app, the same app we had to use to fill streams.

Every transaction using this app has an added fee of .09 ETH, which our multisig does not natively own. While swapping into ETH has been done for this process specifically, anyone who has ever done this knows the challenges this poses.

It was realized that many had this need for an app which can bundle multiple transactions and send varying amounts of tokens to each user, however; no one had built it yet. Leveraging our connections to scaffold-eth the multidropper was quickly prototyped. This was the final piece in having all our contributors paid using only MC products.

As the person currently overseeing compensation and contributor success, this milestone was not only awesome, but for the team morale to validate that we can ship at this pace while also standing up a healthy workstream of a DAO was a major success from my point of view.

As we move into Season 13 it is becoming apparent that other workstreams in the DAO are starting to uncover the same needs that Moonshot had when starting to pay contributors. We are deploying resources now to bring these products and ideas to you and really dive deep into usability tests.

In these test sessions, we will uncover how these products could improve to suit your workstream needs while you are helping us to validate our products. Much of these needs will be fulfilled through our prototype budget to ship solutions as fast/safe as possible to meet the ever-increasing needs of other workstreams and DAO’s.

In addition to all of this, as we transform into our Target state we have a pipeline of talent coming up through Speedrun Ethereum and natively through GitcoinDAO. To attract and retain this talent we need to be quick to pay our contributors. The starting stream for contributors at moonshot is 120 gtc at a 4 week drip rate. We plan to bring on new contributors in the design, product and developer space. The intent of this budget is to do just that, while simultaneously being held accountable to our ratified OKRs.