A community of regen builders shipping public goods for impact measurement, capital allocation, capital formation and community coordination.
We are one of several skill-specific Guilds under the Greenpill Network — a decentralized community of regional Chapters and skill-specific Guilds working to turn degens into regens. Since October 2023 we've been building tools, running grant rounds, and supporting Greenpill Chapters across the world.
We are both grantees and grantmakers: funded by Octant, Giveth, and Gitcoin — and operating Grant Ships and Gitcoin community rounds that fund other regen projects.
Active guild-owned projects we build and maintain:
| Project | What it does | Stack |
|---|---|---|
| green-goods | Offline-first PWA documenting regenerative work on-chain (attestations, hypercerts, impact). Flagship. | TypeScript · Solidity · Bun |
| network-website | Frontend for greenpill.network. | TypeScript |
This profile focuses on guild-owned GitHub projects and earlier guild artifacts. Upstream forks we use for ecosystem contribution or integration are not treated as active project inventory here.
Green Goods, our flagship, is where most of the building happens. Its open pull requests show what is in progress.
Every Green Goods release, with its notes, is on the releases page.
Five teams organize the work: Product, Research, Community, Growth, and Marketing, all tracked in Linear. How we run them explains what each team is for and how its work flows.
Notable earlier artifacts — public, open-source, and worth referencing:
- greenwill · Farcaster Frame for regen reputation scoring (the "GreenWill" reputation primitive)
- allo-yeeter · Allo-protocol disbursement tool
- impact-reef · Qualitative impact evaluation
- regen-rabbit-race · Farcaster betting frame
- greenpill-commons · Community proposals PWA
- cookie-jar · Smart-contract-governed funding pools (allowlist, NFT, POAP, Hypercert, and Hats gating)
Contribution flows through scoped project work. Some work is volunteer open-source contribution; paid work depends on active grants, sponsors, or steward-approved budgets.
- Start with a project issue, proposal, or maintainer-scoped work item.
- Confirm deliverables, acceptance criteria, and review path before implementation.
- Know how it pays: guild members claim a monthly stipend against work tracked and accepted on Linear — see the compensation playbook.
- Submit a PR or design artifact linked to the agreed scope.
- Review for quality, scope, tests, and project fit.
Our working cadence is a weekly public call, monthly Twitter/X Spaces and/or forum updates, quarterly overviews, and regular workshops on Hypercerts, EAS, and other regen primitives.
Full contributor flow: CONTRIBUTING.md. Guild-wide playbooks: routines/.
Funded by: GitHub Sponsors · Gitcoin · Giveth · Octant.
We fund: regenerative projects across gaming and public goods through Grant Ships rounds, Gitcoin community rounds (including the GreenPill x Octant round), and clearly scoped grant-dependent work. Contributor compensation runs through a monthly Cookie Jar stipend backed by Linear-tracked work.
| You are... | Start here |
|---|---|
| A developer or designer wanting to ship regen tools | Join Telegram · Discord · read CONTRIBUTING.md |
| A partner building regen infrastructure | Read PARTNERS.md · email contact@greenpill.builders |
| A funder or sponsor | See our funding profiles |
| A chapter or community wanting tools | Open an issue on the relevant project repo |
Guild operations are stewarded by a stewardship team that handles Code of Conduct enforcement, governance, and treasury. See GOVERNANCE.md.
Project management and all accepted work run through Linear; GitHub is the public surface for code, pull requests, review, releases, and RFC/ADR markdown. See the Linear operating model.
| Channel | |
|---|---|
| General | contact@greenpill.builders |
| Stewards / governance | steward@greenpill.builders |
| Security / responsible disclosure | security@greenpill.builders |
All guild work is open-source. Code is MIT licensed unless otherwise noted. Read our Code of Conduct and Security Policy before contributing.