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

# pUSD

pUSD is an algorithmic stablecoin, governed by the protocol to maintain stability through incentive-based mechanisms and flexible collateral management. Its design allows the protocol to dynamically respond to market conditions while optimizing capital efficiency.

pUSD is backed by USDC at launch, ensuring a stable entry point and user confidence. Over time, the protocol may evolve its collateral model to increase capital efficiency and unlock more flexible yield mechanisms.

**Launch Collateralization:** 1:1 backed by USDC.e

**Adaptive Collateralization:** The protocol aims to optimize the ratio of backing assets to minted pUSD, balancing stability with protocol growth.

**Reward Claim Fee:** A time-weighted claim fee applies to rewards. Currently, the fee is set to 20%, but may be changed to support long-term protocol health and sustainability.


---

# 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://pillar-dao.gitbook.io/pillar-dao-docs/tokens/pusd.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.