Separate donors and coordinated anchors surround two funding pools
Original illustration for Identity Layer Review. Guide and sources checked October 21, 2026.

Summarize this page with

Quadratic funding needs to distinguish broad support from concentrated influence. One person splitting donations across many identities is a Sybil problem. Several real people coordinating support is a different problem: they may all pass personhood verification while remaining related participants. Donor eligibility, relationship analysis and the matching mechanism therefore need to work together.

  1. 1Distinguish identities
  2. 2Review coordination
  3. 3Finalize the match
A practical sequence for the question covered in this guide.

Why donor count matters

Quadratic funding rewards support spread across contributors rather than only the largest total donation. That creates an incentive to make one source of support appear broader than it is. The operational goal is to preserve legitimate participation while preventing the matching pool from rewarding fabricated independence.

A program should state which participants and contributions qualify before it accepts donations. Decide how organizational donors, shared treasuries, sponsored gas and related project teams are treated. The matching policy is not automatically determined by a device score or a wallet credential.

Gitcoin’s historical research on attack and defense distinguishes identity splitting from collusion among real contributors. Its examples explain the mechanism’s incentive problem; they should not be read as a current list of Gitcoin’s verification providers or round settings.

Separate three kinds of relationship

Comparison of the methods and conditions discussed in this section.
Situation Question to investigate Inadequate shortcut
One person, many donor identities Are multiple entries claiming one participant’s entitlement? Counting wallets as independent people
Several people with shared infrastructure Are the participants independently eligible? Excluding everyone with a shared network or sponsor
Distinct but coordinated donors How should related support affect matching? Assuming personhood proves independence

These distinctions matter when reviewing an apparent cluster. An office network can connect genuinely separate donors. A single participant can use several unrelated funding sources. A community can independently value the same projects while showing correlated donations.

Keep the relationship type and its source in the investigation record. A graph edge should describe an observation, not silently assert that two donors are the same person.

Verify eligibility without confusing it with independence

A uniqueness scheme can help limit repeated donor identities. Its required credential, expiration, action scope and duplicate handling need to match the round. Passing a credential does not establish whether a donor has a shared economic interest with a project.

Human Passport offers credential, model and batch-analysis routes. BrightID uses social uniqueness verification. Evaluate the selected product’s assertion and participant journey rather than treating their outputs as interchangeable certificates.

Where donors use a supported web flow, ShieldLabs can add device/network and Multi-accounting evidence. Associate the donor account and wallet with the verified observation. It supplements the round’s identity review; it does not decide how a funding mechanism should discount related communities.

Analyze coordination at the matching stage

A round can have valid unique participants and still face concentrated coordinated support. Gitcoin’s Cluster-Matching explanation addresses correlated donor groups as a mechanism-design question rather than simply declaring all cooperation fraudulent.

That distinction prevents an important category error: a relationship can be relevant to matching without making either participant ineligible. The mechanism may consider correlated support, while the identity process separately determines whether each donor is allowed to participate.

Use a documented mechanism and test its assumptions against the round’s community. Do not import a clustering threshold from an unrelated campaign and assume it fairly distinguishes capture from a legitimate closely connected community.

Design the review window before funds move

A useful round process has explicit stages:

  1. Publish donor and project eligibility conditions.
  2. Collect contributions and the evidence required for those conditions.
  3. Preserve a versioned contribution dataset and cutoff.
  4. Investigate repeated participation and relevant coordination separately.
  5. Resolve disputed eligibility before final matching where the mechanism permits.
  6. Calculate the final match using the published method.
  7. Retain a traceable correction and reporting record.

For an illustrative case, several small donations might resolve to one observed device. Review whether that device represents one participant, a permitted shared workstation or an organizational flow. Do not automatically collapse every linked wallet into one donor. Independently verify the relevant participation rule.

Measure fairness as well as suspicious volume

The number of flagged donors is not the number of correctly detected Sybil identities. Establish independent labels for known legitimate and controlled repeated-participation cases. Keep unresolved evidence in a separate group.

Review whether genuine newcomers, shared-device users or sponsored participants are disproportionately affected. Track completed verification, review time and corrections before final allocation. A participant who never appeals may simply have abandoned the process.

Also examine the matching mechanism’s outcomes. A tool can accurately identify duplicate participants while the mechanism still over-rewards coordination among distinct people. Those are different evaluation results and may require different interventions.

Choose products for the round’s evidence gaps

Use wallet analysis when the relevant question concerns contribution and funding history. Use uniqueness verification when the rule concerns one eligible person. Use live device/account evidence to investigate repeated activity in observed application flows. Use the round’s mechanism and governance process for correlated support and disputes.

The alternatives page compares those layers, and the methodology publishes the criteria behind the scores. Before buying, confirm data delivery, supported chains, enrollment effort and review timing relative to the round’s finalization.

FAQ

Will proof of personhood stop all quadratic-funding manipulation?

No. It can support unique-participant eligibility under its scheme. Distinct people can still coordinate, so independence and matching design require separate consideration.

Should every shared funding source make donors ineligible?

No. Exchanges, bridges and sponsors can serve many legitimate donors. Investigate the relationship and apply the published round policy.

When should a disputed donor be reviewed?

Preferably before final matching or irreversible distribution, within a published review window. The correction route depends on the round’s actual mechanism and state.

Sources and further reading

Read October 21, 2026: Gitcoin, How to Attack and Defend Quadratic Funding, Gitcoin, Cluster-Matching QF, Human Passport, BrightID and ShieldLabs Sybil solution. The Gitcoin articles are dated mechanism explanations, not claims about today’s round configuration.

Continue reading

Compare all ten tools or read the complete deployment guide.