# Welcome to FireBot.gg! ### **Multi-Asset Backing: Stability with Major Cryptocurrencies** FBX is the cornerstone of an ecosystem backed by major cryptocurrencies. With a comprehensive asset management system that ensures FBX is supported by a diverse portfolio of leading digital assets, providing stability and reinforcing its role as a trusted asset in the ever-evolving crypto landscape. ### **Scarcity from Day One** FBX was launched with a hard cap of **21 million tokens**. Every interaction with smartcontracts triggers continuous, protocol-level burns—through various integrated mechanisms, including transmuters—steadily reducing the circulating supply. This built-in scarcity ensures that each token becomes progressively rarer and more valuable over time. ### **Deflationary by Design** The ecosystem employs multiple burn processes to tighten supply every time users engage with the smartcontracts. ### **Yield & Burns** EP tokens are a core innovation of the ecosystem: on-chain proof-of-burn assets minted by burning FBX. This process supports FBX deflation and rewards EP stakers with yield. ### **True Ultrasound Money 🦇🔊** If capped-supply gold is sound money, decreasing-supply FBX is ultrasound money. Bitcoin (BTC), often compared to digital gold, remains inflationary due to its ongoing mining emissions. Ethereum (ETH), while theoretically deflationary, still experiences net-positive emissions in practice. FBX, on the other hand, takes this concept further—by ensuring that supply can only decrease, making it a currency engineered for long-term deflationary scarcity. --- # 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://fbx.gitbook.io/docs/welcome-to-firebot.gg.md?ask= ``` 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.