# Token Distribution

## Total Supply ⇒ 110 Million MFORGE 

**Private Sale** ⇒ 5.45% = 6,000,000\
**Development** ⇒ 12.55% =  13,800,000\
**Founders** ⇒ 9.09% = 10,000,000\
**Treasury** ⇒ 4.55% = 5,000,000\
**Initial Liquidity** ⇒ 0.91% = 1,000,000\
**Marketing** ⇒ 9.09% = 10,000,000\
**Staking Rewards Pool** ⇒ 10% = 11,000,000\
**LP Staking** ⇒ 13.64% = 15,000,000\
**Community Rewards** ⇒ 13.64% = 15,000,000\
**Ecosystem** ⇒ 21.09% = 23,200,000

## Token Migration (New token)

**Last price** ==> $0.01517\
**Old Total supply** ==> 500M\
100% in circulation

## New total supply ⇒ 110M

**Migration ratio** ⇒ 1:5\
**1 new token** = 5 old tokens \
Liquidity transferred from old contract.

## Token allocation

**Migration** ⇒ 100,000,000\
**Ecosystem** ⇒ 10,000,000

## Current Revenue Sources 

Our current revenue model is designed to ensure the sustainability and growth of the MetaForge ecosystem while providing value to our stakeholders. As part of our fee structure, we implement the following charges:

* **Sell Transactions:** A fixed fee of 5% is applied on all sell transactions, collected in our native asset MFORGE.
* **Buy Transactions:** A fixed fee of 2% is applied on all buy transactions, collected in MFORGE.
* **LP Token Staking Penalty:** A penalty of 20% is enforced on LP token staking, serving as a mechanism to maintain liquidity within the ecosystem. The penalty is collected in MFORGE.

These charges are implemented consistently across all buy and sell transactions, as well as LP token staking activities. By leveraging this revenue model, we aim to support ongoing development, incentivize participation, and ensure the long-term sustainability of the MetaForge platform..


---

# 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://magnummeta.gitbook.io/docs/tokenomics/token-distribution.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.