> For the complete documentation index, see [llms.txt](https://rgo.gitbook.io/rgo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rgo.gitbook.io/rgo/platform-modules/rgo-lssuance-layer.md). # RGO Lssuance Layer The RGO Issuance Layer supports two creation pathways: **IFO Issuance Mode and FUN Issuance Mode.** Each mode is designed to meet different needs — from real-world asset tokenization to lightweight community-driven launches. ### IFO Issuance Mode The IFO Issuance Mode is designed for structured, transparent, and irreversible asset creation. It ensures fixed supply, permanent liquidity, and clear market entry rules. #### Fixed Supply Configuration Issuers may define the total token supply during creation. Supply cannot be increased after deployment. #### Liquidity Pair Selection When launching on PancakeSwap, issuers must select one base asset for initial liquidity: * BNB * USDT * RGO This forms the asset’s primary price discovery pair. #### Platform Fee RGO charges a fee equal to 0.1% of the total token supply created. This fee is locked for 90 days and released automatically afterward. #### Liquidity Initialization Issuers may choose one of the following liquidity requirements: * 10 BNB * 10,000 USDT * 5,000 RGO Once liquidity is added, the corresponding LP tokens are sent to a 0x0000… burn address, ensuring: * Liquidity cannot be removed * Liquidity cannot be withdrawn * The pool remains permanent and irreversible This guarantees long-term stability and prevents rug-pull scenarios. *** ## FUN Issuance Mode The FUN Mode is designed for creators, communities, and experimental launches. It provides a fast and controlled token creation process based on fixed templates, ensuring consistency and preventing misuse. #### Template-Based Token Creation Tokens in FUN Mode follow a non-customizable issuance template. Users may set only basic identification fields (e.g., token name, symbol), while supply, taxes, contract logic, and parameters are fully standardized by RGO. This ensures fairness, simplicity, and predictable behavior for all FUN-mode tokens. #### Internal Market First All FUN-mode tokens begin trading exclusively inside RGO’s internal market. Price discovery, early liquidity, and community interaction all happen within the platform. Once the internal liquidity or market cap threshold is reached, the asset becomes eligible for automatic external launch to PancakeSwap. *(This mechanism functions similarly to pump-style launch systems.)* *** ## Purpose of the Two Modes IFO Mode → for structured, credible, long-term assets * Irreversible liquidity * Fixed supply * Transparent rules * Ideal for real-world value support FUN Mode → for rapid, community-driven token creation * Quick launches * Internal trading * Threshold-based external listing Together, these two modes serve all types of creators — from serious IFO issuers to meme, community, and experimental token projects. --- # 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://rgo.gitbook.io/rgo/platform-modules/rgo-lssuance-layer.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.