> For the complete documentation index, see [llms.txt](https://docs.souless.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.souless.fun/launching/launch-a-token.md). # Launch a token > **Availability: ARC MAINNET + TESTNET** Launching creates a fixed-supply token and its market. Review every value carefully: most launch economics become fixed when the opening begins, while Community governance can change only the bounded future policy described below. ## Launch fields | Field | Meaning | After launch | | -------------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | | Token name | Full public name | Immutable | | Ticker | Short market symbol | Immutable | | Image | Public visual identity | Metadata policy applies | | Description | Plain-language summary | Indexed metadata | | Narrative | Primary idea or category | Classification may be updated with history | | Supply | Nominal token amount; current guarded launch uses 1,000,000,000 tokens | Immutable | | Creator launch buy | USDC the creator commits before the public opening | Immutable once opening starts | | Community Mode | Enables the external staking, rewards, and governance layer | Recorded at launch | | Initial Creator / Community allocation | Starting split of the fixed 70% creator/community LP-fee pool | Becomes the Community policy floor from the first reward epoch | | Initial Staking / InfoFi split | Starting split inside the Community allocation | Applies from the first reward epoch; later governance may change future epochs within bounds | | Governance wallet | Wallet associated with creator governance rights | Immutable genesis identity in the current design | | Referral | Signed referral attribution | Immutable for the launch; time-limited economics | | Token Protection | Requests temporary protection for the exact name + ticker pair | Request is recorded at launch; protection activates only after qualification | The UI may enforce a stricter range than the contracts. The prepared transaction is the final source for the values you sign. ## Community allocation at launch When **Community Mode is enabled**, the creator chooses the market's starting fee policy during launch instead of waiting for a later governance proposal. The Creator and Community allocations share a fixed **70%** of collected USDC-side LP fees: * **Community:** may start from **10% to 70%** of LP fees. * **Creator:** receives the remainder of that fixed pool, so `Creator = 70% - Community` and may start from **60% down to 0%**. * The default remains **60% Creator / 10% Community**. The creator also chooses how the Community allocation starts: * **Staking:** **20% to 80% of the Community pool**. * **InfoFi:** the remainder of the Community pool. * The default remains **50% Staking / 50% InfoFi** inside Community. This launch selection is initialized as the market's genesis Community policy and is effective from **epoch 1**. It does not require a governance vote and does not wait for a later epoch to become the starting allocation. After launch, governance still controls future policy within its bounds. Community share can only move upward from the market's established floor, reducing Creator share by the same amount inside the fixed 70% pool. The Staking/InfoFi split can move within the 20%–80% range for future eligible epochs. Referral, Launch Partner, and protocol destinations remain outside this creator/community choice. ## Token Protection is not automatic Selecting Token Protection does **not** make the token protected as soon as it launches. It enters the protection qualification process and must meet the current requirements before protection can be activated on-chain. Current requirements include token age, qualifying non-creator volume, non-creator holder count, liquidity, holder concentration, and creator standing. There is also a one-hour contention period for the exact name + ticker pair. See [Token Protection](/launching/token-protection.md) for the current thresholds, duplicate-launch economics, protection term, and release process. ## Launch sequence ``` Launch details + starting Community policy │ ▼ Fee and transaction review │ ▼ Creator signs ──→ Token deployment ──→ Launch Guard opening │ ▼ Create and settle V3 market │ ┌───────────────────┴──────────────────┐ ▼ ▼ Lock official LP Publish LIVE market ``` ## Before signing * Confirm the connected network is the Arc network you intend to use. * Confirm name, ticker, supply, narrative, governance wallet, and creator commitment. * If Community Mode is enabled, confirm the initial Creator/Community allocation and Staking/InfoFi split. * Read the launch fee and Opening fee separately. * Check slippage/minimum-token protections and the maximum USDC amount. * Treat referral attribution as final for the launch. * If requesting Token Protection, understand that the request still has to qualify after launch. ## What can still change? Market price, balances, indexed metadata, public classification, protection status, and future governance-controlled Community parameters can change. The token supply, launch creator, canonical market, official LP custody, and finalized epoch results remain fixed by their protocol rules. --- # 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://docs.souless.fun/launching/launch-a-token.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.