> 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/what-is-muon/our-story.md).
# Our Story
### Our Story
*“Once upon a time, two brothers looked at the sky and saw more than just clouds.”*
In 2022, a small group of Web3 builders came together with a shared vision: effectively removing the limitations of scalability, interoperability and security to expand capabilities and use-cases of Web3 applications. To accomplish this goal, we formed a team of devs and content creators who shared our vision and called the protocol/project Muon, the most basic building blocks of the universe. The name implies Muon protocol aims to be the basic building block of the Web3 Ecosystem.
#### Development History
To achieve this goal, a POA network was established in 2022, which led to the launch of a Testnet – aka ALICE – in January 2023, with over 1,500 uniquely verified nodes. After nine months of successful operation, passing an audit with a high score of 9.4/10, we launched Pion – our Canary network – with a tradable token and 1,000+ nodes. It ran smoothly for nearly a year and a half until the launch of Muon/$MUON in April 2025.
Muon's Path to Success
On April 9, 2025 Muon protocol and its native token -MUON - were launched. To determine the conditions and metrics of migration from Pion to Muon, a snapshot vote was held for the community prior to the launch. [The results of the vote](https://snapshot.box/#/s:pion-network.eth/proposal/0x2cb57a35820e036bf692dcaff24d6c93402f4a8d6b32e0d2fa1d0574baaf9f85) defined how the migration would take place including the vesting/staking plan and metrics.
---
# 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/what-is-muon/our-story.md?ask=&goal=
```
`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.