> 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/p10-index/overview.md).

# Overview

### What P10 Is

P10 is an index token that represents a curated basket of crypto assets.

Instead of managing multiple tokens:

* buy → **P10**
* get → diversified market exposure

***

### Core Design

P10 is built to be:

* **user-governed** → controlled via veXPGN
* **transparent** → fully on-chain
* **scalable** → suitable for both retail and institutional use

***

### What’s Inside P10

The index includes:

* high-liquidity assets
* top tokens by market relevance
* protocol-approved assets

👉 Examples (illustrative only):

* BTC
* ETH
* BNB
* leading DeFi assets

***

⚠️ Final composition is:

* governed by veXPGN
* updated over time
* publicly visible

***

### How It Works

#### Mint

You deposit:

* USDT or a supported asset

The protocol:

* acquires the underlying basket
* mints P10 representing that allocation

***

#### Redeem

You burn:

* P10

You receive:

* underlying assets\
  **or**
* a single asset via routing

***

👉 This allows flexible entry and exit.

***

### Execution Layer

P10 uses Paragon’s execution system to:

* source liquidity
* optimize trade routing
* improve capital efficiency

***

### Why P10 Is Different

**Traditional index funds:**

* custodial
* opaque
* slower to adjust

***

**Most DeFi indexes:**

* static allocation
* manual rebalancing
* inefficient execution

***

**Paragon P10:**

* on-chain and transparent
* dynamically governed
* execution-optimized

***

### Non-Custodial

* users retain control of assets
* minting and redemption occur via smart contracts
* no centralized custody

***

### Institutional Ready

P10 is designed for:

* funds
* DAOs
* larger capital deployments

***

Key features:

* predictable mint and redeem flow
* transparent holdings
* auditable contracts
* scalable execution

***

### Rebalancing (Governed)

P10 composition is:

* governed by veXPGN
* updated periodically
* based on market and liquidity conditions

***

👉 All changes are transparent and on-chain.

***

### Efficiency

P10 is designed for:

* optimized routing
* reduced slippage
* efficient capital deployment

***

### Use Cases

#### 👤 Users

* simple market exposure
* passive positioning
* diversification

***

#### 🏦 Institutions

* deploy capital in a single transaction
* reduce operational complexity
* maintain transparent allocation

***

#### 🧠 Advanced Users

* integrate with farming
* combine with execution strategies
* use alongside automation tools

***

### ⚠️ Risks

* market volatility
* performance of underlying assets
* index composition changes

***

👉 P10 simplifies exposure, but does not eliminate risk.

***

### Summary

P10 allows users to:

* enter diversified positions in one step
* maintain exposure to key assets
* manage positions efficiently

P10 is a fully on-chain index designed to provide transparent, diversified, and scalable market exposure.


---

# 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://paragon-protocol.gitbook.io/paragon-protocol/p10-index/overview.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.