> For the complete documentation index, see [llms.txt](https://monbux.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monbux.gitbook.io/docs/monbux.md). # Monbux Monbux Overview ## **Overview** ### What is Monbux? **Monbux** is a **liquid staking platform** built on the Monad Testnet. Users can stake their **MON tokens** and receive **mMON**, a transferable receipt token that represents their staked position. mMON provides users with continuous exposure to staking rewards while maintaining liquidity. Holders can keep mMON to accrue rewards or use it in **swaps, transfers, and future DeFi integrations** within the Monad ecosystem. *** ### Why Monbux? Traditional staking often locks tokens for long periods, limiting liquidity.\ Monbux solves this by introducing **liquid staking**: * **Liquidity:** mMON allows users to retain tradable value without locking funds. * **Transparency:** All staking and rewards are recorded on-chain. * **Flexibility:** Stake and unstake at any time without long lockups. * **Rewards:** Earn MON staking rewards while maintaining liquidity. *** ### Key Features * 🔗 **1:1 Initial Conversion** — 1 MON = 1 mMON at the time of staking. * 📊 **Dynamic Exchange Rate** — mMON value increases over time as rewards accumulate. * ⚡ **Instant Stake & Unstake** — Users can stake or withdraw with minimal delay. * 💸 **Configurable Fee Model** — Small fees on unstaking are directed to the treasury/admin wallet. * 🔒 **Secure Smart Contracts** — Designed with robust mint/burn and staking mechanisms. *** ### Vision The vision of Monbux is to make staking on Monad **simpler, liquid, and user-centric**.\ By combining staking rewards with tradable liquidity, Monbux aims to become a **core building block of the Monad DeFi ecosystem**, with upcoming integrations into **swaps, governance, and advanced yield strategies**. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://monbux.gitbook.io/docs/monbux.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.