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

# Emissions

Emissions are the product's marketing budget, spent as locked value that people watch drip. They are front-loaded on purpose, and they end.

## The schedule

| Rule             | Detail                                                             |
| ---------------- | ------------------------------------------------------------------ |
| Reserve          | 4.0B sGAGE, held by the emissions contract                         |
| Schedule         | 52 weekly epochs from token launch, each 10% smaller than the last |
| Week one         | 402M                                                               |
| Week 52          | 1.9M                                                               |
| Half the reserve | Out by week 7                                                      |
| 90%              | Out by week 22                                                     |
| End              | Nothing after week 52. Whatever the reserve still holds is burned  |

The schedule is a table in the contract, and cumulative emission can never exceed it.

## The split

| Split                       | Default | Adjustable               |
| --------------------------- | ------- | ------------------------ |
| Deals : liquidity           | 60 : 40 | Per epoch, within bounds |
| Deal budget, 21-day : 7-day | 70 : 30 | Per epoch                |
| Lender : borrower           | 50 : 50 | Per epoch                |

Deal budget left unallocated at the end of a week goes to that week's liquidity rewards, so every week's emission is paid out in full.

## Why it can be this steep

Most of what week one grants is still locked when week two starts: a 21-day drip has released under 4% after its first week. The week-one grants that do unlock land in weeks two to four in a pool that is days old, and that, not the size of the reserve, is the limit on going steeper.

| Weekly decay | Week one | Week 52  | Half by    | 90% by      | First four weeks |
| ------------ | -------- | -------- | ---------- | ----------- | ---------------- |
| 5%           | 215M     | 15.7M    | week 14    | week 45     | 20%              |
| 8%           | 324M     | 4.6M     | week 9     | week 28     | 29%              |
| **10%**      | **402M** | **1.9M** | **week 7** | **week 22** | **35%**          |
| 12%          | 481M     | 0.7M     | week 6     | week 18     | 40%              |

## Releasing a week

Each week's release is permissionless. Anyone may release an epoch, which streams the liquidity budget to the liquidity rewards contract and opens the deal budgets. After an epoch ends there is a short grace for late registrations, then the unreserved deal budget rolls over to liquidity rewards. After week 52, anyone may finalise, which burns the remainder.


---

# 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.gage.cash/tokens/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.
