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

# SYRUP Tokenomics

As part of the implementation of Maple's latest governance proposal, MIP-010, the Syrup protocol will mint approximately 1.15 billion SYRUP.

This new issuance does not represent an increase in the token supply but rather a conversion of 1 MPL to 100 SYRUP, with no dilution for MPL token holders.

Previously, the Maple DAO voted to recapitalize the Maple Treasury, introducing a one-time issuance of 1,000,000 MPL and a 3 year emission of 5% per annum. With the conversion of 1 MPL to 100 SYRUP, all issuance from the initial schedule will also be minted as SYRUP tokens, broken down as follows:

* 1,000,000,000 (new SYRUP supply)
* 100,000,000 (initial 10% from inflation schedule)
* 54,930,000 (from inflation schedule till 1st Oct 2024)

Following the approval of MIP-010, a migrator contract allows MPL users to convert to SYRUP, and all issuance and emissions will also be minted as SYRUP tokens.

In line with the agreed token inflation schedule and issuance, the expected supply of SYRUP tokens will be 1,267,875,000 by September 2026.

Details regarding the SYRUP token issuance can be found in our [governance proposal](https://community.maple.finance/t/mip-010-syrup-token-launch-and-mpl-syrup-conversion/334).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.maple.finance/maple-for-token-holders/syrup-tokenomics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.