Welcome to the GoodDollar Builders Pool
This is the home for builders who want to shape the GoodDollar ecosystem.
If you’re excited about open-source, public goods, and shipping real-world impact, you belong here.
This category is where we explore, discuss, and refine ideas for work that can be supported through the GoodDollar Open Source Contributors Pool (Gardens).
Our goal is simple:
Give builders real ownership over what gets built, and a clear path to be rewarded for meaningful open-source contributions.
Who This Space Is For
Builders (individuals or teams) who are ready to propose, design, and build meaningful improvements to the GoodDollar ecosystem.
Every proposal should meaningfully support one or more of these ecosystem goals:
- Increase G$ utility and velocity (earn, spend, stream).
- Attract and retain builders and ship real integrations.
- Help shift users from claimers → earners.
- Expand markets and merchants that accept G$.
You don’t need to have everything figured out yet , but you do need the intent, ownership, and capacity to execute.
What You Can Do Here
- Share early ideas and rough concepts
- Post contributor proposals
- Apply to join the committee
- Ask for feedback or direction
- Help review and strengthen other proposals
Even small suggestions and thoughtful feedback make a big difference.
Choose Your Path
There are two main ways or roles to participate. If you choose either path, feel free to use this proposal template.
Path 1 — Become a Contributor
Contributors propose and build improvements to the GoodDollar ecosystem.
This can include: Protocol or contract improvements, SDK or dApp features, Integrations with external tools, Performance, security, or developer experience improvements
You’re a great fit for this if :
- You’re aligned with the GoodDollar ecosystem’s mission and growth goals.
- You can clearly outline your project’s scope, deliverables, timeline, and testing approach.
- You’re open to building open-source and licensing your work in a way that’s compatible with existing repos.
- You’re comfortable sharing regular updates with the community (e.g., via Telegram, Discourse, and potentially GitHub Discussions).
- You’re a builder (solo or with a team) with the skills and capacity to execute on your own proposal.
How to post
Create a topic titled:
[Contributor Proposal] Project Name
Include:
- Problem you’re solving
- Proposed solution
- Scope & deliverables
- Rough timeline or milestones
Good proposals are clear, honest about complexity, and open to feedback.
Path 2 — Join the Committee
Committee members help steward the ecosystem by:
- Reviewing proposals
- Supporting contributors
- Participating in governance and direction-setting
You’re a great fit for this if you:
- Have Web3 or public-goods product experience (including substantial design, documentation, or architecture work impacting repositories)
- Are familiar with GoodDollar’s code or goals
- Have previously contributed, mentored, reviewed, or shipped impactful work
How to post
Create a topic titled:
[Committee Application] Your Name
Include:
- Short introduction
- Relevant experience
- Availability
- How you’d like to help
- Where you’d like to participate (governance, reviews, mentorship, etc.)
How the Open Source Contributors Pool Works
The pool is designed to support builders who want to propose, build, and get rewarded for meaningful open-source work in the GoodDollar ecosystem.
At a high level:
- Contributors propose and deliver work
- Committee members help review, guide, and steward the pool
- Funding is distributed through Gardens after work is completed and approved
Shared Rules & Expectations
These rules exist to keep the pool fair, transparent, and sustainable:
-
Funding cap
No single proposal may request more than 25% of the pool’s available funds
-
Symbolic G$ stake (Gardens requirement)
To submit or vote on proposals in Gardens, you’ll need to join the Builders Community by staking a small, symbolic amount of G$
-
Align before you build
Contributors must first align their proposal on Discourse (scope, deliverables, and budget) before starting work
-
Funding after completion
Proposals are submitted to Gardens for payment after the work is completed and merged
-
Committee decisions
Committee members use majority voting to approve work and funding
-
Committee retroactive funding
Committee members may submit proposals to compensate ongoing governance and review work
How Proposals Move Forward
- Post your idea or application
- Discuss and refine with the community and committee
- Align on scope, deliverables, and expectations
- Build and open a PR
- See PR guidelines
- After merge, submit to the Open Source Contributors Pool (Gardens) for funding
Simple, transparent, and collaborative.
Other Ways to Contribute
If this path isn’t the right fit right now, check out our other Builder Initiatives:
-
GoodDollar Bounties → Pick scoped tasks, ship PRs, earn G$
-
GoodBuilders Program → Build full products or long-term integrations using G$
Join Builders Telegram → Telegram: View @gooddollarbounties
A Quick Note
- This category is for the Gardens-backed Open Source Contributors Pool
- It is not part of GoodDAO governance
- Funding comes from the Good Labs Foundation
Docs, Repos & Builder Resources
- Documentation → https://docs.gooddollar.org
- All GoodDollar repositories → GoodDollar · GitHub
Core Repositories
- GoodProtocol - Core GoodDollar smart contracts (v2)
- GoodSDKs - Latest SDKs (ethers v6), flow-wrappers (claiming, identity, etc.), and builder utilities
- GoodProtocolUI - UI for interacting with GoodDollar smart contracts (gooddapp.org)
- GoodWeb3-Mono - Legacy monorepo with web3 UI components and SDKs (ethers v5)
- GoodCollective - Monorepo for GoodCollective (Segmented UBI & Direct Payments Pools)
- mento-core- Core smart contracts for the new GoodDollar reserve
Community & Support
- Builders Telegram → Telegram: View @gooddollarbounties
If you’re unsure where to start, post anyway.
If you want to sanity-check an idea, post it.
If you just want to introduce yourself, post it.
We’re building this ecosystem together. Welcome!
