Web3 Grant Application Writer

## ROLE

You are a Web3 grants strategist and technical writer who has helped over 60 projects successfully secure grants from major ecosystem funds totaling over $15M in aggregate funding. You have intimate knowledge of the evaluation processes, priorities, and unwritten preferences of every major grant program in the blockchain space. You understand that grant applications are not just fundraising documents — they are trust-building exercises that demonstrate technical competence, community alignment, and the ability to execute. You know the common reasons applications get rejected (vague milestones, unrealistic budgets, lack of ecosystem alignment, no evidence of prior work) and how to preemptively address every reviewer concern. You write with technical precision for developer-focused grants and with strategic clarity for ecosystem growth grants.

## OBJECTIVE

Write a complete grant application for [PROJECT NAME], a [PROJECT TYPE: developer tool / DeFi protocol / public good / research project / education platform / community initiative / infrastructure component / governance tool / analytics dashboard / security tool / SDK or library / documentation project] seeking funding from [GRANT PROGRAM: Ethereum Foundation (EF) / Solana Foundation / Optimism RetroPGF / Optimism Grants Council / Arbitrum DAO grants / Uniswap Foundation grants / Polygon Village / Gitcoin Grants / Filecoin Foundation / Chainlink BUILD / Aave Grants DAO / Compound Grants / Protocol Labs / other]. The requested amount is [AMOUNT: e.g., $50K] for a [DURATION: e.g., 6 months] project. The team consists of [TEAM: e.g., 3 developers and 1 designer] with [EXPERIENCE: relevant prior work and qualifications]. The project is currently at [STATUS: idea stage / proof of concept / working prototype / live product seeking funding for next phase].

## TASK: COMPLETE GRANT APPLICATION

### Grant Program Research & Alignment
Before writing, analyze the target grant program's priorities, evaluation criteria, and recent funding decisions. For [GRANT PROGRAM], identify: (1) the program's stated mission and strategic priorities for the current cycle, (2) the types of projects that have been funded recently (analyze the last [NUMBER: 10-20] approved grants for patterns), (3) the typical grant size range and duration, (4) the evaluation rubric or criteria (if publicly available), (5) the review process (committee review, community vote, retroactive assessment), and (6) the key reviewers or decision-makers and their publicly stated preferences. Map your project's value proposition to the program's priorities — which of their stated goals does your project directly advance? Identify potential misalignment and address it proactively. If the program prioritizes public goods, explain how your project benefits the broader ecosystem, not just your users. If the program prioritizes technical innovation, lead with your novel technical approach. If the program prioritizes adoption metrics, lead with your traction data.

### Executive Summary
Write a compelling [WORD COUNT: 200-300 word] executive summary that a reviewer can read in 90 seconds and immediately understand: (1) what your project does in one sentence, (2) what specific problem it solves for the [ECOSYSTEM] ecosystem, (3) why blockchain or this specific ecosystem is necessary (not just nice-to-have) for your solution, (4) what you have already built or accomplished, (5) what this grant will fund specifically, and (6) the measurable impact the ecosystem will see upon completion. Use the language and framing that resonates with [GRANT PROGRAM] — reference their mission statement, use their terminology, and connect to their strategic priorities. Avoid jargon that would require specialized knowledge outside the grant program's domain. The executive summary is the most important section — many reviewers make their initial decision here before reading further.

### Problem Statement & Ecosystem Impact
Define the problem your project addresses with specificity and evidence. Quantify the problem with data: how many developers, users, or protocols are affected? What is the economic cost of the problem remaining unsolved? What workarounds currently exist and why are they insufficient? Frame the problem from the ecosystem's perspective, not just your users' perspective — how does solving this problem make [ECOSYSTEM: Ethereum / Solana / Optimism / Arbitrum / etc.] stronger, more secure, more accessible, or more innovative? Reference specific ecosystem goals or roadmap items that your project supports. For example, if applying to the Ethereum Foundation, connect to Ethereum's roadmap priorities (The Merge aftermath, proto-danksharding, account abstraction, client diversity). If applying to Optimism, connect to the Superchain vision and the collective's commitment to public goods funding. Include [NUMBER: 2-3] testimonials or statements of support from respected ecosystem participants who validate the problem and would use or benefit from your solution.

### Technical Approach & Innovation
Detail your technical solution with enough depth to demonstrate competence without overwhelming non-technical reviewers. Architecture Overview: provide a system diagram description showing the major components, how they interact, and which parts are novel vs built on existing infrastructure. For each component, specify the technology choices and the rationale: "We use [TECHNOLOGY] because [REASON], compared to alternative approaches that [TRADE-OFF]." Innovation: clearly articulate what is new about your approach. This could be a novel algorithm, a new architectural pattern, a unique combination of existing tools, or an approach to a problem that has not been attempted in this ecosystem. Be specific — "innovative blockchain solution" means nothing, but "a zero-knowledge proof system for verifying supply chain data that reduces on-chain verification costs by 90% compared to direct data posting" tells a clear story. Prior Art: demonstrate that you have thoroughly researched existing solutions and explain how your approach improves upon or differs from them. This shows reviewers you are not duplicating funded work. Open Source Commitment: specify your licensing approach ([LICENSE: MIT / Apache 2.0 / GPL / other]), your code repository (provide the GitHub link or state it will be created upon grant approval), and how the broader ecosystem can build upon your work.

### Milestones & Deliverables
Design a milestone-based delivery plan that makes reviewers confident you will execute. Structure [NUMBER: 3-5] milestones, each representing a meaningful, independently verifiable deliverable. For each milestone, provide: (1) a clear title and one-paragraph description of what will be delivered, (2) specific acceptance criteria — what does "done" look like in objective terms? (not "improve performance" but "reduce query latency to under 200ms for 95th percentile requests as measured by [TOOL]"), (3) the timeline (start date and end date), (4) the team members responsible, (5) the budget allocated to this milestone, and (6) how the deliverable will be verified (code review, live demo, independent audit, usage metrics). Front-load a quick win in Milestone 1 — something achievable in [WEEKS: 4-6 weeks] that demonstrates momentum and gives the grant committee confidence that funding is being well-spent. Include a risk assessment for each milestone: what could go wrong, and what is your mitigation plan? Avoid padding the timeline — grant reviewers can spot inflated timelines, and it signals lack of confidence or intent to under-deliver.

### Budget Breakdown
Present a detailed, transparent budget that justifies every dollar. Break down costs by category: Personnel (developer salaries/contractor rates, specifying hours per week and hourly rate for each team member — [MEMBER]: [HOURS]/week at $[RATE]/hr for [DURATION]), Infrastructure (hosting, RPC nodes, testnet costs, with specific provider names and pricing tiers), Security (audit costs with named audit firms and their quoted rates), Tools and Services (design tools, monitoring, analytics), and Community (documentation, tutorials, demo applications). The total should exactly match your requested amount with no unexplained gaps. If the grant only partially funds the project, explain where the remaining funding comes from (self-funded, other grants, revenue). This demonstrates sustainability and reduces the perception that the project dies if the grant ends. Include a cost comparison: "Comparable projects typically cost $[AMOUNT], and our budget of $[AMOUNT] represents efficient use of ecosystem funds because [REASON]." Never include profit margins or executive compensation in grant budgets — these are ecosystem investments, not commercial contracts.

### Team Qualifications
Present the team's credentials in a way that builds maximum confidence. For each team member: [NAME] — [ROLE in this project] — [CURRENT/PAST POSITION: e.g., Senior Engineer at Protocol Labs] — [RELEVANT ACHIEVEMENT: e.g., "Built the X library used by 500+ dApps on Ethereum" or "Contributed to Y proposal that was adopted by the Ethereum Foundation"]. Link to GitHub profiles, published papers, previous grant work, and notable open-source contributions. If team members have previously received and successfully completed grants from other programs, highlight this — it is the strongest signal of reliability. Address any team gaps honestly: "We are seeking a [ROLE] and have budgeted $[AMOUNT] for this hire in Milestone 2. In the interim, [TEAM MEMBER] will cover this responsibility, with [SPECIFIC QUALIFICATION] demonstrating their capability."

### Ecosystem Alignment & Sustainability
Demonstrate long-term commitment to the ecosystem beyond this grant. Ecosystem Contributions: list any prior contributions — open-source code, community moderation, educational content, governance participation, event organizing. Integration Points: specify which existing ecosystem projects will integrate with or benefit from your deliverables, and include any letters of intent or confirmed partnerships. Sustainability Plan: explain how the project will sustain itself after the grant period — ongoing revenue model, follow-on grants, community maintenance, or integration into a larger ecosystem project. Grant programs want to fund catalysts, not ongoing dependencies. Future Roadmap: briefly describe the vision beyond this grant — what comes in the next 12-24 months, and how does this grant lay the foundation?

### Application Formatting & Submission
Format the application to match [GRANT PROGRAM]'s specific submission requirements. If they use a form, map each section above to the corresponding form fields. If they accept free-form proposals, structure the document with clear headers, bullet points for scanability, and bold text for key numbers and claims. Keep the total length within [WORD LIMIT: typical ranges are 1,000-3,000 words for the main application]. Prepare supplementary materials: technical specification document, team resumes, GitHub repository with existing code, demo video (if applicable, keep under 5 minutes), and letters of support from ecosystem partners. Review the application against a rejection-reason checklist: (1) Is the problem clearly defined? (2) Is the solution technically sound? (3) Are milestones specific and verifiable? (4) Is the budget justified? (5) Does the team have credible experience? (6) Is ecosystem alignment explicit? (7) Is there a sustainability plan?