Web3 Grants and Developer Funding: How It Works in 2026

Web3 grants are non-dilutive funding given to developers, researchers and teams who build software, infrastructure or knowledge for blockchain networks. Non-dilutive means the funder does not take equity in your company. Payment usually arrives in stablecoins, the network's native token, or a mix of both, and it is tied to a deliverable such as open-source code, a developer tool, documentation, a security review or a piece of research.

Why grants exist. Public blockchains behave like shared infrastructure. Foundations and DAOs often hold treasuries created through token issuance, and they want developers to build wallets, libraries, applications and educational material, because a network is only as useful as what runs on it. Many of the most important pieces of the ecosystem, including client software, standards, indexers and testing tools, are public goods. They are hard to monetise directly, so grants fill the gap that ordinary markets leave.

What grants are not. A grant is not a salary, a guaranteed income or an investment with an expected return. Most programs receive more applications than they can fund, and the money is normally restricted to the work you proposed. Many programs also expect public progress updates, and some may stop payments if milestones are missed.

Who they suit.

• Solo developers and small teams building prototypes
• Open-source maintainers whose tools others depend on
• Researchers working on protocol design, security or economics
• Early-stage startups that need to reach a first working version

Grants suit projects less well when they need large operating budgets, sales teams or heavy marketing spend. Those cases usually point toward venture funding or revenue instead.

Funding comes from several kinds of organisation, and each has different goals, speed and expectations. Knowing which type you are approaching shapes how you write the application.

Funder type	Typical motivation	What they usually prefer
Chain or network foundations	Grow the ecosystem and developer base	Tools, infrastructure, apps that deploy on their network
Protocol DAOs	Improve or extend a specific protocol	Integrations, front ends, analytics, security work
Public goods funders	Support shared, open resources	Open-source libraries, education, research
Hackathon organisers and sponsors	Attract prototypes and talent	Working demos built in a short window
Corporate and protocol-lab programs	Strategic technology development	Projects aligned with a roadmap
Community pools and quadratic rounds	Let a crowd decide what matters	Projects with visible community support

Foundations tend to run formal programs with published categories, review committees and written agreements. DAOs make decisions through governance: proposals are posted publicly, discussed in a forum, and sometimes voted on by token holders or delegates. This process is transparent but can be slow, and your proposal will be read by strangers with strong opinions.

Hackathons are the fastest entry point. A weekend event can produce prize money and sometimes a follow-on grant invitation. They are useful for building a track record before applying to larger programs.

Community-driven rounds reward projects with broad support, so building an audience can matter as much as the technical quality of your work.

Before applying, find out who actually controls the money, how decisions are made, and what the funder gets in return. Programs change names, budgets and rules often, so always confirm the current state on the official page or governance forum.

Grant programs differ mainly in how and when they pay. Understanding the model tells you how much risk you carry.

Milestone-based grants. The most common structure. You propose deliverables with dates, and funds are released in tranches as each milestone is reviewed. This protects the funder and gives you a plan, but it means you may need to cover costs before the next payment arrives.

Retroactive funding. Instead of paying up front, the funder rewards work that has already proven useful. The idea is that impact is easier to judge after the fact than to predict. Optimism's Retroactive Public Goods Funding is the best-known example. The downside is obvious: you have to build first with no guarantee of payment.

Quadratic funding. Popularised by Gitcoin Grants. Many small donations are combined with a matching pool, and the formula favours projects with many contributors over projects with a few large donors. Results depend on the number of supporters you can reach and on anti-sybil checks, which try to stop fake accounts from gaming the match.

Bounties. A specific task, such as fixing a bug or building an integration, is posted with a fixed reward. Whoever completes it to the stated standard is paid. Bounties are low commitment but also low certainty.

Hackathon prizes. Cash or token awards for the best entries at a time-limited event, sometimes with follow-up grants for strong projects.

Convertible or hybrid grants. Funding that may convert into equity or tokens, or that comes alongside an investment option. Read these terms carefully, since they behave more like early investment than a gift.

Most developers combine models over time: a hackathon prize, then a small milestone grant, then a larger program once there is usage to show.

Many programs exist, and their rules change, so treat this as a map of well-established names rather than a current directory. Check each program's official page for whether it is open, what it funds and how much it offers.

• Ethereum Foundation Ecosystem Support Program. Supports projects that benefit the Ethereum ecosystem, including tooling, research and education, with a mix of open and targeted calls.
• Gitcoin Grants. A recurring quadratic funding platform for open-source and public goods work, run in rounds with different themes.
• Optimism Retroactive Public Goods Funding. Rewards contributions that benefited the Optimism ecosystem, funded from a dedicated allocation and distributed in rounds whose rules have changed over time.
• Arbitrum DAO grant programs. Funding for builders and contributors on Arbitrum, operated through DAO governance and delegated program managers.
• Uniswap Foundation grants. Support for work connected to the Uniswap protocol and its wider community.
• Aave Grants DAO. Funds developers and contributors building around the Aave protocol.
• Solana Foundation grants. Support for projects building on Solana, with a focus on infrastructure, tooling and public goods.
• Web3 Foundation Grants Program. Funds open-source work on the Polkadot ecosystem and related technology.
• Filecoin and Protocol Labs ecosystem programs. Support for storage, data and decentralised infrastructure projects.
• ETHGlobal hackathons. Not a grant program itself, but a frequent source of prizes and sponsor-backed follow-up funding.

Beyond these, most large chains and many DeFi protocols run their own programs. Smaller programs sometimes have less competition and faster decisions, which can make them a better first step.

The best match is usually the network or protocol you already build on, not the program with the largest headline budget. Funders want work that serves their users, so alignment matters more than ambition.

A practical process.

1. Define what you are building in two sentences: the problem, who uses it, and what exists today.
2. List the ecosystems where your project runs or could run. A project that needs a specific chain's features has a natural case there.
3. Read each program's scope. Look at funded categories, excluded categories and past grantees. Past grantees show what reviewers actually approve.
4. Check the status. Many programs open and close in rounds, pause, or change structure. Confirm on the official site, governance forum or community channels.
5. Match size to stage. Early prototypes suit small grants and hackathons. Projects with users and a roadmap can aim for larger programs.
6. Note the requirements: open-source licensing, legal entity, identity checks, reporting duties and payout currency.

Consider product category too. SocialFi, wallets and account tooling are often funded when they bring new users on-chain or simplify onboarding. For example, Tomo is a social wallet offered as a Telegram bot, app, browser extension and developer SDK, and it is tracked under SocialFi on Linea. Developers building on or integrating tools like this may find that chain-level programs for the network involved are a sensible place to start looking, since those programs often favour user-facing infrastructure. Whether any specific program funds a given integration is something to confirm directly with that program.

Keep a simple spreadsheet of programs, deadlines, requirements and outcomes. It saves time and helps you reuse material across applications.

Reviewers read many proposals, often as volunteers or small teams, so clarity beats polish. A strong application is short, specific and easy to evaluate.

Core elements.

• Problem and users. Say who has the problem and how they handle it now. Avoid broad claims about changing an industry.
• Solution and scope. Describe exactly what you will build, and what you will not. Narrow scope reads as realistic.
• Team and track record. Link work you have already shipped, name relevant experience, and be honest about gaps.
• Milestones. Break work into dated deliverables that a reviewer can verify, such as a deployed contract, a published repository, documentation or a test report.
• Budget. Show how the request maps to hours, tools, audits or infrastructure. A clear breakdown builds trust.
• Impact measures. Explain how the ecosystem will benefit and how you will measure it, without inventing projections you cannot support.
• Licensing and openness. Many programs expect open-source code. State your license plainly.

Habits that help.

1. Read the program's guidelines and follow its template exactly.
2. Talk to the program team or community before applying, if they allow it.
3. For DAO proposals, post a draft in the forum first and respond to feedback.
4. Show something working, even a rough demo.
5. Ask for a modest first grant and plan to earn a larger one.

Common reasons for rejection. Vague deliverables, no clear user, a budget that doesn't match the scope, duplicating existing tools without explaining why, and a project that is mainly a token launch dressed up as development.

Receiving funding creates practical obligations, and they are easier to handle if you plan them before you apply.

Payout currency. Grants may be paid in stablecoins, a native token or both. Token-denominated grants carry price risk: the amount you receive may be worth much more or less by the time you pay bills. Some programs set the value at approval, others at payment. Ask which applies and whether there are vesting or lock-up terms.

Tax treatment. Rules differ by country and by how the grant is structured. In many jurisdictions, grant funding counts as taxable income at the value on the date received, and later price movement on tokens you hold can create separate gains or losses. Keep dated records of every payment, the wallet it arrived in and its value in your local currency. A qualified tax adviser who understands crypto is worth the cost.

Agreements and identity checks. Larger programs may require a signed agreement, a legal entity, or know-your-customer and sanctions checks before paying. Provide accurate information. Misrepresenting your identity or location can lead to cancellation and recovery of funds.

Intellectual property and obligations. Read who owns the code, what license is required, and whether the funder gets any rights, branding or reporting duties. Clarify what happens if you miss a milestone or abandon the project.

Wallet and treasury hygiene. Use a dedicated wallet for grant funds, and consider a multi-signature wallet for team projects. Separate personal and project finances from the start.

This is general information, not legal or tax advice.

Grants are one of several ways to fund web3 work, and they trade off differently against the alternatives.

Option	What you give up	Strengths	Trade-offs
Grant	Usually nothing, apart from deliverables and reporting	No equity, community goodwill	Small amounts, restricted use, uncertain approval
Venture funding	Equity, sometimes tokens	Larger sums, advice and networks	Dilution, growth pressure, long process
Revenue	Nothing	Independence	Needs a product people pay for
Retroactive rewards	Time spent unpaid	Rewards proven impact	No guarantee, delayed cash
Token sale or airdrop	Governance, regulatory exposure	Can fund and distribute ownership	Legal complexity, market risk

When a grant fits. The work is open source, useful to a specific ecosystem, and does not need a large team. Early research and developer tooling are classic cases.

When venture capital fits. You are building a company with a product that can scale and capture value, and you need more money than grant programs usually offer.

When to combine. Many teams use a grant to reach a first working version, then raise capital using that traction. Grant funders generally accept this, but disclose it and check that the grant terms don't restrict later fundraising.

A caution about tokens. Treating a token launch as a funding strategy brings legal, regulatory and reputational risks that differ by country. Seek professional advice before relying on it.

The right mix depends on what you are building, how fast you need to move and how much control you want to keep.

Grant programs attract scammers precisely because applicants are eager and sometimes inexperienced. Defensive habits protect both your funds and your reputation.

Warning signs.

• Someone contacts you first by direct message offering a grant you never applied for.
• You are asked to pay a fee, deposit or gas cost to receive funds.
• You are asked for a seed phrase or private key. No legitimate program needs either.
• You are told to connect your wallet to an unfamiliar site to claim a grant.
• The program has no verifiable governance forum, public past grantees or official channels.
• Pressure to act within hours.
• A shared file or link you must download to open the application.

Safer habits.

1. Reach program pages only through the foundation's or DAO's official website, and bookmark it.
2. Confirm announcements in more than one official channel.
3. Use a separate wallet with minimal funds for any signing or claiming.
4. Review every transaction and signature request before approving it.
5. Keep software and extensions updated, and avoid installing tools sent by strangers.
6. For payments, give only a public address. Never share private keys.

Integrity matters too. Do not inflate usage numbers, fake community support in quadratic rounds or submit the same work to multiple funders as if new. Programs share information, and sybil detection and public records make it easy to be caught. A damaged reputation can close doors across an entire ecosystem.

The grant does not end when the money arrives. How you handle delivery and communication affects future funding and your standing in the ecosystem.

During the grant.

• Work in public where the agreement allows it. Open repositories and regular commits make progress easy to verify.
• Post short updates at each milestone, covering what shipped, what changed and what is next.
• If you are going to miss a deadline, say so early and propose a revised plan. Funders generally respond better to honesty than to silence.
• Keep receipts and records for the budget you proposed.

After the grant.

1. Publish a closing report: deliverables completed, lessons learned and how people can use the work.
2. Document the project so others can maintain or fork it.
3. Track outcomes that matter, such as integrations, users or downstream projects, using sources you can cite.
4. Plan for sustainability. Options include follow-on grants, service contracts, sponsorship, a paid hosted version or fundraising.

Building a funding track record. Many programs favour applicants who have delivered before. A clean record of completed small grants is often the strongest credential for a larger one. Joining governance forums, answering questions and reviewing others' work builds visibility without asking for anything.

Where to check current details. Program budgets, open rounds, rules and eligibility change often. Confirm them on each funder's official website, governance forum and announcement channels, and treat third-party lists as a starting point only.