> 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/what-is-stoxa.md).

# What is Stoxa

<figure><img src="/files/HTpBGwtbqzq0VyWojutU" alt=""><figcaption></figcaption></figure>

## Redefining how the world discovers and owns tokenized equities

You pay for a spin in BNB. Chainlink VRF draws a rarity tier. A card comes off the shelf and lands in your wallet  and that card is an NFT holding actual tokenized shares of SPY, Tesla, NVIDIA, Microsoft or SpaceX (more to be added).

Not a picture of a stock. Not a points balance. The certificate is redeemable for the underlying token at any time, by you, without anyone's permission.

***

### The one thing that makes it different

Most gacha economies are closed loops, you win a token that only has value because the operator says it does, and the only exit is selling to the next player.

Stoxa's prizes have a price that has nothing to do with Stoxa. A card holding $18.80 of NVDA is worth $18.80 of NVDA whether the machine has a thousand players or none. The house cannot inflate it and cannot devalue it.

That property comes from how cards are made. Every card is minted by spending real USDT on a real DEX swap:

```
face value of a card  ==  USDT actually spent acquiring its shares
```

There is no oracle, no admin-set price, no mark-to-model. The house cannot print a card worth more than it paid, because the payment *is* the minting.

### What you can do here

|                      |                                                                |
| -------------------- | -------------------------------------------------------------- |
| **Spin**             | Pay in BNB, win a card off the rack                            |
| **Hold**             | The card is yours; the shares behind it move with the market   |
| **Unwrap**           | Burn the card, take the raw stock token. Nobody can block this |
| **Sell back**        | Instant exit to the house at face for 2 days after winning     |
| **Consign**          | Lend a card back to the machine and earn a cut of every spin   |
| **Provide bankroll** | Deposit USDT, take the other side, earn the house edge         |

### Where it runs

BNB Smart Chain (chain 56). Randomness is Chainlink VRF v2.5. Swaps route through PancakeSwap V3. Settlement is in USDT.

Everything the machine owes you is settled on chain. The website is a convenience; the contracts are the product.

{% hint style="info" %}
**Status:** live on BNB Chain mainnet. Spins, cards, sell-back, red packets, consignment and the bankroll vault are all operational.
{% endhint %}

***

### Start here

* How It Works — the full spin lifecycle
* Spinning — packs, batching, what happens after you pay
* Odds & RTP — every probability, published
* How to Earn — the four ways money comes back
* Fees & Protocol Revenue — where every basis point goes
* Deployments — every deployed address
* Parameters — every tunable, its cap, and who can change it
* Roles — who can call what


---

# 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/what-is-stoxa.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.
