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: the flagship regen-documentation PWA is cutting its August v1.3.0 release, with the beta now a public surface people can be onboarded to and a QA pass running across the app and admin surfaces.
- Commitment Pooling: per-garden pools where a community names a need, members promise help, and the person helped confirms it — the contracts, shared API, and settlement path are built, and a second QA pass is running ahead of release.
- Community Needs & Signals: the community engagement model is settled and the attestation schemas are being consolidated, so a need-to-proof thread stays legible from request through confirmed help.
- Public Goods Staking (PGSP): the operator-first relaunch is refreshing node setups and building an operator base that practices on testnet before taking validator squads to mainnet.
- Greenpill Network website: polishing the public site and community map after June's launch, and onboarding stewards so the map and content stay accurate.
- Green Goods: tagged v1.2.1 — a recovery screen when the app shell fails to start, passkey sign-in on by default in production, open tabs preserved through service-worker updates, and post-deploy asset recovery. The Envio HyperIndex 3.2.1 migration also landed.
- Guild org repo: moved strategy into quarterly editions tracked alongside the work itself, and refreshed the shared routine playbooks — a quieter house style for automated updates and a model refresh across guild routines.
How work is organized: five teams — Product, Research, Community, Growth, and Marketing — tracked in Linear (how we run them). What each is on right now:
- Product — cutting the August v1.3.0 release while a second Commitment Pooling QA pass runs, after opening the beta as a public onboarding surface and clearing the first pooling QA pass.
- Research — reading an existing community-credit deployment before committing to voucher interoperability for Commitment Pooling, having just finished the community engagement model behind Needs & Signals.
- Community — onboarding the current cohort of pilot gardens and the first Commitment Pooling operators, alongside weekly gardener check-ins and an end-of-August activity push.
- Growth — running the Artizen Season 7 raise and reporting on active grant awards, after submitting the Season 6 impact report.
- Marketing — producing the Green Goods demo-video batch for the docs site, with a garden anatomy and roles explainer in review.
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.