Drips is a decentralized toolkit for public goods funding. FIL-RetroPGF-2 is using Drips to distribute FIL to projects receiving funding in the round. One of the benefits of Drips is that it enables funds to be sent to a project’s Github repository and then claimed later by recipients using an Ethereum-style Filecoin wallet.
You will need to choose a public GitHub repository to use to receive funds as part of FIL-RetroPGF-2. If your project has a primary public Github repository associated with your work, we recommend that you submit that one. If your project has many public GitHub repositories associated with it, but doesn’t really have a “primary” one, we recommend that you either pick one to use, or create a new repository to use for the purpose of receiving funds. If your team does not already have a public GitHub repository, you will need to create one in order to receive any funds awarded as part of FIL-RetroPGF-2.
IMPORTANT NOTE: any GitHub user who has commit/merge access on the repository you submit with your application will have access to any funds sent to the project through Drips, so you should only submit a GitHub repository for which you trust all of the users who have this level of access.
Creating a public GitHub repository is easy. Make sure to only give commit/merge access to GitHub users who you are okay with having access to any funds sent to the project through Drips.
Claiming your GitHub repository on Drips is easy! See this guide in the Drips docs for detailed instructions. Note that you will need to use a 0x-style Filecoin wallet in order to claim your repository.
Any GitHub user who has commit/merge access to the repository you submit will have the ability to claim funds sent to the project through Drips. So if you have people who have this level of access to your repository who you do not want to have access to funds sent to you, you should either revoke their access before submitting the repository, or create a new repository to use for receiving funds, limit access to that repository accordingly and submit the new repository with your application instead.