> For the complete documentation index, see [llms.txt](https://liq-3.gitbook.io/stake.liq/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://liq-3.gitbook.io/stake.liq/token-guides/governance.md).

# Governance

LiQ’s Governance structure is designed to be a decentralized, transparent, and participatory framework that empowers $LIQ token holders to shape the protocol’s evolution. As a DeFi-native liquid staking protocol, LiQ requires robust governance mechanisms to manage its staking infrastructure, DeFi strategy allocations, liquidity incentives, treasury funds, and long-term sustainability.

The governance framework operates through a DAO where $LIQ holders have the ability to propose, vote, and implement changes to the protocol. With a hierarchical governance structure, on-chain voting mechanisms, and a multi-sig controlled treasury, LiQ ensures that the decision-making process remains transparent, democratic, and resistant to centralization.

### Governance Model Overview

LiQ follows a progressive decentralization model, transitioning from initial foundation control to full community-driven governance as the protocol matures. Governance operates on a token-weighted system, where $LIQ holders determine key protocol parameters and strategic decisions.

Governance Layers & Roles

$LIQ Token Holders (General DAO Members)

* The core governance participants, responsible for voting on proposals.    &#x20;
* Stakeholders who hold $LIQ can participate in governance.    &#x20;
* Their voting power is proportional to the number of $LIQ tokens staked in the governance contract.

### Governance Proposal & Voting Mechanism

LiQ governance operates through a structured on-chain proposal system, ensuring that protocol upgrades, economic policies, and treasury decisions are made transparently and democratically.

Proposal Lifecycle & Submission Process    &#x20;

* Proposal Creation    &#x20;
* Any $LIQ holder meeting the minimum token threshold can submit a governance proposal.        &#x20;
* Proposals must be structured, detailed, and contain clear execution parameters.    &#x20;
* A preliminary discussion phase on the governance forum ensures community feedback before formal submission.         &#x20;

On-Chain Voting    &#x20;

* The proposal is published on-chain, and $LIQ holders vote via the governance contract.    &#x20;
* Voting power is determined by staked $LIQ balances at the snapshot block.    &#x20;
* Voting Period: Typically 5-7 days, ensuring fair participation.    &#x20;
* Quorum Requirement: A minimum percentage of total $LIQ supply must participate for a vote to be valid.    &#x20;

Voting Outcomes:    &#x20;

* Yes → Proposal moves to execution.    &#x20;
* No → Proposal is rejected and cannot be resubmitted immediately.

Proposal Execution    &#x20;

* If approved, the Governance Council (multi-sig) executes the decision.    &#x20;
* Some changes require timelock delays before implementation to prevent governance attacks.

Voting Power & Delegation    &#x20;

* Token-Weighted Voting: Governance power is directly proportional to the number of $LIQ tokens held and staked in the governance contract.    &#x20;
* Delegation System: Users can delegate their voting power to trusted representatives who participate in decision-making on their behalf.    &#x20;
* Quadratic Voting (Future Implementation): To balance governance influence, quadratic voting may be introduced, preventing large holders from dominating the vote.

### Key Governance Decisions & Control Parameters

LiQ governance oversees all major protocol decisions, ensuring that community stakeholders control key parameters affecting staking rewards, DeFi strategy allocations, and treasury management.

Governance-Controlled Parameters    &#x20;

1\.  Protocol Fees & Revenue Allocation    &#x20;

* Adjusting protocol performance fees and revenue distribution mechanisms.    &#x20;
* Deciding how revenue from DeFi yield strategies is allocated to staking rewards, treasury reserves, and buyback programs.    &#x20;
* Staking & Yield Strategy Management    &#x20;
* Determining how MNT deposits are allocated between lending, yield farming, cross-chain strategies, and vaults.   &#x20;
* Adjusting stMNT reward rates and incentives for liquidity providers.    &#x20;

2\. Treasury & Liquidity Fund Allocation    &#x20;

* Managing treasury reserves, liquidity mining programs, and ecosystem grants.    &#x20;
* Funding new partnerships, cross-chain expansions, and research initiatives.    &#x20;

3\.    Protocol Security & Risk Management    &#x20;

* Approving security audits and implementing safety measures to protect stMNT and governance funds.    &#x20;
* Authorizing emergency actions in case of an exploit.   &#x20;

4\.   Tokenomics & Emission Adjustments    &#x20;

* Adjusting $LIQ staking emissions to ensure sustainable long-term token distribution.    &#x20;
* Implementing buyback & burn mechanisms to support $LIQ price stability.

### Treasury Management & Fund Allocation

LiQ’s governance oversees a decentralized treasury, ensuring that funds are used efficiently for protocol growth and sustainability.

Treasury Composition & Revenue Sources    &#x20;

* Protocol Fees: A portion of yield farming, lending, and cross-chain strategy profits.    &#x20;
* Liquidity Incentives: Funds allocated to DEX trading pairs & liquidity providers.    &#x20;
* DAO Reserve Funds: A governance-controlled treasury used for ecosystem expansion & security grants.

Treasury Fund Utilization    &#x20;

* Liquidity Incentives (stMNT/MNT pairs) – Ensuring deep liquidity for efficient trading.    &#x20;
* Ecosystem Development & Grants – Funding DeFi integrations, developer bounties, and research projects.    &#x20;
* Security & Audits – Allocating funds for ongoing smart contract audits and risk mitigation measures.

### Governance Security & Safeguards

Governance Attack Prevention Measures    &#x20;

* Timelock Delays: Critical proposals require a 48-hour timelock before execution, preventing flash governance attacks.    &#x20;
* Multi-Sig Execution: Governance proposals must be approved by multi-sig signers, ensuring decentralized oversight.    &#x20;
* Emergency Pause Mechanism: A failsafe allowing the Security Council to temporarily halt protocol functions in case of an exploit.

### Long-Term Decentralization Roadmap

As LiQ evolves, governance will progressively transition from foundation-led oversight to full DAO control.   &#x20;

* Phase 1: Governance begins with multi-sig execution & community voting.   &#x20;
* &#x20;Phase 2: Staking rewards & treasury management shift to fully decentralized control.    &#x20;
* Phase 3: Full on-chain execution of proposals, removing reliance on manual execution.

Conclusion

LiQ’s governance model is built for decentralized, transparent, and community-driven decision-making. Through on-chain voting, treasury oversight, and protocol governance, $LIQ holders play a direct role in shaping the future of liquid staking, DeFi integrations, and ecosystem expansion. With structured proposal mechanisms, secure execution frameworks, and progressive decentralization, LiQ governance ensures long-term protocol sustainability and alignment between stakeholders.


---

# 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, and the optional `goal` query parameter:

```
GET https://liq-3.gitbook.io/stake.liq/token-guides/governance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
