Open tools
Useful software, templates, systems, and resources that help Builders work more effectively.
Shenzhen Girl Handbook
Great communities do not only celebrate Builders. They create opportunities for Builders to keep building.
Talent can begin anywhere.Opportunity should be able to reach it.
Why Builder Grants Exist
Many Builders do not lack talent, discipline, or imagination. They lack time, tools, access, confidence, or a small amount of support at the right moment.
A useful idea may never become visible because its creator cannot afford to test it. A valuable guide may remain unwritten. A community program may never begin. A prototype may stop before anyone learns what it could become.
Builder Grants are designed to reduce that distance between intention and action.
The goal is not to reward speculation. The goal is to enable meaningful work.
Support should create progress,not dependency.
Every grant should help a Builder create, learn, contribute, and become more capable than before.
What We Support
The grant program should remain open to many kinds of useful work—not only software or Web3 development.
Useful software, templates, systems, and resources that help Builders work more effectively.
Guides, workshops, documentation, and learning materials that make knowledge easier to access.
Programs that strengthen participation, recognition, collaboration, and shared culture.
Small ideas worth testing before they are expected to become polished products.
Visual work, stories, media, design, and culture that help the movement express what it believes.
Builder-led events, workshops, and practical initiatives that create value in real communities.
Grant Principles
A proposal should be evaluated by its purpose, effort, usefulness, and integrity—not by how much attention it can generate.
Early ideas do not need to guarantee success. They need a clear question, a responsible plan, and a willingness to learn.
Builders should not need a large audience to deserve support. Visible contribution matters more than public influence.
Grant decisions, expectations, milestones, and outcomes should be documented clearly for the community.
Small grants reduce risk, encourage learning, and allow promising Builders to prove what they can create.
Supported work should create knowledge, tools, opportunities, or inspiration that helps others move forward too.
Grant Pathways
Micro Grant
For prototypes, local experiments, educational resources, community activities, and early validation.
Expected
Simple proposal, limited scope, short timeline, and a public outcome.
Builder Grant
For ideas that have already shown effort, traction, usefulness, or strong community relevance.
Expected
Clear milestones, regular updates, responsible ownership, and documented results.
Ecosystem Grant
For larger tools, infrastructure, programs, and partnerships that may serve many Builders.
Expected
Formal review, transparent discussion, staged funding, and greater accountability.
The Grant Process
The process should remain clear enough for a first-time applicant to understand and strong enough to protect community resources.
A Builder identifies a problem, opportunity, experiment, or contribution worth pursuing.
The idea is documented with its purpose, requested support, expected outcome, and basic timeline.
The proposal is checked for clarity, alignment, feasibility, conflicts, and community value.
When appropriate, the community can ask questions, offer feedback, and improve the proposal.
The responsible reviewers approve, revise, postpone, or decline the proposal with clear reasoning.
The Builder receives support and begins the work according to the agreed scope and milestones.
Progress, lessons, outcomes, and use of resources are shared openly through a public Build Log.
How Proposals Are Reviewed
Grant review should not become a contest for the most polished presentation. The purpose is to discover useful, responsible work.
Does the idea strengthen Builders, community culture, knowledge, products, or useful participation?
Can the Builder explain what they want to create, why it matters, and what support they need?
Can the proposal reasonably be completed with the requested resources and available time?
Will the result create value that extends beyond the individual receiving the grant?
Has the Builder shown consistency, honesty, and willingness to report progress openly?
Even if the experiment fails, can the community learn something useful from the process?
Transparency & Accountability
Approved grants should include a public description of the project, the support provided, the Builder responsible, and the expected milestones.
Progress updates should remain proportionate to the size of the grant. A small experiment should not require excessive administration, but no supported work should disappear without explanation.
Failure should not automatically be treated as misuse. Honest experiments can fail and still produce useful learning.
Silence, hidden spending, and repeated avoidance of responsibility are different.
What Builder Grants Are Not
No guaranteed funding for holding or promoting the token.
No payment for artificial engagement, spam, raids, or misleading promotion.
No grants based only on friendship, status, or access to leadership.
No hidden agreements or undisclosed conflicts of interest.
No unlimited funding without milestones and review.
No promise that every useful idea will receive support.
The Honest Beginning
The grant program will not begin with promises the community cannot yet sustain.
It should emerge from real ecosystem value, responsible treasury planning, transparent governance, and a community capable of reviewing work fairly.
We would rather begin small and honest than announce something large that cannot last.
The Builder Grant Promise
One Builder can change
a life.Thousands of Builders can
change the future.
Support the experiment. Share the lesson. Strengthen the Builder. Let the value travel forward.
Opportunity. Responsibility. Progress. Impact.
We Build Together.