> For the complete documentation index, see [llms.txt](https://litepaper.itrainer.fit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litepaper.itrainer.fit/tokenomics/bedo.md). # BEDO **BEDO** the app’s internal **move & earn** token, has an unlimited supply and is earned when the user performs an activity in the app. **BEDO** is burned when the user **Buy Or Rent NFT** From App **iTrainer** does not sell **BEDO** directly to players; users mine tokens themselves, use them in the app, and can sell/exchange them on open marketplaces. ### **Supply and Earning** **BEDO** has an unlimited supply and is earned when a user moves or interact with **iTrainer App**. **Following are the contract :** BEDO (BEP20) Contract address: 0xe63b22b01c476b02732320fb449c7a2f3b2b6953 ### BEDO Burning Mechanics (Destroying) The BEDO Tokens is burned by: 1. GymBuddies Minting 2. Rent NFTs From App 3. Upgrade up GymBuddies 4. Subscribe to **iTrainer App** --- # 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://litepaper.itrainer.fit/tokenomics/bedo.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.