Skip to content
web3grant

How to turn a hackathon project into a grant

Updated 8 min readBy the web3grant editors

To turn a hackathon project into a grant, treat the demo as evidence, not as the product. Clean up and license the code, get real users in the weeks after the event, scope the next two or three milestones, and apply to a program that funds prototypes, such as Starknet Seed Grants or 1inch DAO's Aqua incubator. Ask for the next step, not the whole roadmap.

Key takeaways

  • Some programs ask for exactly what a hackathon produces: Starknet Seed Grants want an MVP or proof of concept and favor teams from a past Starknet hackathon, and 1inch DAO's Aqua incubator welcomes hackathon teams with a proof of concept.
  • Others won't fund a demo at all: Aptos and Base require a live product with users, and Ink Spark says idea-only and testnet-only projects are unlikely to be funded.
  • Starknet asks for a plan for the next three months, which is a good default scope for a first grant after a hackathon.
  • 7 of the 100 programs in web3grant's directory cap grants at $10,000 or less, and 22 usually decide in 3 weeks or less, which suits a first grant.
  • Disclose your hackathon prize and any other funding; several programs, including RootstockCollective and VeBetter, require you to disclose other funding.

Is your hackathon project ready for a grant?

A hackathon project is ready for a grant when a reviewer can run it, see who would use it, and believe your team will still be working on it in three months. Judges reward an idea and a demo after a weekend. Grant reviewers pay for months of work, so they look for different things.

Hackathon judges rewardGrant reviewers look for
A clever ideaA problem with evidence that people have it
A demo that works onceCode that runs, in a public repository
A pitchMilestones with dates, amounts and checks
SpeedA team that will keep going

If you can't show the right-hand column yet, the next three to six weeks of work matter more than the application.

Step 1: Make the code fundable

Hackathon code is written to demo, not to last. Before you apply, fix what a reviewer will open first:

  • Make the repository public and write a README that says what works, what doesn't, and how to run it.
  • Remove secrets such as hardcoded keys, and replace mock data with real calls where the demo faked them.
  • Pick a license. Many programs require open source; Aleo, for example, requires open-source elements, and OpenSats requires all code to be free and open source. Our guide to open-source licenses for grants explains the choice.
  • Settle ownership. Agree in writing who on the team owns the code and who will apply. Grant agreements are signed by a person or an entity, and a teammate who left after the event can complicate that. A lawyer can tell you what applies in your country.
  • Read the hackathon's terms. Some events set rules on the code or prizes; check them before you build a grant on top.

Step 2: Prove traction after the event

A demo shows the idea works; traction shows someone wants it. In the weeks after the hackathon, collect evidence a reviewer can verify:

  • Deploy it. Move from a local demo to testnet, and to mainnet if the program asks for a live product.
  • Find first users. Ten real users with feedback beat a thousand page views. Write down what they said.
  • Measure. Transactions, active wallets, integrations or downloads, with a link to where the numbers come from. Ink Spark, for instance, asks that claims about users, volume or TVL be backed by data reviewers can verify.
  • Keep the judges' feedback. Comments from hackathon judges or sponsor engineers are evidence that people who know the chain looked at your work.

Our guide to grant impact metrics covers which numbers reviewers trust.

Step 3: Scope the first milestones

Ask for the next step, not the whole roadmap. Starknet Seed Grants ask for a plan for how you will use the money over the next three months, and that is a sensible default for any first grant after a hackathon.

An illustrative plan for a fictional hackathon project, a wallet recovery tool:

MilestoneDeliverableHow a reviewer checks itWeeksAmount
1Audit-ready contracts with testsPublic repo, test coverage report4$6,000
2Testnet beta with 50 usersExplorer link, user list4$5,000
3Mainnet launch and docsDeployed address, docs site4$4,000

These figures are invented. Price your own milestones from the hours they take; our guides to milestone-based grants and Web3 grant budgets show how. 55 of the 100 programs in our directory pay in milestone tranches, so a plan like this is what most of them expect.

Step 4: Pick a program that funds early-stage work

Pick a program by what you have now. These programs in our directory accept work at the prototype stage:

What each one asks for, from our records:

  • Starknet Seed Grants: up to $25,000 in STRK for early-stage teams with an MVP or proof of concept that have not gone to market, active in the Starknet community or a past Starknet hackathon or builder program. The Seed Grants page lists the criteria.
  • Aqua Revenue Stream Incubator: up to $50,000 in USDC for new strategies on 1inch's Aqua; hackathon teams with a proof of concept are welcome, in exchange for a revenue share to the 1inch DAO.
  • Mina Builders Grants: Exploration Grants of $1,000 to $5,000 for early experiments and prototypes. o1Labs said in August 2025 it would run Mina grants for about 12 months, and that period has passed, so confirm in the Mina Discord first.
  • Team1 Builder Grants: mini grants of up to $10,000 for early-stage Avalanche builders and new ideas.
  • Tezos Commons Small Grants: small, fast grants for rapid prototypes, for applicants in the US and Canada, with a decision in about a week.
  • HTX DAO Genesis Grant: milestone grants in HTX that prioritize early-stage teams validating a prototype.
  • Stacks Endowment Grants: a Getting Started track of $2,500 to $10,000 in STX for teams with a prototype, technical spec or user research. The Q3 2026 cycle closed on September 23, and Q4 dates had not been announced as of November 15, 2026.

The Stellar Community Fund also offers Instawards of up to $15,000 to early-stage teams through local Stellar Ambassador chapters.

Programs to approach after launch, not before

Some programs say outright that a demo is not enough. Aptos Ecosystem Grants need a live product with evidence of users and point earlier teams to hackathons first. The Base Builder Grant Program wants you past the idea stage with a live product people use. Ink Spark says idea-only and testnet-only projects are unlikely to be funded. Apply to these once Step 2 has produced real usage.

RootstockCollective excludes hackathons from what it funds, meaning it won't pay for running one. A product that started at a hackathon can still apply once it is deployed or ready to deploy on Rootstock mainnet.

For more options, see small Web3 grants and fast Web3 grants.

Step 5: Write the application

Lead with what exists, then ask for the next step. A strong application after a hackathon has five parts:

  1. What works today, with links: repository, deployed contract, a two-minute demo video.
  2. What changed since the hackathon: users, fixes, the feedback you acted on.
  3. The problem and who has it, with the evidence from Step 2.
  4. The milestone plan from Step 3, with amounts.
  5. The team, including who has committed to the project for the grant's duration.

The difference in phrasing:

  • Weak (illustrative): "We won second place at a hackathon with our revolutionary recovery wallet and now want $80,000 to build the full platform."
  • Strong (illustrative): "We built a social recovery module at a Starknet hackathon in September. Since then, 37 testnet users have set up recovery, and two wallet teams asked to integrate it. We are asking for $15,000 over 12 weeks to finish tests, launch on mainnet and publish docs."

Our Web3 grant proposal template has a full structure, and how to write a Web3 grant proposal explains what reviewers score.

Common mistakes

  • Sending the hackathon pitch deck. Reviewers want milestones and evidence, not a pitch.
  • Asking for the whole vision. A first grant funds a scoped step; the rest comes after you deliver.
  • Hiding the prize. Say what you won and from whom, so the reviewer knows which work is already paid for.
  • Applying to the wrong chain. A grant from one ecosystem expects you to build there. If the hackathon was on another chain, explain why you are moving.
  • Waiting too long. Apply while the work and the feedback are recent; our guide to Web3 hackathons vs grants covers how the two fit together.

FAQ

Can you get a grant for a hackathon project still on testnet?

Yes, from some programs. Starknet Seed Grants fund early-stage teams with an MVP or proof of concept that have not gone to market, and 1inch DAO's Aqua incubator welcomes hackathon teams with a proof of concept. Others, such as Aptos Ecosystem Grants, Base Builder Grants and Ink Spark, want a live product with real users before they fund a hackathon project.

Should you disclose a hackathon prize in a grant application?

Yes. List any hackathon prize, its amount and who paid it, along with other funding. Several grant programs require it: RootstockCollective asks applicants to disclose other funding, VeBetter allows other funding only if you disclose it, and Tezos Commons asks whether you have sought money from other Tezos organizations for the same project. Disclosure also shows the reviewer which work is already paid for.

How soon after a hackathon should you apply for a grant?

Apply once you can show progress since the hackathon, typically within a few weeks: a public repository, a deployment and first users. Applying the day after the event gives reviewers nothing beyond the demo, and waiting months lets feedback and team commitment fade. Programs with rolling intake, which are 78 of the 100 in web3grant's directory, let you apply as soon as you are ready.

What if your hackathon team splits up?

Decide in writing who owns the hackathon code and who continues before anyone applies for a grant. A grant agreement is signed by a person or entity, and reviewers ask who will do the work. If only part of the hackathon team continues, say so in the application and show that the remaining team can deliver the milestones alone.

Programs in this guide

Where each one stands today, soonest deadline first.

Browse all grant programsGet deadline alerts