# Introduction

### What is 42?

42 is a decentralized, on-chain asset issuance protocol designed for both **information expression** and **speculative trading**.&#x20;

To put it simply:

*42 is an asset issuance protocol where event outcomes trade like liquid tokens and settle like prediction markets.*

Traditional prediction platforms rely on fixed odds, suffer from liquidity fragmentation, and often require external liquidity bootstrapping. 42 solves this through a **curve-based pricing mechanism** that supports liquidity natively where 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 at the traditional *‘maximum $1 return’*. 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: 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:

```
GET https://docs.42.space/getting-started/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
