> For the complete documentation index, see [llms.txt](https://docs.hit.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hit.one/1000x/how-it-works.md).

# How it works

[***1000X***](https://app.hit.one) is our debut game. It's a slot machine for up to 1000x leverage. Yep, you heard that right.

<figure><img src="/files/cQCSlVD1WquTi1E4W84R" alt="" width="375"><figcaption></figcaption></figure>

### How It Works

A spin on Hit One is one self-contained leveraged trade.

You choose a trade amount in USDM. The slot machine selects a market, side, and leverage multiplier. A perpetual futures position then opens on World Capital Markets.

You watch PnL move in real time. You close the position when you want, or it closes automatically if your stop loss is hit.

There is no account balance. Every spin is a fresh trade.

#### The deposit-per-spin model

Most trading platforms ask you to fund an account first. Then they deduct from that balance on each trade.

Hit One does not work that way.

Every spin is its own deposit. You sign one transaction. That USDM becomes the collateral for one position. When the position closes, your collateral plus any profit — or what remains after a loss — is sent back to your wallet.

#### Limits

* Trade amount: `$1` to `$100` USDM per spin, in whole numbers
* One open position at a time per account
* Minimum position size: `$100` notional (`collateral × leverage`)

#### What the slot machine selects

Each spin randomizes three things:

1. **Market** — `BTC`, `ETH`, and `SOL` are live. `HYPE` is coming soon.
2. **Side** — `LONG` or `SHORT`. This is `50/50` on each spin.
3. **Leverage** — between `500x` and `1000x`.

These are not user-configurable.

#### Trade amount, collateral, and position size

These three numbers are different.

Using a `$10` spin at `750x` as an example:

* **Trade amount** — the USDM you put in: `$10.00`
* **Collateral** — what backs the position after the `1%` open fee: `$9.90`
* **Position size** — `collateral × leverage`, or total market exposure: `$7,425`

Position size is why a `1%` price move translates to roughly a `750%` PnL move at `750x` leverage. The downside is capped at the collateral you put up because the position closes before losses can exceed it.

#### Fees

* **Open fee** — `1%` of trade amount
* **Close fee** — `5%` of profit. There is no close fee on losing trades.

#### Worked example

`$10` trade amount at `750x` leverage:

* Open fee: `$0.10`
* Collateral: `$9.90`
* Position size: `$7,425`
* Close in profit at `+$50` → `5%` close fee = `$2.50` → payout = `$57.40`
* Close at a `$5` loss → no close fee → payout = `$4.90`

#### The lifecycle of a spin

1. **Sign** — You sign a USDM transfer for your trade amount.
2. **Spin** — The reels select your market, side, and leverage. Your position opens on the exchange.
3. **Manage** — PnL updates in real time. You can Double Down, Sell `50%`, or Close. See [Game Controls](/game-controls.md).
4. **End** — You close manually, or the stop loss closes the position automatically. A recap shows the result.
5. **Payout** — Collateral plus profit, minus the close fee if there is one, is sent back to your wallet in USDM.


---

# 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.hit.one/1000x/how-it-works.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.