> For the complete documentation index, see [llms.txt](https://docs.oscollective.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oscollective.org/campaigns-and-partnerships/drips.md). # Drips ## Supporting a project through Drips If a project is hosted by Open Source Collective (OSC) and is set up on Drips, funds sent through Drips can be automatically transferred on a periodic basis. Simply sponsor the project on Drips, and we'll do the rest. *** ## Claiming your Collective with Drips Open Source Collective can 'Claim' a project on your behalf. Before requesting, we claim a project, you will need: * A **GitHub organization** (not an individual user account) that hosts your repository/repositories on GitHub. You can create a GitHub organization by following [this guide](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch). * A[ Collective](https://opencollective.com/opensource/apply) on the Open Collective platform for your open source project. You will need to use Open Source Collective as your fiscal host. [Read more about applying to OSC here.](/how-to-apply.md) * Commit access to the corresponding code repository. * Optional: A hardware or software wallet that supports the Ethereum network. Once you have been accepted to Open Source Collective, contact us at to organize an onboarding call. During our onboarding process, we will: * Provide a quick overview of how Drips works. * Determine whether you would like to use a multi-signature wallet, or have OSC generate and own a wallet for your project. * Decide on an amount to send to your project's balance, to other maintainers directly, and to other projects. *** ## Using Drips with a Safe Wallet Drips can be used through a multi-signature Safe wallet in much the same way Drips is used with an individual wallet. Transactions are 'proposed' to the Safe Wallet for signing by the Drips application, and executed once the threshold has been reached and execution costs paid. {% hint style="info" %} Note that gas fees will be due on transactions written to the Ethereum blockchain; this includes claiming a project on Drips, modifying splits, and collecting funds. Open Source Collective will pay for and charge these costs back to the Collective if needed. {% endhint %} [Read more about using Drips with a Safe Wallet here.](https://docs.drips.network/usage-with-a-safe/) *** ## Receiving Financial Contributions Drips facilitates the constant stream of any ERC-20 token to any number of projects, represented by a GitHub repository. OSC initiates the collection of allocated funds on a periodic basis (typically monthly) based on the amounts received in order to reduce transaction costs. Funds will be added to the Collectives' balance, minus our 10% host fee, on a periodic basis. Drips will be indicated as the source of the funds. A project administrator may be required to sign the document containing the funds collected from Drips. *** ## Frequently Asked Questions ### When will we receive our contributions from Drips? We will request funds from Drips at a frequency that works best for your project, typically monthly. ### What fees will be charged? A standard 10% hosting fee applies to funds credited to your Collective. Gas fees will be due on transactions written to the Ethereum blockchain; this includes claiming a project on Drips, modifying splits, and collecting funds. Open Source Collective will pay for and charge these costs as needed. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.oscollective.org/campaigns-and-partnerships/drips.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.