# Mechanism

Multiplier is built on a simple but powerful mechanism:\
**Every win = live market buy.**

This turns entertainment into programmable liquidity routing, making play the driver of token demand and community growth.

***

### How It Works

1. **Play a Game**\
   Users enter any Multiplier original or integrated third-party game.
2. **Win Tokens**\
   Outcomes are determined by fair-odds **pRNG** and oracle-based resolution.
3. **Automatic Market Buy**\
   Every win routes capital into a **real spot market purchase** of the curated token.
4. **Credit to Player**\
   Tokens are credited directly to the player’s account — visible, tradable, usable.
5. **Onchain Receipts**\
   All purchases are recorded transparently, with receipts verifiable on Solana.

***

### Why It Matters

* **Continuous Buy Pressure**\
  Each play generates organic demand.
* **Verifiable Liquidity**\
  No vanity points — real tokens, real markets.
* **Positive-Sum Gaming**\
  Gameplay becomes a distribution channel, sustaining token communities.
* **Loss Protection**\
  Even if you lose, you earn **MINT cashback** for free plays and progression in the leaderboards and eligibility for curated token airdrops. 

***

### Example Flow

* Player wagers $10.
* Wins a round → triggers $10 buy of curated token.
* Token credited to player wallet.
* Live chart reflects buy pressure.
* Community sees impact in real time.

***

### The Big Picture

Multiplier’s mechanism transforms:

* **Players** into token holders.
* **Games** into liquidity routers.
* **Communities** into active market makers.

This is the foundation of **gamified capital markets**.


---

# 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.multiplier.fun/mechanism.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.