> For the complete documentation index, see [llms.txt](https://triple-plus-global.gitbook.io/tpt-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://triple-plus-global.gitbook.io/tpt-whitepaper/undefined/governance.md).

# Governance

## Current Operations

During the growth phase, the protocol operates with centralized governance:

| Aspect                      | Current Approach          |
| --------------------------- | ------------------------- |
| **Decision Making**         | Core team                 |
| **Smart Contract Upgrades** | Multi-sig controlled      |
| **Risk Parameters**         | Team with community input |
| **Treasury**                | Team managed              |

This ensures rapid iteration and response to issues while the protocol establishes product-market fit.

***

## Progressive Decentralization

{% @mermaid/diagram content="flowchart LR
P1\["Phase 1<br/>Team Governance"] --> P2\["Phase 2<br/>Token Voting"] --> P3\["Phase 3<br/>Full DAO"]

```
P1 -.- P1a["Centralized<br/>decisions"]
P2 -.- P2a["Community<br/>proposals"]
P3 -.- P3a["On-chain<br/>execution"]" %}
```

***

## Phase 1: Team Governance (Current)

| Aspect              | Implementation              |
| ------------------- | --------------------------- |
| **Decisions**       | Made by core team           |
| **Community Input** | Forums, Discord, feedback   |
| **Transparency**    | Public announcements        |
| **Multi-sig**       | 3-of-5 for contract changes |

### How to Participate Now

* Join Discord discussions
* Provide feedback on proposals
* Report issues and suggestions
* Participate in community calls

***

## Phase 2: Token Voting

| Aspect              | Implementation                 |
| ------------------- | ------------------------------ |
| **Proposal System** | Token holders submit proposals |
| **Voting**          | TPT-weighted voting            |
| **Quorum**          | Minimum participation required |
| **Team Veto**       | Reserved for security issues   |

### Proposal Process

{% stepper %}
{% step %}

### Discussion

Community discusses the idea.
{% endstep %}

{% step %}

### Draft

Formal proposal is written.
{% endstep %}

{% step %}

### Review

Team reviews feasibility.
{% endstep %}

{% step %}

### Vote

Token holders vote.
{% endstep %}

{% step %}

### Implementation

Team executes if passed.
{% endstep %}
{% endstepper %}

### Voting Parameters (Proposed)

| Parameter      | Value                  |
| -------------- | ---------------------- |
| Voting period  | 5-7 days               |
| Quorum         | \[TBD]% of staked TPT  |
| Pass threshold | >50% approval          |
| Time-lock      | 48 hours post-approval |

***

## Phase 3: Full DAO

| Aspect                 | Implementation                           |
| ---------------------- | ---------------------------------------- |
| **On-chain Execution** | Approved proposals execute automatically |
| **Treasury Control**   | DAO controls protocol treasury           |
| **No Team Veto**       | Community has final say                  |
| **Elected Councils**   | Specialized committees                   |

### DAO Structure (Vision)

{% @mermaid/diagram content="flowchart TB
TH\["Token Holders"] --> GOV\["Governance"]
GOV --> RC\["Risk Council"]
GOV --> TC\["Treasury Council"]
GOV --> DC\["Development Council"]

```
RC --> RP["Risk Parameters"]
TC --> TF["Fund Allocation"]
DC --> UP["Upgrades"]" %}
```

***

## Governance Scope

Token holders will eventually govern:

| Parameter           | Description                                | Phase   |
| ------------------- | ------------------------------------------ | ------- |
| **Fee Rates**       | Platform fees for listings and settlements | Phase 2 |
| **Risk Thresholds** | Exposure limits, debtor requirements       | Phase 2 |
| **Asset Classes**   | Approval of new asset types                | Phase 2 |
| **Treasury**        | Allocation of protocol revenue             | Phase 3 |
| **Upgrades**        | Smart contract modifications               | Phase 3 |

***

## Governance Principles

### Transparency

* All proposals public
* Voting results on-chain
* Discussion forums open

### Inclusivity

* Any token holder can propose
* Low barriers to participation
* Multiple discussion channels

### Security

* Time-locks on changes
* Emergency procedures
* Gradual rollout of powers

### Accountability

* Clear roles and responsibilities
* Regular governance reports
* Elected positions have terms

***

## Timeline

| Milestone               | Target  |
| ----------------------- | ------- |
| Phase 1 (Current)       | Now     |
| Community forums launch | Q1 2026 |
| Phase 2 voting begins   | Q3 2026 |
| DAO structure proposal  | Q4 2026 |
| Phase 3 transition      | 2027    |

{% hint style="info" %}
Governance timeline is subject to change based on protocol maturity and community readiness.
{% 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, and the optional `goal` query parameter:

```
GET https://triple-plus-global.gitbook.io/tpt-whitepaper/undefined/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.