Skip to content

Boardroom-governance-docs #125

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 114 commits into
base: main
Choose a base branch
from

Conversation

alexsampson-tech
Copy link

@alexsampson-tech alexsampson-tech commented Apr 7, 2025

No description provided.

Copy link
Contributor

juntao commented Apr 7, 2025

Hello, I am a PR summary agent on flows.network. Here are my reviews of code commits in this PR.


Overall Summary

The Pull Request titled "Boardroom-governance-docs" introduces several updates to the governance documentation. Key changes include:

  1. Delegation and Voting Updates: The document now includes details on how to delegate voting power on Tally, including delegating your own tokens to yourself and the steps for a delegation transaction.
  2. GAIA Security Council Details: A new section has been added about the Gaia Security Council, specifying its members' qualifications, responsibilities, and procedures for emergency upgrades.
  3. New Governance Categories: The documentation now includes three new categories under the governance section: Community, Forum, and Legal.

Potential Issues

  1. Missing or Incorrect Information: There are some sections that seem to be incomplete or contain outdated information. For example, the delegation standards section mentions a "Delegates" section, but there's no content about delegates.
  2. Consistency in Documentation Format: The formatting of the documentation may be inconsistent, which can make it difficult for users to find specific information.

Most Important Findings

  1. Completeness and Accuracy: The majority of the updates are accurate and align with current governance practices. However, there is room for improvement on some aspects of delegation and governance standards.
  2. Consistency in Navigation: The documentation should be more consistent in its navigation, ensuring that users can easily find the information they need.

Potential Issues

  1. Missing or Incorrect Information: There are some sections that seem to be incomplete or contain outdated information. For example, the delegation standards section mentions a "Delegates" section, but there's no content about delegates.
  2. Consistency in Documentation Format: The formatting of the documentation may be inconsistent, which can make it difficult for users to find specific information.

Most Important Findings

  1. Completeness and Accuracy: The majority of the updates are accurate and align with current governance practices. However, there is room for improvement on some aspects of delegation and governance standards.
  2. Consistency in Navigation: The documentation should be more consistent in its navigation, ensuring that users can easily find the information they need.

Details

Commit d0e3c04d926feeb3b5661bfc30a2c04aacd0f4fb

Key Changes:

  • The llamacpp documentation for fine-tuning a model on CPUs has been deleted.
  • The process of fine-tuning using the llama.cpp library and converting Q5 GGUF models to LLMs with LoRA (Low-Rank Adaptation) is described in detail.
  • A guide for creating a question and answer set for fine-tuning is provided.

Commit 27a318a4a2a9334b8e133e54cf86097162976c97

The key changes in this GitHub Pull Request are:

  • A new welcome page has been added to the Governance documentation.
  • The main heading is updated from "Fine-tune LLMs" to "Welcome to Gaia Governance."

Commit 053dc0370ade035cd397b5667c7a25f55aa3e1d5

Key Changes

  1. Add/Word-Change

    • A word was changed from "LLM" to "LLM (Large Language Model)" in the text.
  2. Paragraph Update

    • The paragraph has been updated with a sentence explaining that it's necessary to create question and answer pairs to train an LLM.

Commit 6fcb21f2a2a1374b14044e6cd29e391e3a86fe22

-This pull request updates the Welcome category documentation in the Boardroom governance repository. The main change is that it replaces a description about fine-tuning language models with a list of links, GaiaNet DAO mission details, contract addresses, and other relevant information.

Commit 115e2593444dc06ef74ab5feba896b740e2d6859

Key Changes Summary:

  • Welcome Page Content:

    • Updated the welcome page to include new sections on the GAIA token contract, delegate voting power page, governance contract code, main documentation link, app link, blog link.
  • GAIA Governance System:

    • Added a section on the purpose of the GaiaNet Governance System.
    • Created a sub-section for evaluating the impact of governance proposals and defining primary goals and KPIs.
  • GAIA Network Contract Addresses:

    • Updated the addresses for the GAIA Token, Governor, Foundation Address, Security Council Address.

Commit 9dd753fe5b9682b38efd33d63a74db2387cfa1f4

The key changes in this patch are:

  1. Clarified Protection of Human Knowledge: The text has been revised to clarify that Gaia's decentralized platform ensures robust protection for user data and IP. This is now written under the "Protecting human knowledge" section.

  2. Continuous Adaptation and Growth: The text has been refined to emphasize continuous adaptation and growth in real-time, which now appears as a bullet point under the "Continous adaptation & growth" section.

  3. Extensible Knowledge Environments: The text has been improved to highlight how Gaia simplifies decentralized AI, making it accessible to developers and end-users, by writing under the "Extensible knowledge environments" section.

  4. Applications Powered by Rich Knowledge: The text has been revised to clarify that Gaia enables the creation of applications using high-quality, specific knowledge bases, ensuring AI models are built on rich, precise data for more accurate and specialized solutions. This has also been written under the "Applications powered by rich knowledge" section.

  5. Governance Contract Addresses: The text has been updated to list the governance contract addresses in the footer, ensuring all references remain current.

Commit 8fd7a45c3295d0722928f685a04572f5a99ebd9b

Key changes in the GitHub Pull Request:

  1. Fixed bullet indentation:

    • The bullets (-) were not consistently indented properly, affecting readability and consistency.
  2. Updated example KPIs:

    • A single example KPI was provided for "Number of Incidents" with an objective set to 0. This is a minor update but improves clarity about the data being measured.
  3. Fixed bullet indentation again:

    • The same issue was present in another area, specifically for the "Strengthen the GAIA Community" section. This ensures consistent formatting across the documentation.

The patch aims to improve readability and maintain consistency by properly indenting the bullets.

Commit ccb89e3dd54ca416656b68fa444d829b13655b57

Key Changes:

  1. Sidebar Position: The sidebar in the welcome page has been updated to position 1, which is likely an aesthetic change for better visibility on mobile devices.
  2. Documentation Structure:
    • Added a header with ---sidebar_position: 1 to indicate this is the main content area.
    • Updated the documentation structure to reflect the new sidebar arrangement.

Conclusion:

The patch adjusts the sidebar position of the welcome page in the GaiaNet governance documentation, providing a more organized and user-friendly interface.

Commit a647bc451038ee9a714078a92c5d96462471a18c

Key changes in the patch:

  • Added a new section for Delegation, explaining how GAIA tokens can be delegated to other users or entities.
  • Clarified that delegation does not remove tokens from control but allocates voting power to someone else.
  • Defined what GAIA tokens equate to in terms of votes.

Commit d24b3a69a1432a57841402476ec47d9540e6bd3e

-### Key Changes in the Patch

  1. Delegation Documentation:

    • Added a new section on delegation governance.
    • Defined delegated token voting power and its implications.
    • Explained how delegation can be changed, persisted, or deactivated.
  2. Embedding Creation:

    • Mentioned that Firecrawl can convert any website into LLM-ready markdown or structured data.
    • Provided instructions for using Node.js to interact with the Firecrawl API to parse a URL and create embedding snapshots.

Additional Notes

  • The patch maintains the structure of the existing document but updates specific sections on delegation governance and embedding creation.
  • It uses Markdown format to organize the information, making it easier for users to read and reference.

Commit b406f48fe935f5f62ee7b94558ecdc757c519d7d

-Here are the key changes in concise points:

  1. The document discusses how to create a vector collection snapshot from a Markdown file.
  2. The markdown file is segmented into multiple sections by headings, and each section becomes a vector.
  3. Prerequisites include the WasmEdge Runtime, the embedding model nomic-embed-text-v1.5, Qdrant installation, and custom knowledge base setup.
  4. The document provides instructions for creating the vector collection snapshot from a Markdown file using Wasmer and a custom embedding model.
  5. It also outlines options to customize the context size, heading level, maximum context length, and starting vector ID.
  6. The document highlights the benefits of delegation as it allows anyone without GAIA tokens to hold voting power in governance without financial cost.

The changes focus on improving the documentation on how to create a knowledge base snapshot using Wasmer and an embedding model for delegators.

Commit 06b5128151959c66b703448f84c8f52832b03e2f

-This PR updates the documentation on boardroom governance for Delegation section. It includes the following key changes:

  • Added a guide on how to delegate voting power on Tally
  • Removed existing content in the how-to-delegate.md file
  • Updated the title from "How to Delegate" to "Delegating voting power on Tally"
  • Updated the sidebar position to 4

Commit a31c072c297df902ff01ad11d0b7dc28752f2574

-The GitHub Pull Request titled "Boardroom-governance-docs" introduces an update to the governance documentation for Delegation. The change involves modifying the _category_.json file under the Governance directory in the docs folder, updating its description from providing information on creating vector collections based on proprietary and private knowledge to explaining how delegation works in GaiaNet governance. This update is a significant revision aimed at improving the clarity of the documentation and aligning it with the current governance practices.

Commit 5fd1121784472105954d3bfa9562dd982d6038fb

The key changes in the GitHub Pull Request "Boardroom-governance-docs" include the addition of new sections and files for various aspects of governance, such as voting categories, portals, on-chain voting, prerequisites, snapshotting, and voting parameters. The additions provide a comprehensive guide to GaiaNet governance practices, covering different delegation models and methods.

Commit 3212f61acd44d8dc38d5c0124283c396cab2585c

The key changes in this GitHub Pull Request include the addition of new governance documents and categories, such as:

  1. New Category: A new category Governance was added.
  2. Amendments to Governance: Details about how token voting power can be delegated were added.
  3. Supporting Entities: Information about entities that can delegate voting power was provided.
  4. GIP Template: A general template for governance proposals was introduced.
  5. Governance Bodies: Guidance on what governance bodies are and how they operate.
  6. GaiaNet Governance System: An explanation of the delegation mechanism.
  7. Mission: Details about the mission of delegating voting power to third parties.
  8. Overview: A comprehensive overview of the governance process, including the steps for token delegation.
  9. Governance Procedures: Guidance on how to participate in governance processes through delegation.
  10. GaiaNet Security Council: An explanation of what the security council is and how it operates.

These additions provide a more detailed and comprehensive documentation about governance topics within the project.

Commit a2bbb44648158081a1b8984df116ef08cedb0bd8

The patch updates the description of the "Voting" category in the Governance documentation to provide an explanation of how voting works, rather than just delegation.

Commit 2f85da1fde0589c031490d8d6cfd0f443127f01f

Key Changes in Summary:

  1. Voting through Governance Portals:

    • Introduced governance portals for users to review and vote on proposals.
    • Users can delegate tokens to interact with GaiaNet contracts.
  2. Delegation Process:

    • Tokens can be delegated by users, who need to approve the delegation from the governance portal.
    • Delegates are allowed to cast votes directly through the Tally Governance Portal.
  3. Current Portals:

    • There is currently one primary governance portal for voting on active proposals: [link]

Commit 76881ac105b97527c6ff0e6db53909c014ad6c1e

-### Key Changes:

  1. Added a new section on Prerequisites in the Voting/prerequisites.md file.
  2. Updated the title of the page to "Prerequisites".
  3. Deleted two sentences about Delegating token voting power and added four new sentences about prerequisites including:
    • Using an Ethereum-compatible Web3 wallet
    • GAIA tokens delegated to you
    • Gas tokens required for voting (ETH on mainnet)
    • An active proposal

Commit 01c9753a93206b8512f0246e5257d2210f14e789

The main changes in the GitHub pull request "Boardroom-governance-docs" are:

  1. Onchain Voting Changes:

    • The voting period for onchain proposals has been updated to seven (7) days.
    • GIPs can be voted on via various channels: Tally, independent applications, or directly on the block explorer.
    • Delegates now participate in governance by holding voting power through delegation.
  2. Quorum Requirement:

    • Onchain proposals have a quorum requirement of 4% (or 40 million GAIA) of the total number of tokens that may be minted (1 billion).
    • The simple majority rule applies to determining proposal outcomes, meaning at least 50% of the "for" and "against" votes are necessary.
  3. Proposal Process:

    • Delegates can vote on onchain proposals.
    • If a quorum is reached, the proposal's Voting Period will remain open for seven days.
  4. Additional Information Links:

    • Two additional links have been added to help users learn more about delegation and the proposal process.

Commit 90aa971c4d3cf8c706f0644311fff903dc1fb1f2

-This Pull Request updates the documentation for Snapshot voting in the Governance section of the GaiaNet blockchain. The key changes include:

  1. Removing outdated links and instructions for manual voting on Tally.
  2. Adding a link to the Tally guide for more information on delegation on Tally, although this functionality is no longer available as the link is now disabled.

Commit cda4530ef48785c6a665e5da76ecbe7c44a6ca4e

-This patch updates the documentation on voting power, making it more concise and clear. It explains that one GAIA token equals one vote over any proposals submitted to the GaiaNet DAO (the “Voting Power”). This simplifies the information for users while maintaining accuracy.

Commit a3fecbcc1069bc3142de499d05e0998f8f22a967

  • The patch updates the Voting parameters for Tokenholders in voting-parameters.md with new details:
  • A three-day vote delay period is added to the initial submission of a proposal.
  • The Voting Period is extended to seven days.
  • A Timelock period is implemented, requiring a minimum three-day delay before proposal execution.
  • The Proposal Threshold is set at 0.2% (2 million GAIA) for submitting GIPs for an on-chain vote.
  • The Quorum threshold is increased to 4% (40 million GAIA).

The proposed changes are part of a broader governance process related to the Tokenholders' voting rights and procedures.

Commit 267369f251df698c9f0de463f029aa2ecad943a1

  • The patch updates the documentation for a governance section in GaiaNet, changing the description from "An explanation of how delegation works in GaiaNet governance" to simply "An explanation GaiaNet's governance system".

Commit fb8240bf1257319f7f9395e45b4e1baf19fe174b

-This PR updates the governance document for GaiaNet, focusing on the overview of how tokens are delegated and voting is enforced. Key points include:

  1. Delegating tokens grants another user voting rights.
  2. Token holders must delegate their tokens to an Ethereum address.
  3. The controller of a delegate becomes a Delegate who can vote on governance proposals.
  4. Some guidelines for governance are provided, with the intention of fostering best practices but are not legally binding.
    The patch aims to improve the clarity and comprehensiveness of the governance document for users and stakeholders.

Commit a7b845ca6f83bfe08e4ff31c370bf6edd7bccd2b

The following key changes are made in this GitHub patch:

  1. The GaiaNet governance system is introduced, which governs smart contracts related to GaiaNet.
  2. The Governance contract is deployed at two locations: Ethereum and Base networks.
  3. This allows for more decentralized governance without requiring a significant economic investment.

Commit 56b5f672763657af0c60948e02ff29949154e87f

The key changes include:

  • Updated the "Mission" section to replace the old paragraph with a reference to the [GaiaNet DAO Mission].
  • Removed unnecessary sections related to token voting power delegation (delegation types, persistence rules, splitting rules).
  • Added a brief introduction to the GaiaNet DAO's mission.

Commit a15a1dfcc5a69ad9833f3a04e3bebcfa14e171fd

Here are the key changes in summary:

  1. Update of governance bodies: The main points are updated to reflect the current governance structure.
  2. GAIA Delegators: This includes:
    • A governance body consisting of GAIA tokenholders who delegate voting power.
    • Delegates can vote on proposals, including delegating their own tokens to themselves.
  3. GaiaNet Security Council: This is described as a committee made up of committee members who have the power to execute certain Emergency Actions on the GaiaNet DAO and the Foundation Company.
  4. Multisig wallet: The primary responsibility of the Security Council is to review and approve proposals submitted by Delegates before they are executed onchain.

Commit 3a4d783dac72314274c908e27916592a7575c139

The main changes in the patch are:

  • The removal of a guide on voting power delegation from Tally.
  • The addition of details about the GaiaNet Foundation and its multisig (GaiaNet Foundation Multisig).

Commit acf0e484dce6bfbc1ca7e6c8602ad4750d285596

-### Key Changes in the Pull Request

  1. Proposal Submission Process:

    • Drafting GIPs: Proposals include all proposals submitted through the GaiaNet Governor contract, following a template.
    • Onchain Submission: Proposals are submitted for onchain voting after the Discussion Period ends, with a quorum requirement and simple majority.
  2. GIP Submission Rules:

    • Voting Parameters: GIPs require a minimum Quorum of 4% GAIA and a Simple Majority of "For" votes to pass.
    • Proposal Resubmission: If a GIP fails to pass, it can be resubmitted for another round after incorporating feedback.
  3. Voting Mechanics:

    • Voting Delay Period: Proposals enter a three-day Vote Delay period prior to the Voting Period.
    • Quorum Requirement: Delegates must reach a quorum of 4% GAIA voting power to submit a GIP for an onchain vote.
    • Timelock Period: The Timelock Period is three days after the end of the Voting Period.
  4. Delegation and Voting Power:

    • One GAIA token equals one vote over any proposals submitted, enabling tokenholders to participate proportionally.
  5. Implementation and Timing:

    • Upon expiration of the Timelock Period:
      • Onchain Actions may be queued or executed immediately.
      • Offchain Signal Votes should be considered a recommendation rather than mandatory requirements to take action.

Additional Insights

  • This patch introduces a more structured approach to GIP submission and voting, providing clearer guidelines for proposal drafting, discussion, on-chain submission, and the governance process. It emphasizes community participation and encourages active engagement in the GaiaNet DAO's governance mechanisms.

Commit 16c6591ab9818e326484cd687e1bb4c0e42ac9c9

The key changes include adding a paragraph spacing to the procedures.md file, which includes:

  • The addition of "Idea for GaiaNet improvements, new features, integrations, and governance changes" under the section heading "Step 2: Proposal Drafting".

Commit a1089219a7e60cebc3e19e63841cceff6330ec39

-This patch introduces a revised GIP template for proposal discussion in the Governance documentation. It recommends a seven (7) day Discussion Period, encourages token holders to consider voting against proposals to promote democratic governance, and provides instructions on how to signal that a GIP is eligible for submission after the discussion period has concluded.

Commit f14d5c1299017ed49ae9323683f4a2d91976a245

The main changes include adding paragraph spacing to improve readability.

Commit 0d923ac549a9f4cc7a8c6f88b08d069d2717e95f

The key changes in the GitHub patch are:

  1. Updated the GIP template to be more accessible and consistent with GaiaNet governance practices.
  2. Added sections for a simple summary, abstract, motivation, specification, rationale, backward compatibility considerations, security concerns, other information, and voting guidelines.
  3. Reorganized the content to make it easier to navigate and understand for both users and developers.
    This new template should be helpful for GIP submissions and ensure consistency across different proposals in the GaiaNet ecosystem.

Commit f96458ddc980a7c4c0bd25f347851421196c06bb

-Key Changes:

  1. Add a One-Sentence Summary: The first paragraph now states, "Add a one-sentence summary of the proposal."

  2. Use a ~250-word Abstract: The second paragraph has been expanded to 32 words.

  3. Describe the Motivation: A detailed description is provided of why this GIP is needed and what issues or opportunities it seeks to address within the GaiaNet ecosystem.

  4. Specify the Specification: The technical specification section now describes the syntax, semantics, and any new components.

  5. Rationale for Design Decisions: Rationale for key decisions and approach are included in a separate paragraph.

  6. Backward Compatibility Considerations: Issues related to backward compatibility are addressed.

  7. Security Considerations: Threats, risks, vulnerabilities, and mitigation strategies are discussed.

  8. Other Information: Links to Governance Forum discussions, blog posts, and other related discussions, as well as additional resources, context, or previous versions of the proposal, are provided.

  9. Voting Details: The voting process is defined clearly with an explanation of "Yay" and "Nay" votes.

Commit 7c016472bc7ff6894b1e1c7036517eb672f31bdd

Key changes in the patch:

  1. Updated amendments.md by removing unnecessary content about delegating token voting power.
  2. Simplified the governance process described by mentioning that GIPs can be amended or modified through the GIP process.
  3. Emphasized the community's role in deciding future governance state and GaiaNet DAO.

The patch focuses on updating and simplifying the governance documentation to better reflect current practices and community participation.

Commit 07ec5136679738dabc9c5588df50abedd4179737

  • The Security Council is described as a committee of the Foundation Company comprising [amount] committee members.
  • It has powers to perform certain Emergency Actions, as delegated to it by the GaiaNet DAO and The GaiaNet Foundation.
  • GAIA token voting power can only be delegated by the wallet owner. Tokens held within wallets on centralized exchanges cannot be delegated.

Commit 57c4e6a172a8f0810cc83b8dfa1541e39423f5a1

The main changes in this PR are to:

  1. Add a section on Emergency Actions with details on their powers, requirements, and procedures.
  2. Update the Security Council members' qualifications, including experience in risk management and blockchain security or artificial intelligence.
  3. Introduce a timeline for the election process, including nomination, voting, compliance process, transition, and removal procedures.
  4. Provide guidelines for candidate selection and verification.
  5. Outline the consequences of member removal and how emergency procedures will be used to fill positions.

Commit 60732cb4a451c1bb08313fa52c14dfaf22d2d298

-The following key changes are significant:

  1. Proposal Drafting Process:

    • The process for drafting GIPs has been streamlined by removing the mention of a Governor contract.
    • This simplification aims to focus on the core proposal submission mechanism rather than complex infrastructure details.
  2. Clarification about GIP Templates:

    • A link to an example GIP template is provided to aid users in understanding the expected structure and format for their proposals.
    • This simplifies the setup process for new contributors and encourages adherence to a standard template, improving overall governance procedures.

Commit 16b32c8ccbaf097ae768da6d2b47ad2b01db62bc

The patch changes the description of how delegation works in Gaia governance. The old description was "An explanation of how delegation works in GaiaNet governance" and the new one is "An explanation of how delegation works in Gaia governance".

Commit 43a4ce542ad752b45e89484927b55b4fec11df78

The key changes in this patch are:

  1. The subject line "Change/gaianet-to-gaia" was updated from "gaianet-to-gaia".
  2. The section title "Why Delegation Is Important" was updated to "Delegation".
  3. The content of the paragraph describing the benefits of delegation, including increased participation in Gaia governance due to the removal of an economic hurdle for non-token owners, was updated.

These changes are significant as they refine the documentation and clarify the focus on delegation.

Commit 46b1c70ea5c80c64aaed57f10de203244e0bdae6

This GitHub patch modifies the _category_.json file under docs/governance/Governance/, changing the description of GaiaNet's governance system. The new description is "An explanation Gaia's governance system".

Commit 0680f5b2f75467dc0f04652318fa13f0d338120c

Key Changes:

  1. Amendment Process: The text now specifies that the GIP process can be used to amend or modify governance mechanisms, such as the GIP itself.
  2. Governance Mechanics: The existing description of governance mechanics remains unchanged and does not mention any changes.
  3. Community Engagement: The community is encouraged to decide the future state of governance, the GaiaNet DAO, and GaiaNet itself.

These points capture the main improvements and clarifications made in the patch while maintaining a concise summary.

Commit 2fbce28b48a61de052de808b5b7264cbcb3d86b8

  • This PR changes the reference from "GaiaNet Governance" to "Gaia Foundation". The PR also updates a sentence in the governance entity section to use the new term.

Commit 2a8231c37b6c301f31eb257f087f9bd06ad6df66

The following changes were made:

  1. Removed unnecessary punctuation marks from the header.

  2. Changed "gaianet-to-gaia" to simply "Gaia."

Commit 13fd7fd1cfaf4fe734644aed5473d401f6a06fb3

-This patch makes several key changes to the Governance documentation:

  1. Change in governance bodies: It updates the list of governance bodies that participate in the GaiaNet governance system.
  2. Revised GAIA Delegators:
    • Added: A detailed description of the voting power of GAIA Delegators and how it is exercised through delegates.
    • Added: Information on how GAIA Delegators can delegate their GAIA tokens to themselves.
    • Added: Procedures for delegating voting power to GAIA Delegators.
  3. Revised Gaia Security Council:
    • Updated the control over the multi-sig contract.
    • Added information on how proposals are evaluated and approved by the Security Council.
    • Added procedures for initiating and approving emergency upgrades.
  4. These changes provide a more comprehensive understanding of the governance system in GaiaNet, including its bodies, responsibilities, and operations.

Commit 93c0c75ccc804934d1e2574605c4ab1a266c001d

Key changes include:

  1. Updated the sidebar position to 2.

  2. Changed "GaiaNet Governance System" to "Gaia Governance System".

  3. Updated the title of the file to "Governance/gov-system.md".

  4. Modified the content within the file to reflect that it governs smart contracts related to Gaia, not GaiaNet.

Commit 46b6cb69a8b6fa78a520a4c27722e1d69dd52b92

Key Changes Summary

  • The README.md file in the docs/governance/Governance/mission.md file has been updated to reflect changes from patch [46b6cb6 Mon Sep 17 00:00:00 2001] by Alex Sampson-Tech.
  • The content of the file has been modified to include a new mission statement under the header "The [Gaia DAO Mission] sets out the vision and values of the Gaia DAO. "
  • The change involves updating the text within the markdown block to reflect the latest version of the mission statement.

Commit 8cd241ddca9fa2fb8e877a4299c25aa19be92164

The patch changes the title from "Gaianet Governance Docs" to "Gaia Governance Docs" and updates the section on governance overview, removing a redundant sentence about rules being enforced directly onchain.

Commit d36dda04ab1f56584bc277e286ac84a4d19c3d8a

Key Changes:

  1. Proposal Submission and Voting Process:

    • GIPs now require at least 0.2% (2 million) GAIA delegations for submission.
    • Proposals must receive a simple majority of "For" votes in the onchain voting process.
  2. Signal Voting:

    • Offchain signal voting allows community members to express opinions and preferences before onchain voting, providing early insights into proposal acceptance.
  3. Proposal Resubmission Policy:

    • Resubmitted GIPs must demonstrate meaningful improvements and address feedback points raised during previous rounds.
  4. Voting Parameters:

    • Governor contract proposals require a quorum and at least 50% of "For" votes to pass, similar to the original proposal criteria.

Summary: The patch introduces enhanced governance procedures by emphasizing signal voting, requiring minimum delegations for submission, providing resubmission guidelines, and modifying voting requirements.

Commit d91828714074507e19b1b1cd7adb3d134726109b

The following key changes have been made in the docs/governance/Governance/security-council.md file:

  1. The Security Council's responsibilities were expanded to include emergency actions and compliance with GIPs.

  2. A Snapshot vote was required before ratifying the initial Security Council composition.

  3. The election process involved a Nominee selection period, Member Election period, Compliance process, and Transition period.

  4. No single entity should be overly represented in the Security Council.

  5. Candidates must demonstrate strong commitment to the success of the GaiaNet DAO and Foundation.

  6. Security Council members are expected to serve their term until the election is complete and a new Security Council is installed.

Commit e91245d187bf2daf0f07e24e4f85a0929ae188c2

The patch changes the category title from Gaianet governance to Gaia governance in the _category_.json file located in the docs/governance/Voting directory.

Commit 7c3c029b1c69c516a50c051359ba64a47de5a5b5

-The patch changes the name from Gaianet to Gaia in the documentation, updating the URL link accordingly.

Commit 8a12ab22d20d4aed482920c39d9ad67ebd2f08d9

Key changes:

  • The onchain voting period is now 7 days.
  • Voting requires a quorum of at least 4% of total GAIA tokens, which is equivalent to approximately 40 million tokens out of a total possible 1 billion.

Commit 0ccc0896bf129ca5098b13f3012f205da59a9eef

This pull request updates the governance documentation for Snapshot voting, specifying that proposals requiring changes to GaiaNet codebase do not use Snapshot voting.

Commit ce0a79d5c0b1f364c85213e8f393ec5a6530c8b8

The key changes in this patch include changing the description of voting power from "GAIA token" to "GAIA token equals one vote". The patch also mentions that token holders will be able to participate proportionally to their holdings in the governance process.

Commit 5b050540d02979002579852a086f980a303aa0f5

The patch changes the description of a category in the Gaia governance documentation, from "Links, GaiaNet DAO Mission, Contract Addresses, and more" to simply "Links, Gaia DAO Mission, Contract Addresses, and more."

Commit aa26efceaf137ab9035527cff1b05453539a5edc

Key changes:

  • Updated the title of the document from "Welcome to GaiaNet Governance" to "Welcome to Gaia Governance"
  • Changed "GAIA token" to "GAIA Token" in the opening sentence
  • Moved "Proposal should aim to achieve goals supporting the mission of GaiaNet." to the beginning of the section
  • Updated "Number of Incidents (Objective = 0)" and "Number of Bronze, Silver, Gold, Diamond, and Supreme Domains registered" from example KPIs to primary goals and KPIs, respectively
  • Changed "GAIA governance contract addresses" to "Gaia Governance Contract Addresses"

Commit e3f8698210c13ee768a03c904257a5e55c6f1e27

The following changes are key:

  • A placeholder entity named "Placeholder Entity" has been added to the governance section of the documentation.

Commit 244c1f1ea5bd3578abb57d0416ecb0781ab01baf

Key Changes Summary:

  • Changed the title from "page-contents" to "Governance/gov-bodies.md".
  • Removed the paragraph about Delegates and delegated voting power.
  • Added the content for the Gaia Security Council, including its composition, powers, membership, responsibilities, and emergency actions.

Commit 0aefdb04f4797b3185069d1815e8b24f54b291b4

The patch modifies the Governance section of the docs/governance/Governance/gov-system.md file by removing the mention of a contract deployed on Base.

Commit 39bb455adc51614d19d50a6899506ee44d33c56b

Key Changes

  1. Proposal Submission Threshold: Changed from 0.2% (2 million GAIA) to a placeholder.

    • Why: The new threshold is currently set as 6% (60 million GAIA), but it can be adjusted through governance mechanisms.
  2. Quorum Requirement: Changed from 4% (40 million GAIA) to a placeholder.

    • Why: Similar to the proposal threshold, this can be adjusted via governance processes.
  3. Vote Delay Period: Removed as it is no longer necessary with the new threshold and quorum requirements being placeholders.

    • Reason: The delay period was previously required for onchain voting but is not needed when the thresholds are set high enough to pass a proposal without a delay.

Commit 9f717609170db87e3227302198a65973a81755e7

  • The key changes in this GitHub pull request are:
  • Changed the name of the document from "Page Contents" to "Onchain Voting".
  • Updated the quorum requirement for onchain proposals to be 4% (or 40 million GAIA) of total mintable tokens (1 billion).
  • Modified the description of the voting period to state that it will remain open for full 7 days if a quorum is reached.

Commit f1216b7b59edddf3562e643a09b983ba88539ef8

Key Changes:

  1. Voting Threshold and Quorum Calculation: The voting threshold for a GIP has been modified from 0.2% GAIA to a placeholder value (specific to the new proposal). Additionally, the quorum has been updated to also use a placeholder value.
  2. Vote Delay Periods: The vote delay periods have been reduced from 3 days to 7 days, while the Timelock period remains at three days.
  3. Voting Parameters in General: The parameters regarding voting processes, such as the vote delay and Voting Period lengths, have been updated to reflect these changes.

These updates may affect how governance proposals are submitted, voted on, and executed within the Tokenholder community.

Commit 1d33c80562da027c94796af365bcd90d25f5f85e

The key changes in this GitHub Pull Request are:

  • The page content for the Governance section has been updated.
  • Specifically, the placeholder Foundation Address and Security Council Address have been left as is.
  • The purpose of these addresses remains unspecified.

Commit 5e40db5ee91530ab83d415cc5394fc9519efe312

-This Pull Request adds three new categories to the Gaia governance documentation, each focused on a different area of governance: Community, Forum, and Legal.

Commit 5bb2444c399fe1613bea9a73be9ea9141cd90970

This pull request updates and describes the "Community" section in the Gaia DAO governance documentation. Specifically, it modifies the JSON file located at docs/governance/Community/_category_.json to reflect changes made during a patch series. The primary change is that the category now includes a description that explicitly states the GAIA DAO Code of Conduct and Delegate Standards as its content.

Commit c10ed31d7fe9dc93102d4e3ca0d9d247c7176d3c

Key changes:

  • Updated Code of Conduct
  • Moved governance system links to the top level
  • Added expected behaviors and guidelines
  • Enhanced evaluation process for proposals

Commit 46392989ede8ecaf0b150e648111ce5de909dc84

Key Changes:

  1. Update page-contents: The patch includes changes to the file structure of docs/governance/Community/delegate-standards.md, updating the sidebar position.

  2. Delegation standards update:

    • A new section titled "Gaia Delegate Standards" is added.
    • New delegates are introduced and specific standards for their behavior, voting, professionalism, and community engagement are outlined.
    • The Standards include:
      • Personal Conduct
      • Knowledge of Gaia
      • Voting Behavior
      • Professionalism
      • Helpful Discourse
      • Conflicts of Interest
      • Remain active
    • Delegates must adhere to these standards as part of the Gaia DAO Code of Conduct, with additional opt-in requirements.

This update provides clear guidelines for governance delegates and enhances transparency in the Gaia Governance system.

Commit a08b9644ba87f64e6e05ae4cd8fe5a32687a35e2

The key changes in this GitHub Pull Request include:

  1. Adding a new note about the Gaia Delegate Standards.

  2. Updating the sidebar_position for a specific section in the documentation to 1.

  3. Changing the subject of the patch from "[PATCH 071/112] change/note" to "[PATCH 071/112] change/delegate-standards".

Commit a322203339c313824505dd2b1296cb7d615cb99b

The patch updates the governance documents for Gaia by replacing outdated links with current information. Specifically, it changes the "Links" section to direct users to the Governance Forums instead of individual contracts and documents. Additionally, the "Primary Goals and KPIs" section now mentions specific gaianet communities and stakeholders to whom the proposals impact, enhancing the transparency of governance initiatives.

Commit c1ce4bce73fc898892a53fe1bc02fc623062151e

The main change in this PR is an update to the "Forum/category.json" file within the "docs/governance/" directory. The description of the category has been updated from "Links, Gaia DAO Mission, Contract Addresses, and more." to simply "This page is a simple link to the governance forums." This change likely reflects changes in content or structure within the forum section of the documentation.

Commit 86f45784a2fd6f9a68a128199f9afe690ea5de7c

The patch updates the _category_.json file within the Gaia DAO's governance documentation, specifically focusing on the "Legal" section. The primary change is to rephrase the description from "Links, Gaia DAO Mission, Contract Addresses, and more." to "Legal information regarding the Gaia DAO." This change provides a clearer and more accurate description of what is contained in the section.

Commit 9c20b61abc15dd6ef7d535a7dc75d34cfdfbd3a0

-This pull request introduces a section on how to become a delegate, including steps for creating a profile on the Governance Forum, registering through Tally, and posting your Full Statement. It explains that delegates can choose from eight Focus Areas for governance-related focus areas, with no binding nature to ensure work cohesion among the delegate body.

Commit d6772a7ce3074540573ba0217525ea751888c1a4

Key Changes:

  1. Documentation Update: Added an updated guide on how to become a delegate, including steps for creating a profile and registering through Tally.
  2. Tally Integration: Integrated Tally, the third-party governance platform, into the process.
  3. Focus Areas: Added eight focus areas specifically tailored for Gaia DAO governance, facilitating delegate alignment with different aspects of governance.
  4. Forum Cross-Posting: Required delegates to post their Full Statement on the governance forum after registration through Tally.
  5. Documentation Structure: Enhanced the structure and clarity of the documentation for better navigation and understanding.

Commit 7a44e723d1f023fe729a0e64ced804f967e9af3a

Key Changes:

  1. Voting period: From 7 days to [placeholder] days
  2. Quorum requirement: Increased from placeholder GAIA to a simple majority (casted votes without considering abstentions)
  3. Source of information: Updated the proposal's source from Tally to the block explorer

Commit dd21a46715beab6fb14c74a696e96172a1310395

-This GitHub patch updates the docs/governance/Voting/onchain-voting.md file with a placeholder for the voting period duration. The original text stated that the Voting Period would be [placeholder days], and it was followed by instructions on how to vote and what conditions must be met for the proposal to pass. The patch replaces this placeholder with the actual number of days specified in the comment block at the beginning of the file.

Commit 2f300269dc64249e2f076e9bc114b5aed7e8b948

Key Changes Summary

  1. Vote Delay Period: The Vote Delay Period was originally set to 3 days, but is now placeholder.
  2. Voting Period: The Voting Period is also a placeholder and does not specify the exact number of days (7).
  3. Timelock Period: The Timelock Period is now placeholder and requires a minimum delay of 3 days.
  4. Proposal Threshold: The Proposal Threshold is a placeholder and needs to be specified.
  5. Quorum: The Quorum is a placeholder and needs to be specified.

Additional Considerations

  • These placeholders need to be replaced with concrete values or GIPs related to the governance process.
  • The voting parameters should align with best practices for governance processes and community consensus.
  • The update is crucial for maintaining transparency and accountability in the governance structure.

Commit cc51421d21b29ec31d277bdcd0863174a78fe8d1

This patch updates the governance procedures for a blockchain platform, changing the length of the Vote Delay period to [placeholder] days and adjusting the Timelock period as necessary. The voting parameters have also been updated to reflect changes in the governance process.

Commit 00d141e8d3531e9dd30e5bc6543ddf54c28f4d29

  • This patch updates the governance document on the Gaia Security Council, providing a detailed description of its responsibilities and the powers it has under the Foundation's multi-sig wallet.
  • It specifies that the council consists of [amount] committee members, who are signers on a specific foundation multi-sig wallet.
  • The council is responsible for upholding the Gaia DAO Mission and executing any emergency actions as necessary.
  • The Security Council can pause functionality or perform other required actions without delay in response to a security emergency.

Commit 306e6c0184478bf3a407bb8717a273e69335054c

The key changes in the GitHub Pull Request are as follows:

  1. Updated the "Focus Areas" section to include eight specific areas for governance.
  2. Added a brief description of each Focus Area to explain its purpose and relevance to Gaia.
  3. Clarified that these Focus Areas are not binding but rather help guide delegates' work within the governance body.
  4. Improved the structure of the document by organizing the information more logically.
  5. Updated the "Step 3" section to specify how to cross-post the Full Statement to the governance forum.

Commit a37fe839f3f1f79b356242e814d8896f18c4f0be

-This patch updates the governance documentation for GaiaNet. The main changes include:

  • Updating the Welcome page to introduce Gaia DAO and its mission.
  • Adding new sections on the Gaia DAO's Core Mission, Core Mandates, and objectives.
  • Refining the KPIs related to security, resource sustainability, and community engagement.
  • Providing guidance on how governance proposals should be defined and evaluated based on the goals of each initiative.

Commit 4bac3eff998ffbaec929393f93b11a60690b9a8d

The key changes in this Pull Request include the addition of a new section on definitions, which outlines various governance-related terms and concepts. The sections have been updated to ensure clarity and consistency across the documentation.

Commit 66f817afa438a4a2c3ee0e99316450d6707385c4

The following summary captures the key points from the GitHub patch:

  • A new file named mission.md is added to the Governance directory under the docs/governance/ folder.
  • The sidebar_position meta tag is updated in this markdown file to position it as the third sidebar item.
  • A change was made to a line within the mission.md file, from "# Mission" to "# Core Mission", indicating that the core mission now appears in the sidebar.

This patch introduces a new section on the governance documentation, focusing on the core mission of the Gaia DAO.

Commit d1c02bd55a00a9b6171dae38076d6327f34a64d2

The main changes in this Pull Request are:

  • Removed the "Gaia Security Council" and its powers, as it is now merged into the Delegates.
  • Changed the description of the Delegates to reflect their role as governance participants who may propose or vote on proposals.
  • Added a new section titled "Vetoes of proposals under emergency circumstances."

Commit 5c0b8299fc3dfcdbf19b0f82f167676703a401ba

The key changes in this PR include:

  • A table was added to outline the accountability for Gaia DAO and its relationship to other entities within the ecosystem.
  • It clarifies that Gaia DAO operates within a defined scope of work, including governance, procurement, treasury management, and technical advisory roles.

Commit c0aab462e6f3e09337f0a0129532229f934c505f

Key Changes Summary

1. Governance Procedures:

  • Governor Contract: The Governor contract is responsible for executing GIPs, allowing Delegates to vote on them using GAIA tokens.
  • Timelock Contract: A Timelock contract ensures that proposals are executed only after a specified period (7 days) from submission.

2. Gaia Improvement Proposals (GIPs):

  • The GIP template and discussion period are now explicitly defined, with a 7-day Discussion Period and potential signal voting.
  • Early feedback is encouraged through offchain voting to gain insights into proposal acceptance and areas for improvement.

These changes aim to enhance the governance structure of the Gaia DAO by providing a clear path for proposals to be reviewed and executed.

Commit 55492d16bd7a4851f7a44236648786e61abfc4f1

Key Changes:

  1. Added the security council charter, version 0.1.
  2. Updated page content to reflect this new information.
  3. Ensured the sidebar position is set to 9 for better visibility in the documentation.

This patch adds crucial governance documentation and updates related page contents for clarity and accessibility.

Commit 9b9befa5e4050bdb1d9ff7d21803324151df945a

The key changes in the patch include updating the GitHub URL for the Code of Conduct file, removing a redundant reference to Mission, and adding a new section about managing violations. The update focuses on improving the readability and relevance of the code of conduct while maintaining its alignment with the Gaia DAO's core mission.

Commit f66852d4cb53750f04f2632417446670f51be603

-The key changes include updating and organizing the governance forum by creating separate categories for delegate statements, guides & documentation, voting reminders & updates, proposals discussion calls, governance reporting calls (GRC), DAO finances, governance platforms, and adding links to help new users get started. The forum now features pinned posts to provide quick access to important information and resources.

Commit ba30e31541184dbe01576fd7b66321c234935804

Here are the key points from the summary:

  1. The Security Council is an emergency committee with 3-of-5 member approval for important actions.
  2. Its members are selected by tokens or a snapshot vote and must comply with certain conditions before being elected.
  3. It operates differently during normal operations than in emergencies, evaluating proposals without immediate governance approval.
  4. Members can only be removed if GIPs are passed or 3 Security Council Members agree.
  5. The council has a transparent election system, and members are required to declare their candidacy publicly.

Commit 4f0d548e382ad3e58aa0ec8a38c4578636d926ce

-Key Changes:

  1. Updated Step 6a in the governance procedure document.
  2. Replaced "Step 6b: Voting Power" with a new step, "Step 6a: Voting Power."

Commit 47c51e561065fce6f0b2f384fa2bd2b304217395

  • The patch updates the governance framework of GaiaNet by clarifying and updating various entities involved in its management.
  • Gaia Foundation is now an entity established to set high-level vision & strategic goals, enter legal agreements, and ensure compliance. It also serves as a grant program manager and ratifies the budget.
  • Gaia Labs has become the development company of Gaia, responsible for building and maintaining protocol infrastructure and provides integration support for ecosystem programs.
  • The core mission of the DAO is to increase developer adoption and foster the expansion of the AI token economy.
  • The DAO's mandate includes governance of the ecosystem, establishment of token strategy (e.g. DEX selection), procurement of service providers, and managing the Gaia Treasury and various community-driven initiatives with said treasury.
  • The governance system provides access control logic through the Governor role to process proposals and their associated votes in order to determine whether they succeed or fail.

Commit 6c3f9a8fb652daf8f8ae20203dbb65e80629cd18

Key Changes Summary

  • The document has been updated to provide a clear and concise overview of the Gaia Network governance process.
  • The links provided have been expanded to include https://www.tally.xyz/gov/gaianet/delegates for voting power delegation.
  • The Gadia Github repository address is now displayed as https://github.com/GaiaNet-AI.
  • A new section "Key Results" has been added, outlining the governance milestones and responsibilities.

Commit df9edc30ce0da3b5d5e6cfbafe06bf9b760b12ad

This patch updates the delegation documentation to point directly to Tally.xyz's delegation page, removing the need for an intermediary "this page" link.

Commit 0aadebdaf1dab033b8ecc6240c5905f3cce4be20

-The patch updates the how-delegation-works.md file by providing instructions on how to delegate token voting power in the Gaia DAO governance platform. It highlights key points such as registration on Tally, delegation types, and cross-posting statements to the governance forum.

Commit 84e889780df61dac01b010f9238b6c3cea36b930

-This patch modifies the GitHub PR for "Boardroom-governance-docs" to update the link in a file titled docs/governance/Delegation/why-its-important.md from referencing the governance forums directly to providing a direct URL to the Delegate statement template in instructions.

Commit 762ff9da3b9ddd0797457b6f6ce4f7517d9a3a5d

The key changes in this Pull Request are:

  1. The link for accessing the Tally link is updated to a more official address (https://www.tally.xyz/gov/gaianet/delegates) from Tally link on the initial draft.
  2. The updated Tally link includes relevant context related to governance and delegation, providing clarity and direction for users.

Commit 268606f716c151dfb89af9104d1b91d32ab09177

Key Changes Summary:

  1. Documentation Update: The documentation for the Gaia governance portals has been updated.

  2. Link Correction: A link to the Gaia Tally Governance Portal has been corrected from [link] to <https://www.tally.xyz/gov/gaianet/delegates>.

  3. File Path: The file path for the governance portal documentation has been updated from docs/governance/Voting/governance-portals.md to docs/governance/Voting/governance-portals.md.

  4. Sidebar Position: The sidebar position for this documentation section remains unchanged as 1.

This update ensures that users can easily find and access the latest information about the Gaia governance portals.

Commit 66076c53eef7e9fcd07e9f10c3b3de5b4f02a413

This patch updates the onchain voting documentation for the Governance Portal and provides additional resources to help users understand delegation and the proposal lifecycle.

Commit 40c7c92fb8b9e5aaf0b350d34d363d6fd30d3c9c

-This Pull Request modifies the "snapshot.md" file in the docs/governance/Voting directory. It changes the link from [Tally link] to [Tally](https://www.tally.xyz/gov/gaianet).

Commit f6d5b1a206126a2f6fe4223a36d40744afa8964f

  • The patch introduces several changes to the voting parameters for Tokenholders, including:
    • Changing the Vote Delay Period from 1 day to 3 days.
    • Changing the Voting Period from 1 day to 7 days.
    • Adjusting the Proposal Threshold to be set after TGE, and adjusting the Quorum to also be set after TGE.

Commit 84e3acb976b2a9c4b8ade719e03dcae440c50e96

The key changes in this patch are:

  • The voting period has been changed from 14 to 7 days.
  • The proposal threshold and quorum have been set after the token generation event (TGE).
  • The Timelock period has been shortened from 28 to 3 days.

Commit b997c5c5b9feb034487f7e2dc0c028223d5c35f9

Key Changes Summary:

  1. Proposal Submission Threshold: The proposal submission threshold for onchain voting is now [placeholder] GAIA.
  2. Voting Period Extended: The voting period from the discussion period to onchain submission has been extended from 7 days to 7 days.
  3. Timelock Period Length: The Timelock period length has been changed from a minimum delay of [placeholder] days to a minimum delay of three days.

These changes aim to enhance governance by providing more flexibility and transparency in proposal submission and execution, aligning with the goal of fostering community-driven decision-making.

Commit 09a9f6c6fb7f85debafe909cfb4c3657bc6dcb3b

The patch updates the Governance section of the Gaia Security Council Charter documentation. Specifically, it adds a link to the v0.1 version of the Charter.

Commit b369ab8271ade65357d6b7d69cd03943a5f92f26

-This GitHub patch introduces a minor change to the code of conduct document in the code-of-conduct.md file. The patch removes an extra space before the closing parenthesis after mentioning "Gaia DAO Core Mission" in the document title.

Commit ac0f853dde15535be8c779c78e82d5695cb9a460

The main changes in the pull request are:

  1. The Gaia Governance Portal link is updated to use https://www.tally.xyz/gov/gaianet.
  2. The Gaia Forum link is updated to be <gov.gaianet.foundation>.

These updates improve the clarity and reliability of the links in the code of conduct.

Commit 4489a896a1ce3cf52edc277c4a0026a3bf986099

  • The patch updates the Code of Conduct for the Gaia community. It now includes a new link to the Gaia Forum, which is now accessible at https://gov.gaianet.foundation.

Commit d41c98c9927b1359424961fbae4417002aec1837

Key Changes:

  1. Added a link to the Gaia DAO Governance Forum on the forum.md file.
  2. Updated the URL for the forum landing page in the Welcome to Gaia DAO Governance post to reflect the new governance platform.
  3. Removed redundant instructions on how to customize your profile from the Welcome to Gaia DAO Governance post, as it is now available directly under the pinned post.
  4. Simplified the navigation menu on the forum.md file, removing unnecessary sub-categories and links.
  5. Updated the GIP template link to point to a new governance platform URL.
  6. Removed instructions for becoming a delegate from the Welcome to Gaia DAO Governance post, as it is now available directly under the pinned post.
  7. Simplified the category structure on the forum.md file, removing unnecessary sub-categories and links.
  8. Updated the GIP template link to point to a new governance platform URL.

Commit 03a425556619cbea0b870194118327fe50862db4

Key changes include:

  1. Adding disclaimers about legal obligations and risks.
  2. Clarifying the role of governance parties and their responsibilities.
  3. Providing details on multijurisdictional control mechanisms.
  4. Discouraging reliance on third-party documents.
  5. Updating the content disclaimer section for accuracy and completeness.

Commit 34e467d1ad4d4d2558281441f80d3392c5505b4f

The key changes in this pull request include:

  • Adding a section on "Legal" within the governance documentation.
  • Providing details about the Gaia Network governance procedures, including disclaimers and disclosures related to governance processes.
  • Recommending that users carefully study smart contracts and code for understanding potential risks and uncertainties.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants