---
# System prepended metadata

title: Drips x Protocol Lab

---

# Protocol Labs 🤝 Drips 

There are numerous ways we can integrate Drips into the PL ecosystem. 

**Option 1** Drips can be PL's all-in-one RPGF stack
**Option 2** PL can use Drips to fund Blue Fund project dependencies
**Option 3** Both 😊

## Option 1
For context, the Drips product enables anyone to:

- Collaboratively define a list of recipients via badgeholder voting (see demo in TG)
- Stream or one-time give any ERC-20 to any GitHub repository, list, or Ethereum address
- Easily claim funds and “pass it on” to other public goods
- Showcase recipient profiles and funding activity over time all in one place
- Create nested lists where funds flow through
- Publish lists as publicly fundable on-chain lists 

Drips is **the best stack for running RetroPGF rounds** because: 
* **Superior UI/UX**. The Drips app allows users to allocate, distribute, and claim funds all in one UX.
* **Better visibility/transparency**. Drips Lists are completely on-chain and composed of Ethereum addresses.
* **Wider impact**. Recipients can decide to split a portion of grant with *their own* dependencies, directly in the app. This enables a cascading effect for RPGF funds with widens the impact as the round as a whole (take a look at the [ether.js profile](https://www.drips.network/app/projects/github/ethers-io/ethers.js?exact) as an example).
* **Secure**. All our contracts and frontends are [professionally audited](https://docs.drips.network/the-protocol/security).
* **Less overhead**. Users can bring their own governance, and use whatever PGF mechanism they prefer (e.g. RPGF, QV).


### How it would work

1. PL Badgeholders nominate recipients to be included in the Drip list. They can do this directly in the app or upload a CSV. 
2. PL RPGF team sets up a **collaborative Drip list** (see demo on TG) with nominated RPGF recipients. The team could set up one list per round, or multiple. 
3. PL RPGF team adds all PL badgeholders to the voter's list (all you need is an Ethereum address) and sets the voting period.
4. PL Badgeholders vote by submitting their own ranked lists of RPGF recipients. The ranking logic is customizeable. Badgeholder lists are submitted privately via off-chain signature. 
5. Voting period ends, and the list of RPGF recipients & voting results are published onchain. 
6. PL team activates the stream.

Alternatively, if you'd like to curate/vote on the list outside of Drips, Drips can still be used **as the distribution tool for any PGF mechanism.** 

## Option 2

The PL Network can allocate $XX to fund their critical dependencies over the course of X year(s). This would replicate [Radworks' dependency funding initiative](https://radworks.mirror.xyz/qopF06RBjKSEhi7HKQgYiyGGfidDAadES4bPXc8xTpE).

### How it would work
* PL Network would set up a Drip list with PL projects (e.g. lip2p, filecoin) as recipients and decide the top-level allocations (% of pool) for each project.
* Each project creates a list of their dependencies and adds the repos they'd like to split funds with. They can create these lists however they'd like. 
* PL Network would stream funds to the top-level list which then cascade through the PL project's lists.

[👉 See this in action on Drips with Radworks](https://www.drips.network/app/drip-lists/50330452048867519181028275890986093327647919805766323166158196453514).


# Other Benefits
* We have a team of 9 that is willing to build alongside of the PL RPGF team in order to meet your needs.
* We can support with KYC, as we have our own KYC consultant onboard.
* Our team can host 1:1 calls with maintainers to facilitate the creation of dependency lists. 


# Open Questions from PL
* *How do you see it working? Core devs nominate a set of repos to start from and we add each of them? Or could we make a virtual repo (fil-drips) that links to all the other repos as its deps?*
    * See above!
* *What are the tradeoffs on being separate side-by-side program vs being a distribution mode for the v0 easy-retro-pgf for Filecoin?*

  * Being separate side-by-side programs enables focused testing of different programs, while serving as a distribution mode for RetroPGF widens impact by not only reaching recipients but also potentially cascading funds to their dependencies.
* *How flexible is the Drip schedule? If sufficiently flexible to create ~cliff unlock or ~immediate unlock, then maybe it could a be a generic distribution tool too*
    * The Drips schedule is very flexible. You have three options: 
        1. You can do a simple transfer (or many) to the recipients list, that further distributes the tokens immediately based on the weights.
        2. You can stream tokens to the recipients list over time (you specify the rate and duration) 
        3. Combine the first two. For example, you can do a transfer up front and then start streaming at some point in the future or a transfer upfront and start streaming immediately after etc...
    * Technically there is no "cliff" concept but this can be implemented by delaying the stream over the cliff period, which once passed would trigger a one-time transfer and initiate subsequent streaming.
* *What would be the decisions/actions/timeline to drip FIL?*
    * Ready to go. Once we have the answers to the questions above, we can start.
    
# More on Drips

### Resources

**[Drips App](https://www.drips.network/app)**

**[Drips Docs](https://docs.drips.network/)**

**[Radworks Gives $1M to FOSS Dependencies with Drips](https://radworks.mirror.xyz/qopF06RBjKSEhi7HKQgYiyGGfidDAadES4bPXc8xTpE)**

**[Octant Teams Up with Drips to Fund its Dependencies
](https://radworks.mirror.xyz/ABW_l2dGRuJ-iY9iYEbVTtlbQ6rvsaDw0ReQ8rkc0Bc)**

### From the Community
* Wagmi: https://x.com/wevm_dev/status/1752132002952741018
* Ethersjs: https://x.com/ricmoo/status/1752391525378437504
* BuildGuild: https://x.com/austingriffith/status/1752140687015920109
* Banteg: https://x.com/bantg/status/1752349573731799365
