VGK→ GitcoinDAO Notion System Migration
/
GitcoinDAO
GitcoinDAO
/
🔎
Fraud Detection & Defense
/
📖
The Role of FDD
📖

The Role of FDD

Role of the FDD Workstream
Gitcoin(DAO) is a catalyst that transforms capital into impact.
The mandate of this stream is to defend Gitcoin (Grants & DAO) from any threats to its legitimacy, credible neutrality, and sustainability.
Two Categories of Serving Our Mandate
We see two broad categories of how the FDD workstream has served this mandate during Q3.
  1. Defense - Anti-sybil, grant policy, user policy, policy enforcement, and research.
  1. DAO Support - Internal stream operations, financial & structural support
In August 2021 before the first budget proposal was passed, we began developing our structure on Notion & Discord. These became our primary tools for asynchronous & synchronous communications respectively.
As the workstreams developed, FDD needed to quickly create a structure that would provide contributors in critical functions the ability to participate. GR11 was only weeks away and grant rounds depend on many of the defense functions of the FDD.
We made it easy for contributors to participate in FDD in these ways:
  • Ability to see the opportunities available (streams, initiatives, and working squads)
  • An easy system for signaling interest, suggesting updates, and participating
  • The ability to easily communicate with other contributors without a gatekeeper or router
  • Knowing and understanding the compensation structure
  • Empowerment to drive projects where their skills are helpful
A core competency which has emerged is the ability to quickly structure, train, and scale functional working groups. This function firmly fits within our mandate as the sustainability of GitcoinDAO is dependent on filling functional gaps, ensuring a positive contributor experience, and maximizing the evolutionary experiments which will help us find positive sum collaboration mechanisms.
The DAO Support function of FDD
The DAO support work came from other streams adopting our processes. This has been critical for jump starting DAO contributors, providing a better user experience, and aligning shared systems across the DAO. These contributions included:
  • Data / DevOps Services - Needed to run anti-sybil microservices & empower community
    • DevOps services should be made available to all streams
    • Make data maximally available to the community to allow open science
    • Reporting & Analytics falls clearly into knowing what dangers the DAO faces, but shouldn’t duplicate efforts for product (MC + DG) and growth (MMM & PG)
  • Cross Stream DAOops
    • Specialist squads with proper access and knowledge of critical dependencies
      • Notion 1337 crew
      • Discord Roles, Bots, Channels
      • Calendar Crew
      • Zapier Automations
    • Operational support squads which are beneficial to have available to all streams
      • Accounting
      • Legal
      • Payment mechanism gurus
      • Contributor Support
  • Community - FDD funded as necessary but not included in any WS budget
    • Contributor Experience - Designing the experience flow
      • Onboarding - Contributor Reviews / Approvals
      • Onboarding - Contributor success call squad
    • Token Holder Experience - In planning phase
    • Steward Experience - In planning phase
  • User Support was added just after the Q3 budget passed, realizing that the Gitcoin core team was two weeks behind on support tickets with a busy GR11 coming.
    • Discord support for three time zones
      • China / Asia
      • EU / Africa
      • Americas
    • Knowledge Base - Moving to open source / sourcecred instance
    • Translations - Updating Knowledge base, API docs, etc
    • Ambassadors - In planning phase
Standing up the DAO Support functions has been done in a way that does not require mandating, but rather thinking through how to build scalable processes with positive-sum outcomes.
Spinning Out the DAO Support Streams
All streams are either “structured” or “unstructured”.
The structured streams follow the guidelines of the Cross Stream DAOops Governance Committee to ensure modularity and composability. They also benefit from being able to build on the knowledge of other structured streams.
Unstructured streams are essentially payments to an address that will be trusted to put the funds to good use, but not through GitcoinDAO’s collaboration models. The DAO Support streams listed above are all best suited as structured streams, but have not gotten to a state of maturity to be fully self-governed without trusting whomever might lead these streams.
We envision that all of the DAO Support streams listed above should be “spun out” as either one workstream or individually as their own streams with independent decision making and control of assets once they reach maturity.
The Steward Decision for Q4 2021
Because we think it is important to leave this decision up to the stewards, we will be presenting our Q4 budget to include the option of funding for all of the DAO Support functions we are currently supporting.
If approved, FDD maintaining these funds and the operational structure to pay contributors would be subject to releasing designated funds to any stream that is able to gain steward approval via snapshot vote.
During Q4, our goal would be to assist the contributors in these streams to find emergent leadership, decide on their stream’s governance framework, and set up their Notion, Discord, stream onboarding, and asset management plans to accelerate their maturity.
The Cross Stream DAOops budget, while administered by FDD, would be governed by the DAOops CrossStream Governance panel.
There isn’t currently a stream that handles the much needed functions of:
  • Financially filling in gaps like the DAO Support functions above
  • Assisting streams & squads in tool setup, usage, and tracking
  • Providing shared services and covering shared costs between streams
Our aim here is to communicate the necessary functional role the FDD workstream is serving to our stewards and justify the passing of our Q4 budget.
We aim to not only spin out the DAO Support functions, but also to templatize the process of standing up new streams. Once this evolutionary function is spun out, the FDD can then focus purely on defense while the evolution stream can fill in gaps, incubate, and accelerate new potential workstreams.
VGK→ GitcoinDAO Notion System Migration
/
GitcoinDAO
GitcoinDAO
/
🔎
Fraud Detection & Defense
/
📖
The Role of FDD
📖

The Role of FDD

Role of the FDD Workstream
Gitcoin(DAO) is a catalyst that transforms capital into impact.
The mandate of this stream is to defend Gitcoin (Grants & DAO) from any threats to its legitimacy, credible neutrality, and sustainability.
Two Categories of Serving Our Mandate
We see two broad categories of how the FDD workstream has served this mandate during Q3.
  1. Defense - Anti-sybil, grant policy, user policy, policy enforcement, and research.
  1. DAO Support - Internal stream operations, financial & structural support
In August 2021 before the first budget proposal was passed, we began developing our structure on Notion & Discord. These became our primary tools for asynchronous & synchronous communications respectively.
As the workstreams developed, FDD needed to quickly create a structure that would provide contributors in critical functions the ability to participate. GR11 was only weeks away and grant rounds depend on many of the defense functions of the FDD.
We made it easy for contributors to participate in FDD in these ways:
  • Ability to see the opportunities available (streams, initiatives, and working squads)
  • An easy system for signaling interest, suggesting updates, and participating
  • The ability to easily communicate with other contributors without a gatekeeper or router
  • Knowing and understanding the compensation structure
  • Empowerment to drive projects where their skills are helpful
A core competency which has emerged is the ability to quickly structure, train, and scale functional working groups. This function firmly fits within our mandate as the sustainability of GitcoinDAO is dependent on filling functional gaps, ensuring a positive contributor experience, and maximizing the evolutionary experiments which will help us find positive sum collaboration mechanisms.
The DAO Support function of FDD
The DAO support work came from other streams adopting our processes. This has been critical for jump starting DAO contributors, providing a better user experience, and aligning shared systems across the DAO. These contributions included:
  • Data / DevOps Services - Needed to run anti-sybil microservices & empower community
    • DevOps services should be made available to all streams
    • Make data maximally available to the community to allow open science
    • Reporting & Analytics falls clearly into knowing what dangers the DAO faces, but shouldn’t duplicate efforts for product (MC + DG) and growth (MMM & PG)
  • Cross Stream DAOops
    • Specialist squads with proper access and knowledge of critical dependencies
      • Notion 1337 crew
      • Discord Roles, Bots, Channels
      • Calendar Crew
      • Zapier Automations
    • Operational support squads which are beneficial to have available to all streams
      • Accounting
      • Legal
      • Payment mechanism gurus
      • Contributor Support
  • Community - FDD funded as necessary but not included in any WS budget
    • Contributor Experience - Designing the experience flow
      • Onboarding - Contributor Reviews / Approvals
      • Onboarding - Contributor success call squad
    • Token Holder Experience - In planning phase
    • Steward Experience - In planning phase
  • User Support was added just after the Q3 budget passed, realizing that the Gitcoin core team was two weeks behind on support tickets with a busy GR11 coming.
    • Discord support for three time zones
      • China / Asia
      • EU / Africa
      • Americas
    • Knowledge Base - Moving to open source / sourcecred instance
    • Translations - Updating Knowledge base, API docs, etc
    • Ambassadors - In planning phase
Standing up the DAO Support functions has been done in a way that does not require mandating, but rather thinking through how to build scalable processes with positive-sum outcomes.
Spinning Out the DAO Support Streams
All streams are either “structured” or “unstructured”.
The structured streams follow the guidelines of the Cross Stream DAOops Governance Committee to ensure modularity and composability. They also benefit from being able to build on the knowledge of other structured streams.
Unstructured streams are essentially payments to an address that will be trusted to put the funds to good use, but not through GitcoinDAO’s collaboration models. The DAO Support streams listed above are all best suited as structured streams, but have not gotten to a state of maturity to be fully self-governed without trusting whomever might lead these streams.
We envision that all of the DAO Support streams listed above should be “spun out” as either one workstream or individually as their own streams with independent decision making and control of assets once they reach maturity.
The Steward Decision for Q4 2021
Because we think it is important to leave this decision up to the stewards, we will be presenting our Q4 budget to include the option of funding for all of the DAO Support functions we are currently supporting.
If approved, FDD maintaining these funds and the operational structure to pay contributors would be subject to releasing designated funds to any stream that is able to gain steward approval via snapshot vote.
During Q4, our goal would be to assist the contributors in these streams to find emergent leadership, decide on their stream’s governance framework, and set up their Notion, Discord, stream onboarding, and asset management plans to accelerate their maturity.
The Cross Stream DAOops budget, while administered by FDD, would be governed by the DAOops CrossStream Governance panel.
There isn’t currently a stream that handles the much needed functions of:
  • Financially filling in gaps like the DAO Support functions above
  • Assisting streams & squads in tool setup, usage, and tracking
  • Providing shared services and covering shared costs between streams
Our aim here is to communicate the necessary functional role the FDD workstream is serving to our stewards and justify the passing of our Q4 budget.
We aim to not only spin out the DAO Support functions, but also to templatize the process of standing up new streams. Once this evolutionary function is spun out, the FDD can then focus purely on defense while the evolution stream can fill in gaps, incubate, and accelerate new potential workstreams.