> For the complete documentation index, see [llms.txt](https://bigly.gitbook.io/bigly-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bigly.gitbook.io/bigly-docs/background-info/launchpad-tokens.md). # Launchpad Tokens #### Total Supply Every token launched has a total supply of 1,000,000,000 (1B). *** #### Distribution **Distribution** **58% — Presale Contributors (580M tokens)** * Distributed pro-rata based on your share of total SOL raised * Example: contribute 1% of the total → receive 1% of 580M tokens * Airdropped at launch *** **2% — Bonus Pool (20M tokens)** * Reserved for presale participants who contribute at least 1 SOL * Must post a screenshot of your bonus eligibility on X * Bonus tiers are based on follower count * Claimable on the site once the token launches * **20M tokens** are reserved as a bonus This incentivizes distribution and awareness. *** **40% — Liquidity Pool (400M tokens)** * Paired with all SOL raised in the presale to seed the initial trading market via Meteora's DBC * More SOL raised = more attention and deeper liquidity This creates the initial trading market. --- # 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://bigly.gitbook.io/bigly-docs/background-info/launchpad-tokens.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.