> For the complete documentation index, see [llms.txt](https://poolsag.gitbook.io/pools.ag-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://poolsag.gitbook.io/pools.ag-docs/governance-dao.md).

# Governance (DAO)

## Governance — pools.ag Platform Governance

### Decentralized Governance at pools.ag

[**pools.ag**](https://pools.ag/) **is a next-generation liquidity pool aggregator designed to simplify access to decentralized finance (DeFi) opportunities.**

Our governance philosophy is built on the principles of decentralization, transparency, accountability, and community participation.

We believe that the development of decentralized financial infrastructure should reflect the interests of users, liquidity providers, developers, and other ecosystem participants.

To expand community involvement in the development of pools.ag, a decentralized autonomous organization (DAO) governance model is envisioned, with the **POOL** token playing a central role.

Under this model, POOL holders will be able to participate in proposal discussions, vote on important matters, and help determine the platform's strategic direction.

### How Is pools.ag Governed?

The proposed pools.ag governance model involves collaboration between POOL token holders, the community, and the core development team.

Key decisions may be submitted to POOL holders for voting, including:

* Integrating new blockchains, decentralized exchanges, and DeFi protocols.
* Developing the liquidity pool aggregator and expanding its functionality.
* Modifying the platform's economic model and fee structure.
* Allocating funds for ecosystem development.
* Financing developers, community contributors, and new initiatives.
* Developing new products and technological solutions.
* Establishing strategic partnerships and expanding the ecosystem.
* Modifying decentralized governance mechanisms.

The pools.ag core team is responsible for day-to-day platform operations, technical infrastructure, protocol integrations, security, and the implementation of approved decisions.

The strategic objective of this governance model is to progressively expand community participation in decision-making.

### The POOL Token and Its Role in Governance

**POOL is a token intended to enable participation in the governance of the pools.ag ecosystem.**

Under the proposed governance model, POOL holders will have the opportunity to influence the platform's development through voting and submitting their own proposals.

The proposed functions of the POOL token include:

* Voting on community proposals.
* Submitting initiatives to improve pools.ag.
* Participating in determining the project's strategic priorities.
* Delegating voting power to other participants.
* Influencing decisions regarding funding for ecosystem initiatives.
* Participating in discussions about changes to DAO governance mechanisms.

Voting power may be determined by the number of POOL tokens held by a participant, in accordance with the approved governance rules.

This model aligns governance participation with token holders' long-term interest in the ecosystem's development.

### How Can I Participate in Governance?

Participation in pools.ag governance is expected to take place through a community proposal and voting system.

POOL token holders will be able to review initiatives related to the platform's development and express their opinions on matters submitted for voting.

The main participation steps include:

1. Connecting a personal cryptocurrency wallet to the governance interface.
2. Reviewing published proposals.
3. Evaluating the objectives, conditions, and potential consequences of proposed changes.
4. Selecting a preferred voting option.
5. Confirming the vote using a cryptocurrency wallet.

Once voting concludes, the results may be used to determine the next steps for the team and community.

Specific participation requirements, including the minimum number of POOL tokens required to submit proposals, must be established in the official governance rules.

### How Does Voting Work?

Snapshot or a similar decentralized voting system may serve as the technological foundation for the DAO.

Such solutions enable blockchain-based voting without requiring separate paid transactions for each vote.

A potential voting process includes:

**Proposal Submission.** An eligible participant publishes an initiative describing the proposed changes.

**Community Discussion.** The community reviews the proposal, discusses its benefits, potential risks, and alternative solutions.

**Voting Publication.** Following preliminary review, the proposal is submitted for voting.

**Voting Power Determination.** The system records the number of POOL tokens eligible to be counted toward each participant's voting power.

**Voting.** Token holders select one of the available options.

**Result Calculation.** Results are determined according to the approved vote-counting rules.

**Implementation.** An approved proposal is assigned to the relevant ecosystem contributors for execution.

### What Types of Voting Are Available?

The pools.ag DAO governance model may support several voting mechanisms.

#### Basic Voting

Participants choose one of the following options:

* Approve the proposal.
* Reject the proposal.
* Abstain.

The outcome is determined according to the established majority and quorum requirements.

#### Single Choice Voting

Participants select one option from several proposed alternatives.

The option receiving the highest level of support wins, subject to the DAO's governance rules.

#### Weighted Voting

Participants can distribute their voting power across multiple options.

The weight assigned to each option depends on the allocation of voting power.

#### Quadratic Voting

This mechanism is designed to reduce the concentration of influence among large token holders.

A nonlinear mathematical model is used to calculate voting power.

#### Ranked Choice Voting

Participants rank the available options in order of preference.

Votes are counted according to preference rankings and the applicable vote redistribution rules.

The selection of a particular voting mechanism depends on the nature of the proposal and the approved governance framework.

### Vote Delegation

Delegation allows POOL holders to assign their voting power to selected community representatives.

This mechanism is particularly useful for participants who want to influence the platform's development but do not have enough time to review every proposal individually.

Delegation may involve:

* Selecting a trusted representative.
* Assigning voting power within the governance system.
* Allowing the representative to vote using the delegated authority.
* Maintaining ownership of the tokens with their original holders.

**Delegating voting power does not always require transferring POOL tokens to another user.**

The procedures for modifying or revoking delegation depend on the technical implementation of the governance system.

### Who Can Become a Delegate?

Under the DAO model, any participant who meets the established requirements may become a delegate.

Delegates represent the interests of POOL holders who have entrusted them with their voting power.

To promote transparency, delegates are encouraged to publicly disclose their priorities, proposals, and voting history.

This allows token holders to select representatives whose views align with their interests.

### How Is Voting Power Calculated?

A participant's voting power may be determined by the number of POOL tokens they hold.

When Snapshot is used, the system can record the blockchain state at a specific block.

The number of tokens eligible for voting is determined at the time of the corresponding blockchain snapshot.

This approach establishes each participant's voting power for a particular proposal in advance.

The final calculation methodology, including rules for delegated tokens and potential restrictions, must be defined in the DAO governance parameters.

### What Is a Voting Quorum?

A quorum is the minimum level of participation required for voting results to be considered valid.

It helps prevent situations in which a small group of participants can make important decisions on behalf of the entire community.

For example, DAO rules may establish a minimum percentage of total voting power that must participate in a vote.

If the required threshold is not reached, a proposal may be considered unsuccessful regardless of how the votes are distributed.

Quorum requirements, voting periods, and decision-making thresholds must be defined in the official pools.ag governance rules.

### How Do I Submit a Proposal?

The pools.ag governance system may allow POOL holders to independently publish proposals.

A proposal should include:

* The title of the initiative.
* A detailed description of the proposed changes.
* An explanation of why the changes are necessary.
* Expected benefits for the platform and community.
* Potential technical, economic, and organizational risks.
* Proposed voting options.
* An estimated implementation timeline.

Depending on the scope of the initiative, additional information may be required, including a budget, technical documentation, and an implementation plan.

Proposals should be sufficiently detailed to allow participants to make informed decisions about their potential consequences.

### DAO Proposal Categories

The pools.ag governance model may include several categories of proposals.

#### Pool Improvement Proposals (PIPs)

Proposals focused on improving the platform.

These may address the user interface, integrations, analytics, security, liquidity provision mechanisms, and other technical components.

#### Community Signaling Proposals (CSPs)

Advisory votes intended to determine community sentiment on various matters.

Such proposals may be non-binding but can help evaluate support for initiatives before implementation.

#### Ecosystem Funding Proposals (EFPs)

Proposals requesting funding for development, research, infrastructure improvements, and ecosystem projects.

#### Grant Proposals

Applications for grants to support initiatives that contribute to the development of pools.ag.

Grant programs may support developers, researchers, educational projects, and other activities aligned with the ecosystem's objectives.

#### Governance Improvement Proposals (GIPs)

Proposals aimed at improving the governance system itself.

These may address voting procedures, quorum requirements, delegation mechanisms, and proposal review processes.

### How Do We Protect Against Malicious Proposals?

An open governance system should include mechanisms designed to protect the platform and its users from potentially harmful actions.

Special attention may be given to proposals that:

* Create security risks for the platform's infrastructure.
* Involve unauthorized access to user assets.
* Violate established governance rules.
* Include technically impossible requirements.
* Do not provide sufficient time for discussion.
* Are ambiguous or lack adequate detail.
* Attempt to manipulate voting procedures.

Review and moderation mechanisms should be transparent and must not be used to unjustifiably restrict community participation.

### Governance of Protocol Integrations and Liquidity Pools

One of the most important areas of pools.ag development is the integration of new decentralized exchanges, blockchain networks, and liquidity pools.

Potential integrations are evaluated based on:

* Protocol architecture and technical compatibility.
* Available liquidity.
* Trading volumes and economic activity.
* Protocol operating history.
* Known vulnerabilities and security assessment results.
* Smart contract and infrastructure reliability.
* Quality of available market data.
* Potential benefits for pools.ag users.

Community members may suggest new integrations and express their opinions regarding the platform's development priorities.

However, the inclusion of a protocol or liquidity pool in the aggregator does not guarantee its security or profitability.

### Dynamic APR and Market Data Transparency

One of the key technological features of pools.ag is its **Dynamic APR** model.

Current APR is dynamic and changes in real time based on market conditions, trading volume, liquidity, and transaction fees.

The platform analyzes available decentralized market data and provides users with up-to-date estimates of potential returns.

Developing analytical infrastructure, improving data accuracy, and enhancing the Dashboard are important areas of the project's ongoing development.

Community members may propose improvements to analytical tools, metric visualization, and position management functionality.

### Non-Custodial Architecture and Security

**pools.ag operates using a non-custodial model for cryptocurrency asset management.**

Users connect their own cryptocurrency wallets and independently authorize blockchain transactions.

The platform does not request private keys, passwords, recovery seed phrases, or other confidential cryptocurrency wallet information.

Key security development priorities include:

* Monitoring the technical reliability of integrations.
* Analyzing risks associated with supported DeFi protocols.
* Strengthening infrastructure security.
* Identifying potential vulnerabilities.
* Improving risk management mechanisms.
* Informing users about significant technical changes.

Although non-custodial architecture reduces reliance on centralized asset custody, it does not eliminate smart contract risks, market volatility, or the possibility of financial losses.

### The Future of Decentralized Governance at pools.ag

Our long-term objective is to develop a transparent and sustainable governance system in which the community can take a more active role in shaping the platform's future.

The POOL token is envisioned as a key component of the proposed decentralized governance system.

As the ecosystem evolves, additional mechanisms for voting, delegation, initiative funding, and the distribution of governance authority may be introduced.

The implementation of a DAO should be accompanied by the publication of technical documentation, voting parameters, and official participation rules.

Until these mechanisms are formally launched, community proposals remain advisory, while operational responsibility stays with the pools.ag core team.

### Building the Future of DeFi Together

We believe that the sustainable development of decentralized finance requires transparent governance, technological innovation, and active community participation.

pools.ag aims to combine advanced liquidity aggregation technologies, convenient position management tools, and opportunities for users to participate in ecosystem development.

Our mission is to make DeFi simpler, more accessible, and more efficient while preserving the fundamental principles of decentralization and user control over digital assets.

**One Platform. A World of Decentralized Liquidity Opportunities.**

[**pools.ag**](https://pools.ag/) **— The Next-Generation Liquidity Pools Aggregator.**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://poolsag.gitbook.io/pools.ag-docs/governance-dao.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
