> 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/chainspin/executive-summary.md).

# Executive Summary

Gambling, as we know it, is changing.

Over the past decade, blockchain and online gambling have grown into each other. The result is a sector people now call GambleFi: casinos and sportsbooks that run on crypto rails and reward players with a token that has real market value.

Online gambling is worth hundreds of billions a year, but the legacy version carries old problems. Payments are slow and expensive. Licensing stops at borders. And reward programmes are designed in the dark: points, comps and VIP deals that mean whatever the operator decides they mean this month.

Crypto fixed the payments part. Deposits and withdrawals settle in minutes, fees are a fraction of card processing, and anyone with a wallet can play. That is why crypto-native casinos have grown so fast.

Other market participants then proved something bigger: connect a token to the casino's revenue and you get a wheel. Players buy the token and play with it, the platform's income buys it back off the market, and holding it becomes more attractive as the platform grows. Activity feeds demand. Demand rewards activity.

But the first generation of GambleFi is incomplete, and players know it. The tokens were mostly passive. Reward rates said "up to" and paid less. Earning mechanics disappeared overnight. And the loudest complaint against every major crypto casino is the same one: fast deposits, frozen withdrawals. The economics worked. The trust didn't.

Chainspin is built as the second generation: keep the wheel turning, prove everything.

The platform is live and licensed today, with thousands of slots and live tables, a full sportsbook, and prediction markets on the way. At the centre is $SPIN: a fixed supply of one billion tokens that can only shrink.

$SPIN is not a badge. It does things. Stake it and you climb six VIP tiers, from Shrimp to Whale, each paying better rakeback on every bet, bigger weekly cashback, more odds boosts and more freebets. Bet with $SPIN itself and every reward pays extra. Presale buyers stake from day one, before the token even lists, and their locked tokens keep earning through one simple, published unlock timeline that playing can speed up.

Then the platform holds up its end. Every week, a fixed share of revenue buys $SPIN on the open market. 60% is burned forever. 40% goes back to stakers. Every burn, every unlock and our real payout speed sit on a public dashboard anyone can verify on-chain. We publish our burns and our payouts.

So the Chainspin position is simple: players hold a piece of the engine they play in. As the platform grows, the token gets scarcer, stakers earn more, and every step of it can be checked.

The rest of this paper shows exactly how: the tiers, the rewards, the unlock schedule, the buyback maths, and the player protections behind them.

Welcome to the next generation.


---

# 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/chainspin/executive-summary.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.