> 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/staking.md).

# Staking

<img src="/files/SMeBmIfcRrxxltcTsVyO" alt="" data-size="line"> **Where the Rewards Come From**

Staked $SPIN does three things at once: it sets your VIP tier, it earns your share of the weekly buyback rewards, and it takes supply off the market.

Where post presale staking rewards come from: 40% of every weekly buyback (see [Buyback & Burn](/spin-token/buyback-and-burn.md)) is distributed to stakers, pro-rata. Tokens are purchased from the open market with the house's own revenue.

Paying stakers this way adds buying pressure to $SPIN instead of sell pressure. Rewards land already staked by default, so your position climbs the ladder on its own; unstake them any time if you would rather take them liquid.

**Presale staking:** presale buyers stake from the dashboard before the token even lists, earning from the Player Rewards pool. At listing, presale stakes carry straight into live staking, same balance, tier active from minute one, locked tokens included.

Stakers also unlock higher betting limits and staker-only tournaments as they climb.

{% hint style="info" %}
**On the contracts.** The staking and vesting contracts are finalised and independently audited before listing, not after. That work sits in Q4 2026 on the [Roadmap](/roadmap.md), alongside publishing the buyback wallets, the burn address and the multisig. Every mechanism described in this paper is meant to be inspectable before a single token trades.
{% endhint %}


---

# 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/staking.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.