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

# 5. GRO

*GRO Contract Address (BSC): 0x336ed56d8615271b38ecee6f4786b55d0ee91b96*

*GRO Contract Address (ETH): 0x09e64c2b61a5f1690ee6fbed9baf5d6990f8dfd0*

Circulating Supply: Approximately 380,000

GRO is the core governance token of the Growth DeFi ecosystem. It is bought back and burned using the excess system surplus in MOR.

System Surplus increases from three sources:

1. Stability Fees
2. Liquidation Penalties
3. PSM Fees

It is ideal to always have some MOR reserved in the system surplus to protect against black swan events. This excess amount is used to buyback and burn GRO.

GRO is the governance token used to vote on the important decisions for MOR such as stability fees, debt ceilings and other important parameters.\
\
\
\
\
\
\ <br>


---

# 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.growthdefi.com/gro-tokenomics.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.