# 3. Tokenomics Setup

{% hint style="info" %}
This is where you configure how the token actually behaves.
{% endhint %}

<figure><img src="/files/cp33CpX20tm4ZxEJFuqI" alt=""><figcaption></figcaption></figure>

You control:

### Supply

Tokens created inside FOREST do not rely on a fixed maximum supply.\
Instead, supply adjusts mechanically based on bonding curves and liquidity behaviour.

### Token Split (%)

How your supply is allocated:

* Liquidity
* Treasury / Reserve
* Staking Rewards
* Airdrop Pool

These percentages must total 100%.

### Fees

Two adjustable fees:

* Buy Fee (%)
* Sell Fee (%)

Fees route value into:

* creator revenue
* protocol revenue
* automatic buybacks

### Bonding Curve (Pre-Progression Phase)

Choose how your early pricing behaves:

{% tabs %}
{% tab title="Linear" %}
A simple, even pricing progression during buying activity.
{% endtab %}

{% tab title="Exponential" %}
Price increases accelerate as demand rises.
{% endtab %}

{% tab title="Logarithmic" %}
Pricing increases slower at first, then stabilises.
{% endtab %}
{% endtabs %}

These curves define how price reacts to buying during the early phase.

### Progression Threshold

This is the point (measured in $FOREST liquidity) where your token transitions from curve-based pricing into the long-term liquidity pool.

A progress bar shows how close your token is to this threshold once it is live.

### Buyback %

Define what share of eligible revenue is used for automatic buybacks.

* High % = stronger buy pressure.
* Low % = slower, steady accumulation.

{% hint style="success" %}
Goal of this step: Shape the core economics of your token.
{% endhint %}


---

# Agent Instructions: 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.forest.inc/creating-a-token/3.-tokenomics-setup.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.