> For the complete documentation index, see [llms.txt](https://nexon-3.gitbook.io/nexon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nexon-3.gitbook.io/nexon-docs/appendix/open-parameters.md). # Open Parameters The list of economic, governance, product, operational and jurisdictional fields awaiting the project's written decision, and the rule for closing them. The current mechanism finalised on 10 September 2026 closes the principal economic questions: the two asset roles, the deposit split and fuel wallet, settlement every 12 hours at 0.3% – 1.0%, term bonuses, the exit window, three settlement speeds and their burns, the three sale tiers with the 3:1 pairing, the 1,095-day release, 20 generations of referral rewards and V1 – V12 leadership bonuses. The narrative addendum of 8 September closes the brand meaning, the two-asset narrative and the direction of the five products. The implementation fields below **remain the project's to decide in writing**. ## Economics | ID | Field | Why it matters | | ------ | ----------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | | OP-T01 | When the subscription-to-stake pairing switches from 3:1 to 1:1 after listing | Sets the end of the private-sale pairing | | OP-T02 | Execution rates for leadership bonuses V1 – V12 | Published externally as ranges; execution rates are set by market stage and recorded by parameter version | | OP-T03 | Stage adjustments to the per-settlement range | 0.3% – 1.0% is the current range; adjustments take effect by parameter version | ## Legal and security | ID | Field | Why it matters | | ------ | ------------------------------------------------------------------------- | ---------------------------------------------------------- | | OP-L01 | Eligible jurisdictions and participant categories | Legal availability | | OP-L02 | Responsible legal entities and service-provider terms | Accountability and disclosure | | OP-S01 | Contract addresses, audits and control design | Technical verifiability | | OP-G01 | The XO governance framework: scope, eligibility, thresholds and execution | Turns governance from a stated function into defined rules | ## Products | ID | Field | Why it matters | | ------ | ---------------------------------------------------------- | ----------------------------------------------------- | | OP-P01 | PayFi actions, fees, settlement assets and executors | Makes routes measurable and accountable | | OP-P02 | Wallet custody, recovery, network and permission standards | Who controls assets and how access is recovered | | OP-P03 | Prediction-market protocols, settlement and eligibility | Separates third-party responsibility and legal access | | OP-P04 | Marketplace suppliers, payment, refund and dispute terms | Where responsibility for real-world fulfilment sits | | OP-P05 | Stablecoin Card issuer, jurisdictions, assets and fees | Establishes the responsible regulated product | | OP-P06 | Social protocol, governance, privacy and promotion rules | The operating model of decentralized social | ## Data, AI and operations | ID | Field | Why it matters | | ------ | ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | | OP-D01 | Price and market-data providers, cross-check tolerance bands, quote validity | Determines the price at which a route is built | | OP-D02 | Accepted KYC / AML credential providers | Determines who issues identity references | | OP-A01 | AI models, policy engine, authorisation format and limits | Makes agent behaviour testable and revocable | | OP-O01 | Launch order and service levels for the Wallet, the Marketplace, decentralized social and the Stablecoin Card | Separates capability gates from calendar commitments | ## The closure rule An open field is closed by a subsequent written decision that states: the approver, the basis, the effective scope, the version, and the products affected. Then the fact registry, both documentation trees, user disclosures and the validation tests are updated **together**. Three things that cannot close a field: * **A narrative position cannot close an economic field.** * **A product mock-up cannot close a custody or legal field.** * **A third-party announcement cannot close a NEXON operational field** unless the responsibility is documented. Conflicting older material stays archived and is never used to fill a gap. *Previous:* [*Legal Disclaimer*](/nexon-docs/appendix/legal-disclaimer.md) --- # 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://nexon-3.gitbook.io/nexon-docs/appendix/open-parameters.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.