Matching Pool

A matching pool is the sponsor-contributed fund that gets distributed across projects in a quadratic funding round. Donors give directly to the projects they care about, and the matching pool layers on top: it allocates additional funding based on how broadly each project was supported.

The mechanism creates a multiplier. If a project is broadly supported, it receives far more from the matching pool than the sum of its direct donations would suggest. If a project is supported by only a few wallets, it receives less. This is how QF rewards community breadth.

Who Funds the Matching Pool

Matching pools are typically funded by:

• Foundations or DAOs with mandates to support public goods. Example: Optimism's RetroPGF rounds use OP treasury funds.
• Ecosystem funds with capital earmarked for specific domains. Example: TheDAO Security Fund's 500 ETH matching pool for the Ethereum Security QF round on Giveth.
• Project treasuries running community grants programs.
• Multi-sponsor pools where several entities contribute together for a specific round.

The common thread: the funders want the community to decide how their capital is allocated, rather than a traditional grants committee. The matching pool is the capital commitment; QF is the allocation mechanism.

How Distribution Works

At the end of a QF round, organizers calculate each project's matching allocation using the quadratic formula. The rough rule: sum the square roots of each donation a project received, then square the total, then normalize across all projects to the size of the matching pool.

The net effect:

• A project with 100 donors × $5 typically gets significantly more matching than a project with 5 donors × $100.
• Adding new unique donors to a project provides much more matching benefit than increasing the donation from existing donors.
• The matching pool is constrained to its total size — the formula is normalized so the total distributed never exceeds the sponsor's commitment.

Why Sponsors Use Matching Pools

For a sponsor, funding a matching pool is a way to outsource allocation decisions to the community without giving up control over which kinds of projects are in scope. Sponsors define eligibility (security, climate, open source) and seed the pool, but they do not pick winners. This is particularly valuable when:

• The sponsor has capital but not the domain expertise to evaluate every project.
• The sponsor wants the community to signal which projects are most valued.
• The sponsor wants to test a policy hypothesis (e.g., does amplifying expert voices improve outcomes?) as with the ETHSecurity Badge mechanism layered on the Ethereum Security round.

Matching Pool Limitations

Matching pools amplify whatever signal the donation pattern creates. They do not fix bad signals. If the community donates heavily to a project that is low-quality, the matching pool amplifies that too. Defenses include:

• Eligibility review to filter projects before the round.
• Sybil-resistance mechanisms like Gitcoin Passport to ensure donations come from real people.
• Badge or reputation systems that weight voices with demonstrated expertise.
• Statistical review of donation patterns during and after the round.

Even with these defenses, the matching pool is a market-like mechanism — it reflects the community's preferences at that moment, with all their strengths and blind spots.