> For the complete documentation index, see [llms.txt](https://docs.rwa.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rwa.inc/investor-platform-and-staking/introduction-and-overview/how-does-an-ido-work.md). # How does an IDO work? When projects are ready to list on the RWA Launchpad, RWA Inc. will help them prepare a campaign and connect them to the RWA Inc. community. After the specifications have been finalized, token supply, market rate, sale duration, etc., the project will be listed with a countdown to launch. Every IDO listing consists of 2 Rounds: ## Round #1: Guaranteed Allocation Top staking Tier groups — Silver, Gold, Platinum and Diamond Tier, and some Bronze members (with potential allocation based on a lottery system) will have access to the Guaranteed Rounds. All users must register interest to participate in the Guaranteed Round. ## Round #2: First-Come-First-Served (FCFS) If any tokens remain after Round 1, they will be made available in Round 2 for all whitelist participants, regardless of whether they won the lottery or secured a guaranteed allocation. Token purchases during this phase will follow a FCFS format, with individual purchase limits determined on a project-by-project basis. --- # 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.rwa.inc/investor-platform-and-staking/introduction-and-overview/how-does-an-ido-work.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.