# Revenue Share

<figure><img src="/files/C5ue4NMrcdYrrj6V63pd" alt=""><figcaption></figcaption></figure>

Revenue allocated to buy and burn vlPEAS functions as a backing-based yield mechanism, similar to how Pod tokens (pTKN) accrue value. When vlPEAS is burned, it reduces the supply of outstanding vlPEAS while leaving the underlying PEAS untouched. As a result, each remaining vlPEAS represents a larger share of the underlying PEAS tokens.

This process increases the claimable PEAS backing per vlPEAS, providing holders with non-emissive, protocol-native yield in the form of value accrual.

This structure has several key properties:

**Backed Yield**:\
vlPEAS holders earn PEAS-denominated yield as the collateral backing ratio (PEAS per vlPEAS) increases with every vlPEAS burn.

**Non-Dilutive**:\
No new vlPEAS or PEAS are minted as the yield is derived purely from treasury growth and vlPEAS supply reduction.

**Governance Aligned**:\
Since vlPEAS represents both voting power and yield from Treasury-assigned revenue, its value increases in tandem with protocol usage.

The percentage of revenue allocated to these burns is governance-controlled, allowing vlPEAS holders to balance direct yield accrual with other strategic deployments. This system transforms vlPEAS into a PEAS-yielding governance token, where participation is rewarded through growing backing as opposed to the inflation model that is common amongst governance tokens.


---

# Agent Instructions: 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://docs.peapods.finance/protocol-revenue/revenue-share.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.