Introducing the FDD Review

FDD Review List of Articles

1/11/23 - Public goods Legos: roadmap

12/21/22 - Passport scoring-as-a-service

12/8/22 - Anti-Sybil Legos

11/7/22 - Insights from GR15 Identity analysis

10/18/22 - FDD: some security & privacy issues in a protocol based grants system

9/16/22 - The Limits of Sybil Defense (and How Composability Might Help)

9/8/22 - Scaling Gitcoin Grant Reviews

8/29/22 - Decentralizing Sybil defense using Gitcoin data

8/2/22 - Closing the Gap Between Passport Trust Bonus and FDD Sybil Detection

7/11/22 - Rethinking FDD: Defending Against Fraud or Optimizing Capital Allocation.

Prior to the launch of FDD Review but still canonical

5/31/22 - The Grants 2.0 Funding Stack - Choose Your Own Algorithm

4/28/22 - Grant Reviewer Rewards Modeling

12/1/21 - A Community Based Roadmap for Sybil Resistance

Introduction to FDD Review

This is an announcement to kickoff an communication series about FDD. The intention is to update the community through the voice of an honest critic. The remit for this “honest critic” role is to point out areas where FDD is becoming misaligned with its stated goals and/or the values of the wider community, or is failing to adequately explain its internal processes to its various stakeholders. The aim of this is to provide transparency of FDD to the wider community and stimulate continuous FDD introspection and course-correction.


After a difficult restructuring and realignment sparked by the Season 14 Budget Request process, we learned that our communication was subpar. Poor external communication of our objectives and methods led to difficult budget negotiations. At the same time, poor internal communication allowed individual squads to become siloed, making high-level decision making difficult.

Our hypothesis is that a dedicated role focused on high-level critical feedback that specifically aims to point out instances of misalignment or opacity will enable a positive feedback loop which continually improves the alignment of FDD both internally and externally and significantly improve our outcomes and accountability.


An honest critic requires subject matter expertise, experience of participating in FDD processes, and an exceptional skill for communicating nuanced and technical information. The critic must be a passionate advocate for the subject matter but not wholly dependent on the financial success of the endeavor.

Our critics are asked to keep a high-level overview of the stream as a whole and write regular posts for consumption within and outside FDD. These posts may clarify the purpose and the mechanics of the work done in FDDs squads, point out inefficiencies and misalignments between the work done by individual squads and the wider stream, and the instigate conversation to refocus the direction and priorities of the stream itself. Ultimately, the aim is to review and communicate the work of FDD in the context of its various stakeholders, users and the community at large.

The writing should:

  • Inform FDD of potential blind spots and new perspectives
  • Assist the community in understanding nuances and tradeoffs in FDD work
  • Provide a space for communication around FDD priorities
  • Point out new developments that FDD could consider implementing
  • Provide a tighter feedback loop for FDD optimizations

The writing should not:

  • Be seen as the chosen direction of FDD
  • Be censored or overly orchestrated by FDD
  • Focus on existing alignments, rather it should focus on tradeoffs and prioritization
  • Directly critique contributors effort or competency

This series of posts is an experiment we will run through 9/1 with renewal consideration at that time.


Ideally, this will be a role for someone, or a small group of people, who have a solid understanding of the mission of FDD, but who are not employed by FDD full time. As well as being a dedicated role, anyone can participate by tagging an post with “FDD Review”. Select articles will be featured here.

Post Summaries

Our first article proposes a rethink of FDD’s mission statement from one that focuses on “preventing fraud” to one that aims to “optimize capital allocation”. The argument is that flipping mindset from defensive and adversarial to constructive and positive will have greater overall positive impact on grant giving performance because it can cover non-Sybil inefficiencies, including those arising inside FDD.

The post challenges the assumption that a Sybil free quadratic funding round will naturally optimally allocate capital. Stakeholders in funding rounds are looking for the best possible method of funding their shared needs. Is Sybil defense the only threat a community must consider?

The tl;dr for this post is that FDD should stop asking “How do we stop fraud”? and start asking “How can we optimally allocate capital”?

Article list moved to the top of this thread!


Copy that.
Ok we understand clearly what you said

Sharing the legos documentation here for followers GitHub - Fraud-Detection-and-Defense/lego-docs: home for lego documentation


Hello, I believe that the Github resources deserve to be at least 10x more popular
Reading glasses on :disguised_face:

1 Like