> 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/42-outcome-tokens.md).

# 42 Outcome Tokens

Everything you need to know about 42 market's outcome tokens.

Outcome Tokens are the core assets issued by 42. Each token represents a specific, mutually exclusive outcome of a future event. These tokens are fully transferable, trade continuously throughout the event lifecycle, and settle objectively at resolution.

### **Transferability**

Outcome Tokens are fully transferable on-chain assets. Once minted, they behave like standard tokens ([`ERC-6909` standard](https://eips.ethereum.org/EIPS/eip-6909)) and are not confined to a single interface or execution venue.

In practice, this means Outcome Tokens:

* Can be moved freely between wallets
* Can be held, transferred, or traded externally
* Are not bound to the 42 interface for ownership or custody

This ensures that eventcoins remain composable and interoperable, while still settling deterministically at resolution.

To dive deeper into how Outcome Token works, refer to the following sub-sections:

* [Pre-Resolution](https://docs.42.space/getting-started/protocol-mechanics-101/42-outcome-tokens/market-discovery-pre-resolution.md)
* [Post-Resolution](https://docs.42.space/getting-started/protocol-mechanics-101/42-outcome-tokens/post-resolution.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 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/42-outcome-tokens.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.
