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

# Emissions

**ve(3,3) Dynamics**

The main stakeholders of a typical AMM (on Polygon), including `veRETRO` holders, LPs, users, and protocols, are all aligned by the ve(3,3) dynamics that determine $oRETRO emissions.

**`veRETRO` holders** — are incentivized to vote either for the highest volume pools (because the greater the volume, the greater the amount of fees produced as a result), the ones being bribed by protocols seeking to bootstrap their liquidity, or that have a large amount of autobribes. This allows these protocols to create their own flywheel, if the token generates strong volume. 

**Liquidity Providers (LPs)** — are incentivized with emissions driven by “Real Yield” based metrics. 

**Traders** — benefit from the low slippage thanks to the liquidity provided, in concert with the latest and greatest battle-tested vAMM / sAMM tech. 

**Protocols** — have access to a cooperation-oriented liquidity layer. They benefit from capital efficient trading conditions for their tokens, and they can incentivize their liquidity via bribes offered to `veRETRO` holders.

### **Emissions specifications**

* *Weekly emissions (at inception)*: 2,600,000 `$oRETRO` 
* *Weekly emissions decay*: 2% 
* *Weekly team wallet allocation*: 2.5%
* *Weekly* `veRETRO` *rebase*: 30% for first 90 days post-launch, 15% thereafter
* *Emissions for liquidity providers*: 67.5% for first 90 days, 82.5% thereafter


---

# 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.retro.finance/tokenomics/emissions.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.