> 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/economics/fees.md). # Fees and economics Fees are shown by source because “the fee” can mean several different charges. The review screen and prepared transaction are authoritative for a specific action. ## Fee table | Fee | Who pays | Base | Current value | Destination | Change control | | -------------------------- | -------------------------------- | ------------------------------------------------------------------------- | ---------------: | --------------------------------------------------------------- | ----------------------------------------- | | Standard launch | Creator | Per launch | 0.05 USDC | Protocol | Published protocol policy | | Protected duplicate launch | Creator | Exact name + ticker pair while another launch has active Token Protection | 50 USDC | 80% protection holder, 20% protocol | Published protocol policy | | Launch Guard Opening fee | Opening participant | Committed USDC | 0.10% | Opening Fee Vault | Contract-version constant | | Canonical guarded pool fee | Trader | Swap input | 1% | Uniswap LP positions, then collected by side | Pool immutable | | USDC LP-fee distribution | Collected USDC-side LP fees | Amount collected | Policy below | Creator/community/protocol/referral/Genesis Launch Partner pool | Launch policy + bounded future governance | | Token-side LP fee | Traders, accrued in launch token | Collected token amount | Market-dependent | Timelocked reserve or allowed burn address | Separate token-fee policy | | Gas | Transaction sender | Network execution | Variable | Arc validators/network | Network-controlled | The values above are used by the current Arc Mainnet and Testnet guarded deployments. A launch quote binds the accepted policy version and maximum fee. The protected-duplicate fee applies only while protection is **actually active** for the normalized exact name + ticker pair. Selecting Token Protection at launch only submits a request; the market must qualify before protection activates. An exact duplicate is still launchable—it pays the protected-duplicate fee instead of the standard launch fee. See [Token Protection](/launching/token-protection.md). ## Creator and Community at launch Creator and Community share a fixed **70%** block of collected USDC-side LP fees. With Community Mode enabled, let **C** be the Community share selected at launch: * `C` may be **10%–70%** of LP fees. * Creator receives `70% - C`, so Creator may start from **60% down to 0%**. * The default is `C = 10%`, producing **60% Creator / 10% Community**. The creator also selects the starting split inside Community. Staking may receive **20%–80% of C**, and InfoFi receives the remainder. The default is 50:50. These launch values become the genesis Community policy from **epoch 1**. Later governance can increase Community from its established floor and can adjust the Staking/InfoFi split within bounds for future eligible epochs. ## USDC-side LP-fee allocation Referral and the Genesis Launch Partner campaign are independent, temporary overlays funded from the protocol residual. Because Creator + Community remain fixed at 70%, changing `C` does not change the protocol residual for a given referral/partner state. | Community Mode | Active referral | Genesis campaign active | Creator | Community | Protocol | Referral | Launch Partner pool | | -------------- | --------------: | ----------------------: | ------: | --------: | -------: | -------: | ------------------: | | Off | No | No | 60% | 0% | 40% | 0% | 0% | | Off | Yes | No | 60% | 0% | 35% | 5% | 0% | | Off | No | Yes | 60% | 0% | 35% | 0% | 5% | | Off | Yes | Yes | 60% | 0% | 30% | 5% | 5% | | On | No | No | 70% − C | C | 30% | 0% | 0% | | On | Yes | No | 70% − C | C | 25% | 5% | 0% | | On | No | Yes | 70% − C | C | 25% | 0% | 5% | | On | Yes | Yes | 70% − C | C | 20% | 5% | 5% | The protocol share is the residual after all currently eligible destinations are calculated. Therefore 20% is the fully loaded Genesis minimum, not a permanent protocol rate. When a temporary destination is absent or expires, its unused allocation returns to protocol. The current guarded referral allocation lasts 30 days for that launch. The Genesis Launch Partner allocation applies only while the deployed campaign window is active. The two clocks are independent and collection time determines whether each temporary allocation is eligible. Launch-time Community settings and later Community governance cannot redirect referral or Launch Partner allocation. ## Worked examples For **100 USDC of collected USDC-side LP fees** using the default Community policy, with an active referral and the Genesis campaign active: Creator receives 60 USDC, Community receives 10 USDC, protocol receives 20 USDC, referral receives 5 USDC, and 5 USDC is credited to the Launch Partner pool. At the default 50:50 Community split, the 10 USDC Community amount is 5 USDC for Staking and 5 USDC for InfoFi. For a custom launch policy with **30% Community** and **70% of Community assigned to Staking**, the same fully loaded 100 USDC collection becomes: 40 USDC Creator, 30 USDC Community, 20 USDC protocol, 5 USDC referral, and 5 USDC Launch Partner. Inside the 30 USDC Community pool, 21 USDC is for Staking and 9 USDC is for InfoFi. Using the default 60/10 policy, after Genesis ends while the same launch's referral is still active, 100 USDC becomes 60 USDC Creator, 10 USDC Community, 25 USDC protocol, and 5 USDC referral. After the referral also expires, it becomes 60 USDC Creator, 10 USDC Community, and 30 USDC protocol. For a **1,000 USDC Launch Guard commitment**, the Opening fee is 1 USDC. The remaining 999 USDC is the public swap amount. Pool fee, price impact, gas, and launch fees are separate. ## Canonical invariant > Every distributable fee unit must have exactly one destination. Accounting must neither duplicate a unit across recipients nor leave an optional allocation unassigned. --- # 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/economics/fees.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.