Drips Wave
Drips Wave is a recurring bounty cycle that helps ecosystems attract developers and accelerate maintenance through predictable monthly one-week sprints. Contributors fix open-source issues tagged with Point values, earn rewards based on their share of Points, and build verifiable portfolios. Ecosystems and maintainers apply to run Wave Programs to incentivize contributions across repositories, while developers join active Waves to earn by solving scoped tasks.
Eligibility: Ecosystems (e.g., Stellar Development Foundation), project maintainers within ecosystems, and contributors/developers seeking to earn rewards by fixing open-source issues.
Pipeline
Funder track record · does Drips actually pay grants?
🟡 Some payout evidence · 1 grantee found · last payout 2026-01-07 · checked 2026-11-17 · 0 forum reports, 6 web pages read, 8 unverifiable claims dropped
Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.
| Grantee | Amount | Date | Evidence |
|---|---|---|---|
| Oky | — | 2026-01-07 page date | “Oky is an open-source digital period tracker and education product, co-created with and for girls.” source |
Trust breakdown (1/3 checkable facts verified)
| Signal | Weight | Result | Note |
|---|---|---|---|
| deadline | 0.35 | 0% | rolling claimed but not stated |
| apply link | 0.075 | 0% | link not in source |
| funder | 0.075 | 100% | named in source |
| source quality | 0.15 | 50% | social or search hit |
| model confidence | 0.1 | 80% | model self-report |
Fit breakdown (against the ORG_* profile)
| Signal | Weight | Result | Note |
|---|---|---|---|
| model fit | 0.5 | 10% | model rated 10% |
| ecosystem overlap | 0.25 | 0% | stellar vs aleo |
| category overlap | 0.15 | 17% | dev_tooling, community vs zk, privacy, infra, dev_tooling, security, interoperability |
| tech overlap | 0.1 | 0% | github vs rust, leo, zk |
Sources (1)
| Role | Document | From | Fetched |
|---|---|---|---|
| primary | Drips Wave – Drips Docs | Web discovery: ecosystem sweep | 2026-10-18 |
History (1)
| v | Changed | Fields |
|---|---|---|
| 1 | 2026-10-18 | created |
Extracted text
Drips Wave is a recurring bounty cycle designed to help ecosystems attract developers, accelerate maintenance, and grow their communities. Instead of one-off grants or long-term commitments, Wave creates a predictable rhythm of contribution where developers can "Fix, Merge, and Earn." By focusing on short, structured cycles, typically running for one week every month, Wave bridges the gap between available funding and the day-to-day work that maintainers need help with.  Browsing issues part of a Wave Program. ## Who is Drips Wave for?[ ](/wave/#who-is-drips-wave-for) * **Ecosystems** such as the Stellar Development Foundation use Drips Wave to broadly incentivize contributions across their entire open-source ecosystem. * **Project Maintainers** within those ecosystems use Wave to attract new contributions, clear their backlog, and grow their community. * **Contributors** earn rewards while building a verifiable portfolio of work in top-tier open-source projects. ## The Anatomy of a Wave[ ](/wave/#the-anatomy-of-a-wave) One or more **Wave Programs** run on a predictable cycle, with **Waves** occurring at regular intervals. Each Wave Program is centered around a specific open-source ecosystem (e.g., Stellar). A Wave is a synchronized event that concentrates community energy. While parameters can be adjusted, a typical Wave follows this lifecycle: 1. **Scoping**: Ecosystem maintainers apply their repositories to a Wave Program. Once approved by the program's organizers, maintainers add issues that they want the community to tackle during the upcoming Wave. These issues are tagged with specific Point values based on their complexity and impact. 2. **The Sprint**: The Wave opens for a set period (e.g., one week). Contributors browse available tasks, log in with their GitHub accounts, and submit pull requests to fix issues. For each resolved issue, contributors earn Points. 3. **Reward**: Progress is tracked automatically via points and leaderboards. Once the cycle concludes and work is verified, rewards are distributed to the successful contributors according to their share of Points earned during the Wave.  The Wave lifecycle: A recurring frantic sprint and reward payout. ## Why Run a Wave Program on Drips?[ ](/wave/#why-run-a-wave-program-on-drips) Wave is built to solve the "maintenance gap" in open-source funding. It provides the tooling to turn a budget into tangible code progress with minimal friction. ### 🔄 Predictable Rhythm[ ](/wave/#-predictable-rhythm) Regularity breeds engagement. By running monthly cycles, you create a habit for contributors to return to your ecosystem. It keeps existing developers engaged while providing a reliable schedule for new ones to join. ### 🎯 Focused Impact[ ](/wave/#-focused-impact) Grants are great for big ideas, but Waves are for getting things done. Maintainers can direct community power toward specific roadmap blockers, bug fixes, or documentation needs that often fall through the cracks. ### 🚀 Accessible Entry Points[ ](/wave/#-accessible-entry-points) For new developers, a massive codebase can be intimidating. Waves present scoped, manageable tasks that allow contributors to build a track record and earn trust (and income) quickly. It is an ideal funnel for discovering future core contributors. ### 🤖 Automated Operations[ ](/wave/#-automated-operations) Drips handles the heavy lifting of tracking contributions, managing the review flow, and calculating rewards. This reduces the administrative burden on maintainers, allowing them to focus on code reviews rather than spreadsheets. ## Getting Started[ ](/wave/#getting-started) Whether you are an ecosystem looking to boost activity or a developer ready to earn, here is how to get started. ### For Maintainers[ ](/wave/#for-maintainers) Learn how to leverage Drips Wave to clear your backlog and grow your contributor base. * [**Participating in a Wave**](/wave/maintainers/participating-in-a-wave): Learn how to apply your repositories for a Wave Program, add issues to a Wave, and manage contributions. * [**Understanding Points & Rewards**](/wave/points-and-rewards): A breakdown of how contributions are valued and how payouts work. * [**Applicant metrics**](/wave/applicant-metrics): How the Code Metrics scorecard and language profile are calculated. ### For Contributors[ ](/wave/#for-contributors) Ready to fix, merge, and earn? * [**Join a Wave**](/wave/contributors/solving-issues-and-earning-rewards): How to find active Waves, and start contributing. * [**Understanding Points & Rewards**](/wave/points-and-rewards): A breakdown of how contributions are valued and how payouts work. * [**Applicant metrics**](/wave/applicant-metrics): How the Code Metrics scorecard and language profile are calculated.