> For the complete documentation index, see [llms.txt](https://docs.peapods.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peapods.finance/pods/indicative-pod-settings.md).

# Indicative Pod Settings

Configuration can vary depending on asset characteristics and typical price action.  Below are some indicative settings based on the daily volatility of the underlying asset of a Pod.

| Volatility Category    | Wrap/Unwrap Fee | Buy/Sell Fee |
| ---------------------- | --------------- | ------------ |
| Low Volatility (<5%)   | 0.2% / 0.3%     | <1% each     |
| Mid Volatility (5–10%) | 0.5% / 1%       | 1–2% each    |
| High Volatility (10%+) | 1% / 1.5%       | 2.5% each    |

The recommendation for pTKN Burn varies depending on the intention of the Pod. A lower pTKN burn will see a greater portion of Pod revenue being supplied solely to liquidity providers, whilst a higher burn ensures a larger portion of yield for passive pTKN holders.\
\
If the goal is to incentivize a “staking” style model then a higher pTKN burn is the favorable option, or if the aim is to encourage liquidity depth then a lower pTKN burn should be applied.\
\
\&#xNAN;*Note: The greater the volume and liquidity depth of both the TKN and pTKN pools, the greater the potential performance of the Pod.*


---

# 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://docs.peapods.finance/pods/indicative-pod-settings.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.