> 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/jackpot-and-golden-egg.md).

# Jackpot & Golden Egg

Two pools that feed off every spin and return to players. Together they are **1.5% of all volume**, and none of it is protocol revenue.

***

### The jackpot

**One card. It never sits on a rack, it grows.**

0.5% of every spin accumulates in a fund. Periodically the restocker calls `growJackpot`, which swaps that fund into the jackpot stock and **tops it up into a single certificate**. The prize compounds continuously rather than being reset.

```solidity
if (jackpotCertId == 0) jackpotCertId = wrapper.wrap(jackpotStock, received);
else                    wrapper.topUp(jackpotCertId, received);
```

Hit the **0.05%** tier and the whole card transfers to you, plus any fund not yet swapped in.

|                  |                                          |
| ---------------- | ---------------------------------------- |
| Odds             | **0.05%** — 1 in 2,000 spins             |
| Feed             | 0.50% of every spin                      |
| Asset            | SPCXB (SpaceX)                           |
| Hard cap on odds | 0.20% — the contract will not allow more |

#### It doesn't touch the vault

The jackpot pre-funds itself. When someone wins it, the payout is the card the feed already bought -- LPs are not on the hook for it, and the tier does not draw against the bankroll.

#### It is one-way

There is no withdrawal path for the jackpot fund. Not gated absent. Money in the pot leaves only to a winner. That applies to the operator too.

***

### The golden egg

**A raffle over recent spins, and the person who triggers it has no advantage.**

1% of every spin feeds the egg. When cumulative spin volume in the current window crosses **$10,000**, the egg cracks on the next settlement and the entire fund is credited to **one randomly chosen spinner from that window**.

```solidity
uint256 count = spinId - start + 1;
uint256 winnerSpinId = start + (keccak256(word, 0xE6) % count);
```

Every spin in the window is equally likely including the very first one. The spinner who happened to push volume over the threshold is exactly as likely to win as anyone else.

The window then resets and starts accumulating again.

|           |                                           |
| --------- | ----------------------------------------- |
| Feed      | 1.00% of every spin                       |
| Cracks at | $10,000 of window volume                  |
| Winner    | uniformly random spin in the window       |
| Payout    | the entire fund, as claimable USDT credit |

#### Why it can't be gamed

The winner is drawn from the **same VRF word** that settled the cracking spin, using a different hash lane (`0xE6`). So it inherits Chainlink's randomness and is independent of the tier and card draws.

You cannot predict which spin will crack it, and you cannot steer the winner by timing your spin the selection is over the whole window, not the moment.

If the selected spin was cancelled rather than settled, the payout falls to the cracking spin instead. That guard exists because a cancelled spin has no player to pay.

#### One spin, one entry

Entry is per spin, not per wallet or per dollar. A $8.88 spin and an $88 spin are the same single ticket which deliberately keeps the egg accessible rather than making it a whale prize.

***

### Where the money actually goes

Of every $100 wagered:

```
$1.00  →  golden egg      →  returns to a random spinner
$0.50  →  jackpot feed    →  returns to whoever hits 0.05%
```

Both are counted in the **91% total return to players**, not in the operator's 2.5%. They are player money in transit, it leaves the vault and comes back to players later, in larger, rarer chunks.

That is the point of them: they move a slice of the return away from the predictable 70%-of-stake common pull and into outcomes worth talking about.


---

# 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/jackpot-and-golden-egg.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.