> 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/networks-and-reference/parameters.md). # Protocol parameters This is a readable reference for the current guarded Arc Mainnet and Testnet policy. The values shown by the transaction review are authoritative for a specific action. | Parameter | Current value | Control | | ------------------------------------------- | -----------------------------------------------------: | ------------------------------ | | Guard opening | 60 seconds | Contract-version constant | | Minimum guard commitment | 10 USDC | Contract-version constant | | Opening fee | 0.10% | Contract-version constant | | Finalization grace | 30 seconds | Contract-version constant | | Guard participant cap | 64 | Contract-version constant | | Guard cancellation delay | 30 minutes | Contract-version constant | | Nominal guarded supply | 1,000,000,000 tokens | Contract-version constant | | Guarded pool fee | 1% | Launch/deployment immutable | | Public commitment cap | 83 USDC | Current deployment | | Creator commitment cap | 126.9 USDC | Contract/deployment maximum | | Standard launch fee | 0.05 USDC | Protocol fee policy | | Protected duplicate fee | 50 USDC | Protocol fee policy | | Protection-holder share | 80% | Protocol fee policy | | Token Protection contention window | 1 hour | Protection policy | | Minimum token age for protection | 1 hour | Protection policy | | Minimum qualifying volume for protection | 100 USDC, excluding creator trades | Protection policy | | Minimum holders for protection | 5 non-creator holders | Protection policy | | Minimum liquidity for protection | 500 USDC | Protection policy | | Maximum holder concentration for protection | 75% of circulating holdings | Protection policy | | Active Token Protection term | 7 days | Protection policy | | Token Protection dormant period | 24 hours | Protection policy | | Fixed Creator + Community pool | 70% of USDC-side LP fees | Contract/deployment policy | | Default Creator share | 60% | Genesis policy default | | Default Community share | 10% when enabled | Genesis policy default | | Launch-time Community range | 10%–70% when Community Mode is enabled | Genesis policy bounds | | Launch-time Creator range | 0%–60%, derived as 70% − Community | Genesis policy bounds | | Default Staking share of Community | 50% | Genesis policy default | | Staking share of Community range | 20%–80% | Genesis/governance bounds | | InfoFi share of Community | Remainder after Staking | Derived policy | | Referral share | 5% when active | Launch-time signed terms | | Genesis Launch Partner pool share | 5% when campaign is active | Time-bounded deployment policy | | Fully loaded protocol residual | 20% when Community + referral + Genesis are all active | Derived fee routing | | Referral duration | 30 days | Contract-version constant | | LP USDC collection minimum | 1 USDC | Contract-version constant | | Creator alignment target | 3% supply | Deployment policy | | Alignment tolerance | 0.1% supply | Deployment policy | | Alignment grace | 7 days | Deployment policy | | Voting delay | 1 hour | Deployment policy | | Voting period | 3 days | Deployment policy | | Execution delay | 2 days | Deployment policy | | Proposal threshold | 1% | Deployment policy | | Quorum | 10% | Deployment policy | For a Community-enabled launch, the selected Community share and Staking/InfoFi split are initialized as the genesis policy from **epoch 1**. No governance vote is required to establish those starting values. After launch, governance can increase Community from its established floor and can change the Staking/InfoFi split within the 20%–80% bounds for future eligible epochs. The protocol fee share is a residual after eligible Creator, Community, referral, and Launch Partner destinations are calculated. Because Creator + Community remain fixed at 70%, changing their internal split does not change the protocol residual. See [Fees and economics](/economics/fees.md) for the complete matrix. Selecting Token Protection does not activate it. The launch must satisfy the protection policy before the exact name + ticker pair is protected. See [Token Protection](/launching/token-protection.md) for how qualification, activation, expiry, and duplicate launches work. --- # 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/networks-and-reference/parameters.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.