1. Meta Data
Original Author(s): list of authors. Include full name or pseudonym. At least one author must have valid contact information provided
Stage: The current stage of this GOC. Available values: Proposal, Draft, Candidate, Accepted, Live, Rejected, Retired
Creation Date: Date when code first reached Proposal stage
Live Date: Date when GOC initially went live with version 1 and became operational
Last Version: Current version number. Updates made to sections Live Date, Organization, Tags and References do not require a full version update (+1 to the nearest full integer), but should rather be documented as minor version updates (+0.01) without the need for on-chain Signal Proposal, but rather be approved off-chain by Ops Committee
Last Version Date: Date when latest version went live and became operational
Last Version Author(s): A list of authors of the latest version. Include full name or pseudonym. At least one author must have valid contact information provided
Organization: List which part of the DAO organization is directly impacted by this GOC. Available values: DAO (everyone impacted), Advocate Committee, Grant Committee, Ops Committee
Tag(s): Select all key tags that apply to this GOC. Available values: Advocate Program, Community Grant Program, ClickUp, Coordinape, DAOHaus, Discord, Discourse, Email, Emergency Multisig, Financials, Forum, GitBook, Google, Governance, Guideline, JotForm, Procedure, Twitter, Website
Version History:
| Version | GitHub Commit-Hash | Comment |
|---|
Ensure to highlight the latest DAO-approved version
2. Summary
A brief (roughly 5-10 lines) summary of this proposed GOC
3. Motivation
Why are you proposing this change? How will its adoption benefit the Graph AdvocatesDAO operations or community? What problem does it solve?
4. Prior Art
(Optional) Many ideas are influenced by prior work completed, either within the DAO community or other web3 protocols. This section provides the opportunity to recognize prior art that has inspired or influenced the design of the proposed code. What solutions have been explored previously in this problem space? What prior art inspired or influenced this design?
5. Specification
Describe your specific solution beginning at a high level and subsequently work your way down to lower levels. Include diagrams, process flows, organizational charts, and any other artifacts helpful in showing how your proposed code works. This type of information is required for a proposal to reach the Proposal stage.
Specifying the right level of detail is key. Too broad of a specification may leave readers with numerous questions where stakeholders might end up with differing interpretations of the core spirit of the proposed code. Defining too much detail may lengthen a code unnecessarily and prohibit a degree of flexibility required for future code owners to identify best paths to implement the code. GOCs are not meant to be detailed Standard Operating Procedures (SOPs).
6. References
6.1. Relevant GOCs
Specify any other GOC that intersects or connects with this GOC
6.2. Links
Provide links to documents, websites or applications as applicable
6.3. Attachments
Provide any attachment that this GOCs references or utilizes in operation