# Governance

## 7. Governance

### 7.1 Overview

Pinata Chain is governed by a decentralized, token-holder-based system that allows the community to participate in protocol upgrades, economic parameters, and ecosystem incentives through on-chain proposals and voting.

The governance model is designed to be:

* Transparent
* Accountable
* Extensible to AI Agent logic and treasury workflows

***

### 7.2 Governance Participants

| Role                      | Description                                                                      |
| ------------------------- | -------------------------------------------------------------------------------- |
| **PIN Token Holders**     | Can submit and vote on proposals based on staked PIN                             |
| **Validators**            | Execute validated proposals at the protocol layer                                |
| **DAO Treasury Multisig** | Manages community funds under proposal-driven execution                          |
| **AI Delegates (Future)** | Smart contracts or AI agents authorized to vote on behalf of users or strategies |

***

### 7.3 Voting Power

* Governance voting is weighted by **staked PIN** (not liquid tokens)
* Users must stake PIN to earn **governance power (gPIN)**
* Voting power decays if PIN is unstaked or delegated elsewhere
* In the future, **AI agents can be delegated gPIN** for autonomous strategy voting

***

### 7.4 Proposal Lifecycle

1. **Proposal Submission**:
   * Requires minimum stake threshold (e.g., 100,000 gPIN)
   * Proposal types: parameter change, funding, feature upgrade, agent registration
2. **Voting Period**:
   * 3–7 days
   * Snapshot-based vote count (based on gPIN at proposal start)
3. **Execution Phase**:
   * If quorum & majority achieved, proposal becomes executable
   * Validators or relayers trigger on-chain implementation
   * Treasury proposals trigger multisig execution flow
4. **Rejection / Lapse**:
   * Proposals with insufficient quorum or failed vote are archived
   * Spam mitigation via proposal bond (burned if rejected)

***

### 7.5 Treasury Governance

The DAO treasury holds:

* 15% of PIN supply
* Ecosystem growth funds
* Strategic grant allocations
* Emergency reserves

Treasury operations are governed by:

* On-chain voting → Proposal → Multisig trigger
* Public expenditure dashboard via Blockscout
* Quarterly treasury report and audit (open-sourced)

***

### 7.6 AI Agent Governance (Planned)

As AI Trading Agents become core components of Pinata, governance will extend to:

* **Agent Whitelisting / Registration**:
  * Prevent malicious or spam agents
  * Community vote required to enable public marketplace agents
* **Strategy Certification**:
  * Voting on safe / approved agent strategies for newcomers
* **Agent Ranking DAO**:
  * Token-curated registry of high-performing agents
* **Delegated Voting via AI**:
  * Allow agents to hold and exercise gPIN to vote on behalf of users

***

### 7.7 Security & Governance Safeguards

* **Time-delayed execution**: Critical changes have a mandatory delay window
* **Emergency veto**: Community-led pause vote if exploit suspected
* **Rate limits**: Max budget size, voting frequency caps
* **Proposal metadata hashes**: Ensure immutability and verifiability of content
* **Snapshot governance fallback**: In case on-chain logic fails or is attacked

***

### Summary

Pinata’s governance is more than token voting — it is a multi-layered system built for transparency, flexibility, and safe extension into AI-driven infrastructure.

As AI agents become strategic actors in on-chain finance, Pinata aims to pioneer **AI-participatory governance** — where intelligent systems, backed by user intent, can collectively shape the rules of decentralized economies.


---

# Agent Instructions: 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://pinatalabs-1.gitbook.io/pinatalabs-docs/governance.md?ask=<question>
```

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.