Crypto Grants Programs Worth Applying To
Grants are the cheapest non-dilutive capital in crypto and the most misunderstood. Foundations do not fund good ideas — they fund work that removes a specific gap in their ecosystem, and the application is really a proposal to do their roadmap for them. This page groups the programme types, explains what reviewers weight, and sets out how to write a proposal that gets past the first screen.
Covered on this page (alphabetical, not ranked): Aave Grants DAO, Arbitrum Foundation Grants, Avalanche Multiverse, Base Builder Grants, Ethereum Foundation ESP, Gitcoin Grants, Optimism RetroPGF, Polygon Village, Solana Foundation Grants, Uniswap Foundation Grants.
We have not audited these organisations, we publish no scores or price tables, and no placement on this page is paid for.
How the options differ
- Foundation ecosystem grants. Fund infrastructure and public goods that the chain needs. Structured milestones, slow review, strong signalling value.
- Retroactive funding. Rewards work already shipped and demonstrably used. No application risk, but you must fund the build yourself first.
- Quadratic and community rounds. Matched by crowd contributions. Rewards distribution and community effort as much as the work itself.
- Growth and liquidity programmes. Incentives for bringing users or TVL to a chain. Not really grants — model them as performance marketing with token payment.
What to verify before you commit
- Read the last cohort's funded list. If nothing resembling your work has been funded, your proposal is educating the reviewer, which is a losing position.
- Map the milestone schedule to your actual runway. Most grants pay in arrears; a six-month schedule can be a cash-flow problem, not a solution.
- Check the token and tax treatment. Grants paid in the ecosystem token with a vesting schedule are not the same as cash.
- Confirm what rights you give up — licensing, open-source requirements, exclusivity to the chain.
- Find a reviewer or prior grantee to read your draft. Every programme has conventions that are invisible from the public docs.
Mistakes we see most often
- Writing about your product rather than about the ecosystem gap it closes.
- Proposing milestones you cannot evidence with a public artifact.
- Applying to eight programmes with one generic document.
What a grant is really buying on both sides
Ecosystems fund work that increases activity on their chain or fills a gap in their stack. That is the whole thesis, and applications that succeed are legible against it: here is the missing piece, here is why it is missing, here is what changes for other builders once it exists. Applications that fail are usually a product roadmap with a chain name pasted on top.
What you receive is rarely just money. The valuable parts are often the introductions, the ecosystem marketing surface, and the technical support channel — and those are the parts you should negotiate for explicitly, because they are not in the default template. What you give up is optionality: most programmes expect you to build on their chain first, and some expect exclusivity for a period. Read that clause before the amount.
Running the application like a small fundraise
Scope the smallest deliverable that is genuinely useful and can ship in a single milestone. Reviewers are choosing among many applications with limited attention, and a narrow, verifiable deliverable beats an ambitious one. Show prior shipped work, even if unrelated — evidence you finish things is the strongest signal you can send.
Then treat the milestones as commitments. Grant committees talk to each other, and a completed small grant is the best possible introduction to the next programme. Publish what you built, credit the programme, and send a short update when you ship even if nobody asked. That habit is why some teams keep getting funded and others get one grant and disappear from the list.
Want help choosing?
We take no kickbacks from anyone named on this page. Book a 30-minute vendor selection call and we will work through which option fits your stage, budget and ecosystem.
🔗 Related reading from the Metamoonshots Journal
FAQ
How long does a grant take?
Commonly six to twelve weeks from submission to first payment, longer for large amounts and committee-reviewed programmes. Never plan payroll around an unapproved grant.
Do grants hurt a future raise?
No — non-dilutive funding and an ecosystem endorsement generally help. Problems only arise if the grant terms include exclusivity or IP conditions you forgot to disclose in diligence.
What is the most common rejection reason?
A proposal that reads as funding for a company rather than delivery of a specific, verifiable artifact the ecosystem is missing.
Does taking a grant affect a later raise?
Generally it helps: non-dilutive funding plus a completed milestone is evidence of execution. Check the paperwork for anything that grants rights over future tokens or equity, which is unusual but not unheard of.
Can we apply to several ecosystems at once?
Yes, provided each application is genuinely scoped to that ecosystem and you disclose other funding when asked. Sending one identical application to five programmes is transparent to reviewers and gets rejected by all five.