🍊Public Reporting Requirements for Grantees

Objective: The aim is to establish a set of requirements that ensures consistent, easy-to-understand disclosures without creating unnecessary friction that could deter projects from building on MVC.

Proposers will be responsible for providing necessary data in a user-friendly format, which will be publicly accessible for community use.

The data collection from grant recipients will occur during the KYC information collection at the time of grant approval and during the evaluation of milestone-based grant distributions.

The proposed system incentivizes proposers to provide regular updates

Proposed Reporting Fields

Our goal is to collect all information in a way that:

• Any delegate/analyst can accurately track grant distributions

• Governance can effectively evaluate the user growth experiments and continue to iterate

• Requirements are thorough but lightweight enough to avoid overburdening proposers

The following information may be entered by proposers in a Google Form. Results would be publicly viewable by anyone (and updatable by the Foundation or Grants Council, as applicable)

For Builders Grants

Grant Program Distributions: List of grant payouts for projects who used their Space governance grant to run their own grants program. This helps us understand the impact of governance distributions to project grants programs (i.e. what super cool things came out of the grants programs?)

1. Project and Grant Name: Name of grant and project transferring Space

2. Affiliated Project (if applicable): Top-Level project that received Space (i.e. Mirror, Gamma / <> Uniswap)

3. Transaction Hash: Transaction hash of the transfer

4. Sender Address: Address sending the Space (i.e. the project’s wallet)

5. Recipient Address: Address receiving the Space (i.e. the project’s wallet)

6. Space Transferred: Amount of Space Tokens Transferred

7. Recipient Address Name: What is the recipient address’ purpose (i.e. entity name, address label)

8. Grantee Name: Name of the entity receiving the grant (could be generic, i.e. bug bounty, if relevant)

9. Grantee Website/Github/Twitter: Where can we keep up with the grantee’s progress?

10. Grant Description: Information about the grant (i.e. purpose, milestones, grant program information)