> 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/protocol-mechanics-101/glossary.md).

# Glossary

Key terms and concepts specific to 42 markets.

**Eventcoins**\
A new asset class representing mutually-exclusive outcomes of a future event, issued as fully transferable tokens that trade continuously and settle objectively at resolution.

**42 Market**\
A novel launchpad-like market structure where prices evolve continuously during the event, but final payouts are determined collectively at resolution from the total collateral pool.

**Outcome Tokens**\
ERC-6909–style tokens representing a specific outcome of an event. They are fully transferable during the market lifecycle and exhibit ERC-20–like behaviour. Upon resolution, the winning Outcome Token(s) redeem a pro-rata share of the total collateral pool.

**Power Curve**\
The endogenous pricing function that governs minting (buy) and redemption (sell) of Outcome Tokens based on supply and orderflow.

**Redeem Tax**\
A dynamic market-level spread applied on redemption that reflects supply impact, liquidity depth, and time-to-resolution, with proceeds retained in the settlement pool.

**Resolution**\
The deterministic process by which a single outcome is declared correct based on predefined rules and oracle inputs.


---

# 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/protocol-mechanics-101/glossary.md?ask=<question>&goal=<user_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.
