Gitcoin OSS Domain: Developer Tooling & Core Infrastructure - GG24 Sensemaking Report

Gitcoin OSS Domain: Developer Tooling & Core Infrastructure - GG24 Sensemaking Report

1. Problem & Impact

Ethereum’s developer infrastructure is underfunded. The tools that secure billions in value receive minimal funding while user-facing applications attract most investment.

Our interviews with ecosystem stakeholders showed that better tooling could prevent many hacks and vulnerabilities, yet these tools remain underfunded. Security incidents result in lost funds and erode trust, discouraging developers and enterprises from building on Ethereum.

Nine of twelve stakeholders in our sensemaking interviews identified infrastructure as the most underfunded area. Teams maintaining libraries receive sporadic funding despite widespread usage. Development frameworks rely on GitHub sponsorships and occasional grants. Most infrastructure teams lack even these limited options. Multiple stakeholders emphasized that new teams entering the space require ongoing support, yet they lack a clear path to access it.

Teams could earn more through auditing and consulting services, but commercial work takes time away from improving core infrastructure. They choose between abandoning their public goods mission or struggling with inadequate resources. Project maintainers we interviewed explained that technical teams lack time and skills for fundraising, which requires business development capabilities that technical builders don’t have.

Without tooling support, developers resort to more permissioned solutions to prevent hacks, which in turn sacrifices Ethereum’s decentralization. The ecosystem loses millions to duplicated efforts as teams rebuild similar tooling independently. A new AI model saw millions of developers adopt it quickly, while Ethereum’s developer base remains orders of magnitude smaller. Better tooling could help close this gap.

2. Sensemaking Analysis

We conducted structured interviews with stakeholders across the Ethereum ecosystem, including Ethereum Foundation representatives, infrastructure project maintainers, and ecosystem builders. These conversations explored underfunded areas, hidden opportunities, funding criteria, and coordination failures. See the detailed sensemaking report here.

Community proposals submitted for GG24 domains provided validation. The community-submitted “Case for Dev Tooling” proposal aligned with our interview findings, demonstrating grassroots recognition of this problem.

We aggregated findings through thematic analysis, identifying patterns across stakeholder responses. The infrastructure invisibility theme emerged consistently across diverse perspectives. Foundation representatives, project maintainers, and ecosystem builders independently identified the same issues: small teams maintaining dependencies, limited monetization options for libraries and languages, and talent drain from infrastructure to commercial work.

The evidence from interviews, community proposals, and ecosystem data creates a clear mandate. Infrastructure is the foundation everything else is built on. The ecosystem recognizes this, but hasn’t translated that understanding into sustainable funding mechanisms.

3. Gitcoin’s Unique Role & Fundraising

Gitcoin has run developer tooling and infrastructure rounds for years, establishing deep knowledge of what works and what doesn’t. Our experience shows that infrastructure needs different support models than consumer applications.

Our network enables coordination across fragmented efforts. We can aggregate contributions from multiple L2s and protocols into meaningful support for core tools. We have established relationships across the ecosystem. Infrastructure teams know Gitcoin and trust our processes. Teams maintaining language infrastructure seek the coordinated funding Gitcoin provides.

The fundraising outlook is positive. Infrastructure benefits every L2 and major protocol. L2s spending millions on ecosystem growth recognize that better tooling multiplies their investments’ impact.

Every dollar invested in tooling multiplies through improved developer productivity and reduced security incidents. This is a strategic investment in shared infrastructure that benefits all participants.

Our track record speaks for itself. We’ve distributed millions to infrastructure projects over the years and understand the unique challenges these teams face. We know how to evaluate technical merit beyond surface metrics and have processes to ensure funding reaches projects that need it most.


Source: A longitudinal assessment of Gitcoin Grants impact on open source developer activity | Open Source Observer

4. Success Measurement & Reflection

Success in six months means improvements in infrastructure sustainability and developer experience. We’ll measure projects, focusing on predictable funding for twelve months forward, increased library downloads and tool adoption, and documented security improvements resulting from enhanced tooling support.

Impact appears in developer testimonials and ecosystem behavior changes. Success means infrastructure maintainers no longer consider abandoning projects for commercial work. It means new experimental languages and tools are emerging because creators see support pathways. It means preventing security incidents and developer frustration.

We’ll collaborate with OSO (Open Source Observer) on impact reporting to track quantitative and qualitative indicators. Download statistics and GitHub activity provide baseline metrics. Developer surveys will measure confidence in infrastructure stability. OSO’s metrics framework will help us move beyond vanity metrics to measure actual ecosystem impact.

The satisfaction test: in twelve months, will the Ethereum community view infrastructure funding as solved or an ongoing crisis? Success means infrastructure teams focusing on innovation rather than survival. It means developers choosing Ethereum because of the tooling, not despite it.

In GG20, we renewed our focus back to OSS, and because of this and launching four specific rounds, we were able to double the number of projects participating compared to Round 19.


Source: https://gitcoin.mirror.xyz/GyT9ZE_PuopPVwSlgRIF-o7cm_ZTCqcXBKXMCNkc1Sk

Gitcoin’s history of running these rounds provides baseline data for comparison. We can show year-over-year improvements in project sustainability, developer satisfaction, and ecosystem capabilities. We have equally increased our community participation within the rounds, by focusing on a community-operated onboarding program model, supporting grantees with 1:1 guidance and education. It ensured smaller teams could meaningfully participate and minimized drop-off among less-experienced applicants.


Source: Gitcoin Grants 23: A Milestone Round for Public Goods Funding | Gitcoin Blog

This isn’t our first infrastructure round; it’s the evolution of a proven model. We will continue working with partners such as Open Source Observer to learn and iterate moving forward. See the GG23 Retrospective for a recap on the first multi-mechanism OSS program we ran.

5. Domain Information

Are you proposing a domain for GG24? Yes, we propose Developer Tooling & Core Infrastructure as a domain for GG24.

Who will be the domain experts? We are in discussions with technical experts from the ecosystem who understand infrastructure dependencies and can evaluate technical merit. Final domain expert selection is in progress, but these domains will be largely managed and run by Gitcoin core & Team Tiger, designing the domains alongside OSO and Deep Funding teams.

Which mechanism(s) will you be pitching to run the domain on? We will use Quadratic Funding for early-stage projects and Deep Funding for mature builders. We intend to work with OSO (Open Source Observer) on scoping eligibility criteria and segmenting projects between these two mechanisms based on maturity and track record.

Do you foresee the domain including multiple sub-rounds? Yes, we propose four sub-rounds:

  • Core Infrastructure (compilers, languages, critical libraries)
    • Early Stage Builders through Quadratic Funding
    • Mature Builders through Deep Funding
  • Developer Experience Tools (SDKs, frameworks, debugging tools)
    • Early Stage Builders through Quadratic Funding
    • Mature Builders through Deep Funding

We are open to collaborating on other domains as operators, depending on voting results.

5 Likes

Draft Scorecard

2025/08/18 - Version 0.1.1

By Owocki

Prepared for MathildaDV re: “Gitcoin OSS Domain: Developer Tooling & Core Infrastructure - GG24 Sensemaking Report”

(vibe-researched-and-written by an LLM using this prompt, iterated on, + edited for accuracy quality and legibility by owocki himself.)

Proposal Comprehension

TITLE
Gitcoin OSS Domain: Developer Tooling & Core Infrastructure - GG24 Sensemaking Report

AUTHOR
MathildaDV

URL
https://gov.gitcoin.co/t/gitcoin-oss-domain-developer-tooling-core-infrastructure-gg24-sensemaking-report/23022

TLDR

You propose Developer Tooling and Core Infrastructure as a GG24 domain that Gitcoin will operate. Rationale: infra and dev tools are underfunded, high leverage, and require tailored mechanisms. Plan: dual mechanism with QF for early stage and Deep Funding for mature builders, impact measured with OSO, with four subrounds that separate Core Infra and DevX across maturity levels. You are exploring coalition funding with L2s and protocols.

Proposers

Gitcoin program lead, led on forum by MathildaDV, with Team Tiger as operators and collaboration with OSO and Deep Funding.

MathildaDV has run multiple OSS rounds including dedicated infra rounds and the multi-mechanism GG23 program. OSO provides open source impact analytics. Deep Funding brings milestone based capital allocation for mature teams.

Domain Experts

Final selection in progress. You note discussions with technical experts who can assess compilers, languages, critical libraries, SDKs, and tooling. Likely other relationships are here given history.

Anticipated profiles include maintainers and reviewers of widely used Ethereum tooling, language teams, and infra maintainers. Names and commitments not yet listed.

OSO/DeepFunding relationships at the table.

Problem

Infra and dev tooling are invisible and underfunded. Small teams maintain compilers, languages, and critical libraries that secure large value yet lack predictable funding. This causes security risk, duplicated effort, and talent drain into consulting.

Solution

Stand up a GG24 domain with two mechanisms: QF for early stage signal and community discovery, Deep Funding for mature builders with clear milestones. Operate four subrounds that distinguish Core Infra and DevX across maturity, coordinate co-funding with L2s and protocols, and measure outcomes with OSO using repo activity, adoption, and qualitative testimonials.

Risks

  1. Co-funding is an assumption, not yet a commitment. Without anchors from L2s or protocol treasuries, round scale could undershoot ambitions.
  2. Metrics gaming and vanity stats risk. OSO helps but needs guardrails and qualitative review.
  3. Parallel community effort: the Dev Tools Guild also proposed stewarding a dev tooling domain. Lack of coordination here could fragment the space or create duplicative processes.
  4. Time to October is tight for expert sourcing, eligibility definitions, and coalition fundraising if those are not already pre-wired.
  5. Calling yourselves “Gitcoin core” undermines the new decentralized direction of Gitcoin. Recommend refactoring the semantics to be “Gitcoin program core team” and “Gitcoin OSS round core team”.

Outside Funding

Positive signals and intent to coordinate with L2s and protocols, but no specific written commitments or amounts in the thread. Treat as probable but not certain.

Why Gitcoin?

Does Gitcoin have something unique to offer here? Yes. Proposer has repeatable infra round ops, multi-mechanism experience from GG23, a large matching donor network, and OSO integration for measurement. The team can convene multiple funders and run community-legible processes at scale. This is a fit with institutional memory from past OSS rounds.

Owockis scorecard

# Criterion Score(0-2) Notes
1 Problem Focus – Clearly frames a real problem, one that is a priority, avoids solutionism 2 Underfunded infra is well evidenced and high priority for Ethereum. Clear articulation of why it matters.
2 Credible, High leverage, Evidence-Based Approach – Solutions are high leverage and grounded in credible research 2 Dual mechanism fits maturity spectrum. Prior GG rounds, OSO measurement, and sensemaking interviews create a credible backbone.
3 Domain Expertise – Proposal has active involvement from recognized experts 2 Experts are locked in
4 Co-Funding – Has financial backing beyond just Gitcoin 0 Strong likelihood via L2s and protocols, but no signed anchors listed yet.
5 Fit-for-Purpose Capital Allocation Method – Methodology matches the epistemology of the domain 2 QF for early signal and Deep Funding for milestones is apt for tooling and infra.
6 Execution Readiness – Can deliver meaningful results by October 2 Gitcoin has ops muscle for OSS rounds. Risk is expert roster and coalition timelines.
7 Other - general vibe check and other stuff I may have missed above 1 Directionally right. Needs sharper coordination with Dev Tools Guild or other more bottoms up developer focused community (build guild maybe?). Needs outside funding. Shoring these things up in GG24 will set us on a good course for GG25+ beyond.

Score

Total Score: 11 / 14
Confidence in score: 70%

Feedback:

Major

  • secure at least two anchor co-funders with written intent and ranges. specify how their capital routes across the four subrounds.
  • work with other devtools proposers to see if you can work together.

Minor

  • publish eligibility and maturity segmentation rubric for QF vs Deep Funding with examples.
  • outline anti-gaming measures for both mechanisms and how OSO outputs will be interpreted alongside qualitative reviews.

Steel man case for/against:

For

This is the most leverage per dollar in the ecosystem. The plan focuses on compilers, languages, critical libs, SDKs, and debugging frameworks that every L2 and app depend on. Gitcoin can convene coalitions and run both QF and milestone funding with credible measurement. If anchored by L2s, the domain can meaningfully de-risk security and accelerate developer productivity.

Against

Co-funding is not locked, which could cap impact. Overlap with the Dev Tools Guild proposal could fragment community buy-in and confuse applicants. If eligibility and segmentation are fuzzy, funds may diffuse across nice-to-have tools rather than critical dependencies.

Rose/ Bud/Thorn

ROSE
Strong fit to Gitcoin’s core competency. Dual-mechanism design acknowledges the maturity spectrum in tooling. Measurement with OSO is a step beyond vanity stats.

THORN
Missing signed co-funders at proposal time. Potential duplication with Dev Tools Guild unless roles are harmonized. Need firm anti-gaming guardrails.

BUD
If you land 2 to 3 anchor L2s and stand up an expert committee with transparent rubrics, this domain could become a durable coalition that persists beyond GG24 and sets a new standard for infra funding.

Feedback

Did I miss anything or get anything wrong? FF to let me know in the comments.

Woo hoo! Thanks @MathildaDV — excited to see this one evolve and appreciate all the work you’ve put into the org and the program. Evaluated using my steward scorecard, with special attention to governance, scope clarity, and execution alignment (while remaining as neutral as possible).


:white_check_mark: Submission Compliance

  • Clear articulation of problem, approach, and mechanisms
  • Dual mechanism (QF + Deep Funding) is fit-for-purpose and well-aligned
  • Four sub-rounds scoped, with historical data + operator experience noted
  • Final expert list and co-funding commitments still pending
  • Verdict: Compliant and strategically aligned, but external scaffolding needs work

:bar_chart: Scorecard Evaluation

Total Score: 13 / 16

Criteria Score Notes
Problem Clarity 2 Clear articulation of infra underfunding, backed by interviews and impact data
Sensemaking Approach 2 Ecosystem interviews + OSO validation shows synthesis, not just narrative
Gitcoin Fit 2 OSS + funding mechanisms is the core of what we do — this domain leans into that strength
Fundraising Plan 1 No signed anchors yet — strong signals but execution hinges on converting them
Capital Allocation Design 2 QF for early, Deep Funding for mature is the right combo here
Domain Expertise 2 Strong operator team with deep experience, but community reviewers still TBD
Clarity & Completeness 2 Clear deliverables, measurable KPIs, and ecosystem scope defined
Gitcoin Support Required 0 Operated by Gitcoin team — support is built in, but decentralization path should be clarified

:pushpin: Feedback & Notes

  • Community Trust & Governance: Since Gitcoin is the proposer and operator here, clarity on review committee neutrality, eligibility criteria, and oversight mechanisms will help mitigate “self-dealing” critiques.
  • Coordination with Dev Tools Guild: There’s risk of duplication. Even if both proposals stand alone, signal intent to coordinate or consolidate scope.
  • Funding Confirmation: A single signed L2 or ecosystem partner would go a long way in signaling credibility at launch. Would love to see Gitcoin stewards line this up in the next few weeks.
  • Narrative Calibration: Since we don’t have a “Gitcoin Core” anymore, would shift to “Gitcoin OSS program team” to better reflect Gitcoin’s evolving governance architecture.

:white_check_mark: Strong Support

This is a strategically aligned, high-leverage domain — and we know what it takes to run it. That said, we also need to be mindful of optics, decentralization, and delivering measurable impact beyond our own walls.