> For the complete documentation index, see [llms.txt](https://spawnmeme.gitbook.io/spawnmeme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spawnmeme.gitbook.io/spawnmeme-docs/whitepaper/04-token-launches.md). # 4. Token launches and graduation ### Launch preparation The documented standard launch creates a Solana token and a Meteora bonding-curve pool through a transaction approved by the creator. The published standard describes a supply of **1,000,000,000 tokens**, **six decimals** and **SOL as the quote asset**. The creator must review the actual configuration presented by the deployment flow. The process starts with the token's name, ticker, image, description and links. SPAWN prepares and simulates the transaction before wallet approval. The documented flow removes mint and freeze authority, locks token metadata and can include an optional initial creator purchase capped at 5% of supply. These properties should be checked on the resulting token and pool. A familiar name, logo or address suffix is not proof that a launch uses the expected settings. ### Approval and confirmation The creator reviews the complete transaction and its costs in the wallet. Token creation, pool creation, the platform launch fee and any supported initial buy form the documented launch transaction. After execution, SPAWN reads the confirmed result and verifies launch conditions before listing the token. Its documented checks cover the token and pool, standard settings, fee payment and initial-buy limit. A transaction signature alone does not prove successful execution. If a transaction remains pending or a page loses connection, users should inspect its status before repeating the launch. Network fees may apply to a submitted transaction that fails; local preparation or simulation is a different stage. ### Curve trading Buy and sell transactions interact with the pool. Price depends on the deployed curve and pool state. The documented model uses a custom square-root-price curve; this paper does not substitute a simplified formula for the actual on-chain configuration. The fee page describes a 1.2% base trading fee for new SPAWN bonding pools. Protocol deductions and network costs remain relevant. Price can move downward, and a pool's existence does not ensure liquid trading at a user's preferred price. ### Graduation Graduation follows the pool's on-chain curve and Meteora rules. This edition does not assign a universal SOL graduation threshold. Users should inspect the current pool progress and configuration rather than relying on a promotional approximation. Under the documented model, graduated liquidity is permanently locked in a Meteora position held by the creator wallet. The position's eligible fee income can be claimed separately through the Creator Dashboard. Claiming fees does not withdraw the locked liquidity. A liquidity lock is a specific restriction on a position. It is not a guarantee of token value, active trading, creator conduct or protocol security. ### Creator earnings before and after graduation Tokens launched with creator fees earn the launch wallet about **0.25% of each bonding-curve trade**, from the first trade. This is included in the existing **1.2% trading fee**, not an additional charge. Tokens launched before creator fees were enabled retain a permanent 0% creator share on the curve. After graduation, creators can claim the eligible trading fees of the locked Meteora pool, after Meteora’s share. Earnings require trading and may be zero. Accrued curve fees stay claimable after graduation. The graduated pool’s fees are a separate claim; locked liquidity remains inaccessible. See 50. Claim your creator fees. ### Metadata and token-balance locks Current launches lock the token identity at creation. An eligible older Classic token can be made immutable by its metadata update authority from the token page. This action is permanent and separate from supply, balance locking or graduation liquidity. The Locked tokens card reports supported Jupiter Lock and Streamflow schedules, including creator amounts and cancellable locks. A token lock restricts only its covered balance. Branded mint suffixes may be available but do not replace full-address verification. *** Previous: 3. Architecture and transaction boundaries · Next: 5. Markets, trading and wallet tools --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://spawnmeme.gitbook.io/spawnmeme-docs/whitepaper/04-token-launches.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.