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

# MUON Token

## Distribution Plan

The total (and max) supply of $MUON is **1 billion tokens**. The following chart illustrates how MUON will be distributed. (Click on the image to see a larger-scale version.)

<figure><img src="/files/KADSfwHa0aBZS4a6EISc" alt=""><figcaption><p>$MUON Distribution Plan</p></figcaption></figure>

## Vesting & Staking

Prior to migrating the PION - the Canary network's native token - [a snapshot vote](https://snapshot.box/#/s:pion-network.eth/proposal/0x2cb57a35820e036bf692dcaff24d6c93402f4a8d6b32e0d2fa1d0574baaf9f85) was held. Based on the results of the community vote, the following vesting and staking plans were put into action at launch.

* **Vesting:** 90% of MUON allocations are locked for one year and released **on a daily basis** over the twelve months.
* **Staking:** 10% of MUON allocations - including any MUON migrated from liquid PION - are staked (or auto-delegated) as node power. This amount can be un-staked at any time, but there is **a two-week cooldown period**.

To see the status of your staked amounts, see [Muon Node Operating Dashboard](https://app.muon.net).&#x20;

To see your delegated amounts, refer to [Muon Delegators Dashboard](https://delegate.muon.net).&#x20;

## Utility

$MUON forms the Muon’s backbone and has been designed to incentivize the protocol's participants in the most efficient way and maximize value, with regards to tech development, marketing/community and incentives.

There are four major utilities for $MUON:

* Node Operations
* Fees
* Liquidity
* Governance

<figure><img src="/files/iTXugmoBqI75PjgTAXQC" alt=""><figcaption><p>$MUON Utility</p></figcaption></figure>

#### **Node Operations** <a href="#node-operations" id="node-operations"></a>

Muon is powered and secured by a network of nodes which validate and sign the requested data. To protect the network against any potential fraudulent activity, nodes must stake $MUON as collateral, and, in return, they earn rewards for keeping the protocol secure and decentralized.&#x20;

#### **Fees** <a href="#network-fees" id="network-fees"></a>

$MUON serves the same purpose as any gas token: user fees funds the protocol expenses, such as node operation. Muon has a modular and chain-independent fee structure; fees can be paid on one chain, but used for data requests on any chain.

#### **Liquidity**

Getting listed on DEXes will provide opportunities for users to supply liquidity with their $MUON, and be rewarded for doing so.&#x20;

#### **Governance** <a href="#governance" id="governance"></a>

Part of the future will be the Muon DAO. This governance structure will see a decentralized initiative towards decision making around the direction of Muon elements. $MUON holders who wish to have greater say in the project will be able to contribute to the DAO.


---

# 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.muon.net/muon-protocol/muon-token.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.
