Edited (version 9)
Retro PGF
Retroactive Public Goods Funding
⛶ Fullscreen
↓ Download
This challenge is based on an interview by Philip Heltweg with David Gasquez about funding models and open data in the Web3 ecosystem.
Retroactive Public Goods Funding (Retro Funding) is based on the idea that it's easier to agree on what was useful in the past than what might be useful in the future -- Optimism community
{ hacknight challenges }
Read the full conversation or our summary below, and check out the recommended learning resources:
✅ Get the book: Designing Data-Intensive Applications by Martin Kleppmann
✅ Try out Kaggle and AIcrowd, platforms for data science competitions
Find a person to interview in the context of open source/data ecosystems in your near vicinity, or online. Publish this interview as a recording, blog or social media post. Share the link here and on social media.
Design and build a platform or application that leverages open data portals to create value and generate revenue. Inspired by Drip Lists, GitHub Sponsors, Gitcoin Grants and Filecoin Open Grants, we challenge you to create a innovative solution that showcases the potential of open data ecosystems.
The article features an interview with David Gasquez, who works independently on open data projects within the Web3 community. The conversation focuses on "Retroactive Public Good Funding" (Retro PDF), a novel funding approach in Web3. David's Background: David Gasquez works self-employed on open data projects, focusing on the Web3 ecosystem, aiming to create open pipelines with open data.
Retroactive Public Good Funding (Retro PDF) is defined as a grant received after completing a project. It involves building a fund for existing projects, community voting, and retroactive distribution of funds to selected projects. Implementation examples include voting via Google spreadsheets or the Filecoin data portal.
The interview speculates on whether this funding model could work outside Web3, potentially for open data portals or even public goods like parks, with participatory budgeting as a similar concept. There is mention of possible experimentation by the Linux Foundation, which needs to be confirmed. David mentions the importance of learning from previous rounds, as seen in Gitcoin's approach, to improve aspects like project surfacing, impact measurement, and more.
(Summarized will help from Llama 3.1)
This content is a preview from an
external site.
Project
Event finish
I've set up a Fider poll where you can quickly log-in and leave your vote for an Open Collective: https://hacknight.fider.io/
4 weeks ago
~
loleg
Start
All attendees, sponsors, partners, volunteers and staff at our hackathon are required to agree with the Hack Code of Conduct. Organisers will enforce this code throughout the event. We expect cooperation from all participants to ensure a safe environment for everybody.
The contents of this website, unless otherwise stated, are licensed under a Creative Commons Attribution 4.0 International License.
Category
Challenges
Projects in need of patching, ideas of things to start - put your thinking caps on and take part in an open source challenge presented at the HACKnight! Contact us if you have any questions, or add one of your own through GitHub or after logging in here. We recommend that every Challenge proposes tasks on several levels:
NEWBIE challenges about becoming a user of a product/project and learning the ropes.
INTERMEDIATE tasks for people with experience in the project and/or the technical domains involved.
EXPERT challenges will include things like security testing, performance optimisation and other advanced topics.
Demand public funding for free and open source software 🇪🇺 Sign an open letter to the European Commission (via Proxeus)