> For the complete documentation index, see [llms.txt](https://docs.ichi.org/legacy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ichi.org/legacy/developers/core-technical-concepts/governance.md). # Governance Within the ICHI system we divide governance into two sections based on scope of authority. Both sections rely on the same voting code (in separate instances) that enables voting rights based on tokens staked. The sections are divided into: 1. Global (ICHI) Governance 2. Local/Instance (oneToken) Governance ## ICHI Governance ICHI Governance is the system’s overall governance which we refer to as “global”. It is the highest level of authority and thus has the largest scope. It provides boundaries inside of which the oneToken Governance instances can function to govern their oneToken community-backed Collateral and Treasury. ICHI Governance is responsible for admission control as it pertains to: 1. Accepting the creation of a new oneToken species, its initial configuration and its corresponding Community Governance contract. 2. Adding a new Collateral Token to the list of “like kind” Collateral Tokens available in the Collateral Reserve for oneToken holders. 3. Adding and removing implementation versions. 4. Adding Oracle, MintMaster, Controller, and Strategy implementations. ### Key components include 1. **Versions:** oneToken implementations. 2. [**Oracles**](/legacy/developers/core-technical-concepts/oracles.md)**:** Price aggregators for each token in the Community Treasury and Collateral. 3. [**MintMaster**](/legacy/developers/core-technical-concepts/mint-masters.md)**:** sets the Minting Ratio. 4. [**Collateral Tokens**](/legacy/developers/core-technical-concepts/collateral-tokens.md)**:** USD hard pegged stablecoins accepted and emitted in the Minting and Redemption processes. 5. [**Strategies**](/legacy/developers/core-technical-concepts/strategies.md)**:** Modular contracts purpose-built for deploying Collateral and Community Treasury funds. ### Deployments ICHI Governance also deploys oneToken implementations. It does so by specifying an initial configuration from the available predetermined options. This is done through the following steps: 1. ICHI Governance includes the initial oneToken configuration and instructs the oneToken Factory to deploy a new oneToken contract. 2. The oneToken Factory (owned by the ICHI Governance contract) validates the input including confirmation that only a pre-approved implementation Version, Oracles and Collateral are specified. 3. The oneToken factory deploys the oneToken instance and the system of contracts is ready for service. ![Components used in deploying oneTokens](https://lh6.googleusercontent.com/UGw75KWk0J4KLSXZHZ8FwvigoxJ0EMzBmTsghs5RdaVN2TECYVNbjAD10-uYp8GoqpWGj4tK1V9VFQ-QeKP8FhyZMRAm3jTma6RLqd2llRWJ0qgv4e8OlWU9iiGJctrnWSRbDMgH) ## oneToken Governance oneToken Governance is akin to local or community governance. Each oneToken instance has its own community-led governance with the ability to decide on customized implementations of system components that are whitelisted by ICHI Governance. oneToken Governance is implemented as an address which can be an EOA (Externally Owner Account), multisig, or on-chain governance contract capable of emitting bytecode. Important issues that oneToken governance deals with include: 1. Adjusting the Minting Minimum/Maximum or absolute Ratio for new minted oneTokens when using the Incremental implementation of the MintMaster, or working with other parameters chosen modules require. 2. Adjusting the type of Collateral used, e.g. change USDC to DAI or a combination of both. 3. [Executing Community Treasury operations](/legacy/developers/core-technical-concepts/governance/treasury-governance.md) {% hint style="info" %} Each oneToken is a vote on treasury allocations, specific stablecoins parameters (like minting and redeeming fees), and on adoption programs. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ichi.org/legacy/developers/core-technical-concepts/governance.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.