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

# Tokenomics and Emission Schedule

#### Pickle adopts a style of tokenomics inspired by Andre Cronje's ve(3,3) [tokenomics](https://andrecronje.medium.com/ve-3-3-44466eaa088b) for Solidly.

This model has been adapted by Pickle with a view towards incentivizing locking $PICKLE tokens for $DILL. $DILL is a governance utility token received by Pickle users that lock $PICKLEs for a set amount of time, granting not only participation in soft governance but also an array of perks such as revenue-sharing.

The key changes Pickle has made are:

* clearly framing the utility of $DILL locking as a claim on Pickle revenues: present and future
* reduced dilutive pressure on $DILL lockers
* dynamic reduction of $PICKLE emissions as $DILL adoption increases

As $DILL supply increases as a percentage of the $PICKLE total supply, emissions will decrease. This encourages collaboration and locking for $DILL amongst users, creating positive pressure on the price of $PICKLE.


---

# 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:

```
GET https://docs.pickle.finance/pickle-token/tokenomics-and-emission-schedule.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.