> For the complete documentation index, see [llms.txt](https://docs.stoxa.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoxa.app/usdstoxa-1.md).

# $STOXA

{% hint style="info" %}
**Not yet launched.** The contract address will be published here on launch. Anything claiming to be $STOXA before then is not.
{% endhint %}

### What it is

A fixed-supply token, fair-launched on [Flap](https://flap.sh), trading on PancakeSwap V3.

|         |                                                      |
| ------- | ---------------------------------------------------- |
| Supply  | **Fixed.** No mint function, no inflation            |
| Launch  | Fair launch on Flap — no presale, no team allocation |
| Trading | PancakeSwap V3                                       |
| Tax     | **3% buy / 3% sell**                                 |

### What the tax does

This is the part that matters. The trading tax does not go to a treasury that sits there — it is routed straight back into the machine:

```
3% of every trade
   ├─ ⅓  →  the jackpot card
   └─ ⅔  →  the bankroll vault
```

**One third grows the jackpot.** It buys the jackpot stock and tops up the single growing certificate, so the top prize gets bigger as the token trades. Irreversible — that money only ever leaves to a winner.

**Two thirds deepen the bankroll.** It is deposited into the Bankroll Vault, which is what backs every payout and what caps how many people can spin at once. A deeper vault means the larger packs can be enabled and more spins can run concurrently.

So trading volume makes the game bigger, not the team richer.

### How the routing works

A keeper process sweeps the tax wallet on a timer:

1. reads the accumulated BNB, leaving a gas reserve
2. swaps the whole amount to USDT in **one** hop
3. splits the USDT **actually received** — not a quote — and sends ⅓ to `fundJackpot()` and ⅔ to `deposit()`

It runs every 3 minutes but only fires above a minimum threshold, so it does not burn gas moving dust. The treasury leg is executed **before** the jackpot leg, because the jackpot is irreversible — if anything is going to fail, it fails before money is committed to a pot with no withdrawal.

### Addresses

|                   |                                                                                                                        |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------- |
| $STOXA            | *published at launch*                                                                                                  |
| Tax wallet        | [`0xAA6E068c4872CDcDCac423882E4EFDe0b1d49c1E`](https://bscscan.com/address/0xAA6E068c4872CDcDCac423882E4EFDe0b1d49c1E) |
| Bankroll Vault    | [`0x73D1269Ff347b16199de3a4Ddf32359718da026C`](https://bscscan.com/address/0x73D1269Ff347b16199de3a4Ddf32359718da026C) |
| Machine (jackpot) | [`0xD9361C1C160CB056fc4227E1ce18737b3214eEBb`](https://bscscan.com/address/0xD9361C1C160CB056fc4227E1ce18737b3214eEBb) |

Every sweep is visible on chain: `JackpotFunded` on the Machine and `Deposited` on the vault. You can verify the tax is doing what this page says it does, without trusting the page.


---

# 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.stoxa.app/usdstoxa-1.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.