> For the complete documentation index, see [llms.txt](https://docs.yamata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yamata.io/using-yamata/predictions-market/platform-features.md).

# Platform Features

Anyone can create a prediction market on Yamata. No approval needed—simply define your event, set the parameters, and launch your market.

### **Liquidity-Gated Discovery**

Markets begin in the Wild West zone where creators can share links and build initial liquidity. Once a market reaches the liquidity threshold, it graduates to the Public Markets page where it gains visibility to the entire Yamata community.

### **Position Tokens (ERC-1155)**

All commitments receive ERC-1155 token receipts as proof of participation. These tokens represent your position in the market and are required for claiming payouts after resolution.

### **Fully On-Chain**

Every bet, market creation, and resolution happens on-chain for maximum transparency, auditability, and security.

### **Optional: Time-Weighted Rewards**

Early participants can receive higher rewards through beta-weighted distribution—rewarding conviction and early market participation when enabled by the market creator.


---

# 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://docs.yamata.io/using-yamata/predictions-market/platform-features.md?ask=<question>&goal=<endgoal>
```

`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.