> 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-1.md).
# Pods
Pods are the foundation of the Peapods protocol, allowing users to wrap one or more underlying assets into a single ERC-20 token. Pods enable volatility farming and generate yield from market fluctuations.
* **Flexible:** Pods can take the form of an index by [wrapping](#wrapping) multiple assets, or a synthetic version of a singular asset.
* **Fully Collateralized:** Pods are always 100% backed by the underlying assets, ensuring security and transparency.
* **Value Accrual:** Over time, Pods can accrue in value versus TKN if they include a pTKN burn fee (see [Protocol Fees](/pods-2/fees.md)).
* **Arbitrage Opportunities:** When the price of the wrapped token (pTKN) deviates from the underlying asset (TKN), arbitrageurs can take advantage of this discrepancy, generating fees for the protocol.
Each pTKN burn increases the value of each pTKN vs TKN
## Multi-Asset Pods
All multi-asset Pods on Peapods have a set weight per asset that make up the Pod when created. These Pods do not depend on the market value of the tokens and anyone can create them at any time.
## Decentralized & Trustless
In contrast to conventional and certain crypto methodologies which function off a more centralized asset management style of structure, our framework is entirely decentralized which means that there is no central management from the team or any individual at any stage after a Pod has been launched.
Investors can engage autonomously and, by becoming a fund liquidity provider, earn fees based on asset volatility.
---
# 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-1.md?ask=&goal=
```
`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.
