> For the complete documentation index, see [llms.txt](https://paragon-protocol.gitbook.io/paragon-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://paragon-protocol.gitbook.io/paragon-protocol/governance-and-tokens/governance-voting.md).

# Governance (Voting)

### TL;DR

* anyone can vote (subject to thresholds)
* proposals are public
* results are enforced via timelock
* governance evolves from Points → veXPGN

***

### Current System — User Points Voting

Paragon currently operates using a Points-based voting system.

***

#### Voting Power

Voting power is derived from:

* Paragon Points
* earned through protocol usage
* non-transferable and wallet-bound

***

👉 Increased participation leads to greater governance influence.

***

### How Voting Works

#### 1. Proposal

* users above the threshold can submit proposals

***

#### 2. Voting

* options: For / Against / Abstain
* voting period: 5–7 days
* voting power based on Points

***

#### 3. Execution

If a proposal passes:

* it is queued in the timelock
* executed after the delay

***

👉 Execution is transparent and publicly verifiable.

***

### Voting Requirements

Initial parameters:

* proposal threshold: \~25k Points
* quorum: \~1M Points
* majority: 50%+
* critical proposals: higher thresholds

***

👉 All parameters are adjustable through governance.

***

### Execution (Timelock)

All approved proposals pass through:

* timelock delay (≥ 48h)
* public queue
* visible execution

***

👉 This ensures:

* no instant changes
* protection against malicious actions
* full transparency

***

### Emergency Controls

A limited Guardian role exists for:

* security incidents
* exploits
* critical failures

***

#### Constraints

* short-term usage only
* must provide public explanation
* cannot override governance permanently

***

👉 Designed to balance safety and decentralization.

***

### Delegation

Users can delegate voting power.

***

#### How It Works

* assign Points to another wallet
* delegate votes on your behalf
* revoke at any time

***

#### Why It Matters

* enables representation
* supports active governance participants
* improves decision quality

***

### Future — veXPGN Voting

Paragon will transition to fully on-chain governance.

***

#### veXPGN Model

* lock XPGN → receive veXPGN
* longer lock duration increases voting power
* non-transferable

***

#### Voting Power

Based on:

* amount locked
* lock duration

***

#### Execution

* proposals executed via Governor contracts
* enforced through timelock

***

👉 Governance becomes fully on-chain and binding.

***

### Transition (Points → veXPGN)

Points holders will be incorporated into the veXPGN system through:

* governance boosts
* proposal participation rights
* early influence

***

👉 Designed to reward early participation while maintaining long-term alignment.

***

### What You Vote On

***

#### ⚡ Protocol Parameters

* fee structure
* execution parameters
* routing rules

***

#### 🌾 Emissions

* XPGN distribution
* farm incentives

***

#### 📊 P10 Index

* asset selection
* rebalancing rules

***

#### 🏦 Treasury

* buybacks
* POL strategy

***

#### 🛡️ Risk Controls

* oracle settings
* system limits

***

### Transparency

All governance activity is:

* public
* verifiable
* recorded on-chain

***

Users can view:

* voting activity
* voting power
* proposal outcomes
* execution status

***

### ⚠️ Important Notes

* Points are not tradable
* voting power changes over time
* governance evolves in phases
* not all proposals are approved

***

### Summary

* Points enable early governance participation
* veXPGN enables long-term on-chain control
* proposals are transparent
* execution is delayed and verifiable

***

Paragon governance is designed to give active users meaningful influence, evolving toward fully decentralized, on-chain decision making.


---

# 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://paragon-protocol.gitbook.io/paragon-protocol/governance-and-tokens/governance-voting.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.