> For the complete documentation index, see [llms.txt](https://empmoneyv2.gitbook.io/emp.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://empmoneyv2.gitbook.io/emp.money/protocol/platform.md).
# Platform
## Eshare Emissions
Our original EMP farms rewarded ESHARE emissions until a supply of 56K ESHARE was reached, at which point a halving model was commenced which cut the emissions rate in half each year.
**With the launch of EMP Fusion, all emissions that were originally allocated to the Farms are now being allocated to EMP Fusion.** The original farms are no longer receiving emissions, and any EMP/ETH LP & ESHARE in the farms can be removed and sacrificed into Fusion to continue earning daily yield from both emissions and additional revenue streams.
**Emissions schedule example:**
* Year 1: 28,000 Eshare emissions (completed)
* Year 2: 28,000 Eshare emissions (completed)
* Year 3: 14,000 Eshare emissions **(currently here)**
* Year 4: 7,000 Eshare emissions
* Year 5: 3,500 Eshare emissions
\
###
##
---
# 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://empmoneyv2.gitbook.io/emp.money/protocol/platform.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.