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

# The SPIN Cycle

**Why These Rewards Last**

Every reward is funded from one of two capped sources. Platform revenue funds the weekly buyback, rakeback, cashback and boosts, and every player-facing rate is calculated on the house edge, not on turnover, so rewards scale with what the house actually earns and can never be gamed into paying out more than it makes.

The Player Rewards & Airdrops pool (125,000,000 $SPIN, 12.5% of supply) funds Play & Earn, presale staking and airdrops on a published, declining schedule, with the buyback taking over as the engine as revenue grows.

No hidden inflation. No promises the maths cannot keep. The reward budget grows only when the house grows, which is exactly what keeps the wheel turning.

## A Week in the Life of a Live $SPIN Holder

Maya stakes 100,000 $SPIN, Dolphin tier. This week she wagers $2,000, mostly in $SPIN, and ends the week $150 down.

* Rakeback landed instantly on every bet, all week, roughly $9 in $SPIN at Dolphin's boosted rate.
* Monday morning: 10% cashback on her $150 net loss. $15 in $SPIN, automatic.
* She used 5 of her 6 weekly Odds Boosts on the Boxing, and every $SPIN sports bet carried the permanent uplift.
* Her points from the week convert to more $SPIN at month end, and because her presale tokens are still vesting, every dollar she wagered also unlocked 2 of them early (see [Vesting](/spin-token/vesting.md)).
* Sunday evening: her share of the weekly staking pool arrives, bought off the open market by the house's own revenue, landing already staked.

Everything Maya earned is real $SPIN. She can stake it and climb toward Shark, bet it at 1.5× rates, or hold it while the weekly burn shrinks the supply beneath her. She lost $150 playing this week and ended it a bigger stakeholder in the house than she started.

## All This and More Coming After Listing

Three more ways to win are already in the plan for after listing, in the order they will arrive:

<img src="/files/Ca9qoThMr8WBs0whkiN2" alt="" data-size="line"> **Token Boosters**, a small chance on every staker's bet of a surprise payout multiplier, from 1.05× nudges to rare 2× to 5× hits (the house pays the bonus; game results never change).

<img src="/files/e2oj6TnLhZWzoSohdWHA" alt="" data-size="line"> **Community jackpots**, shared parlay pools for the big tournaments, split between everyone who hits the week's challenge.

<img src="/files/inA8dVRFepppwKrkazwC" alt="" data-size="line"> **Seasonal leaderboards**, casino and sports, with prize pools worth clearing your calendar for.

Staking $SPIN is the ticket into all three.


---

# 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.chainspin.com/rewards/the-spin-cycle.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.
