> For the complete documentation index, see [llms.txt](https://docs.42.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.42.space/getting-started/quickstart.md). # Introduction ### What is 42? 42 is a decentralized, on-chain asset issuance protocol designed for trading. To put it simply: *42 is an asset issuance protocol where event outcomes trade as liquid tokens with defined settlement rules.* 42 uses a **curve-based pricing mechanism** that supports liquidity natively. Every trade mints or redeems directly against the curve, eliminating the need for pre-seeded liquidity. This architecture unlocks **open-ended upside**. Payouts are not capped. The return profile is shaped entirely by market flow, timing, and the distribution of positions across outcomes. Where recent platforms like Pump.fun popularized purely speculative tokens, 42 introduces **liquid outcome assets:** tokens with **explicit resolution and settlement rules** embedded at the protocol level. These outcome tokens behave like tradable assets with deterministic end states. #### **Why this matters** * **Short-term markets** can exhibit wide payoff ranges and rich trading dynamics. * **Long-term markets** behave like fair memecoins where tokens with real resolution rules that can be listed and traded across external platforms. 42 is an infrastructure built to introduce a **new asset class**. In essence, 42 combines: * the expressiveness an opinion, * the liquidity and dynamics of trading, and * the structural clarity of assets with deterministic settlement. This creates a new category of on-chain markets where **belief, timing, and flow** all translate into tradable, liquid, and ultimately resolvable assets. --- # 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.42.space/getting-started/quickstart.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.