> For the complete documentation index, see [llms.txt](https://shakestock.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shakestock.gitbook.io/whitepaper/stock-rewards.md).

# Stock Rewards

How SHAKESTOCK turns Shake Coins into on-chain stock rewards, from choosing an asset to receiving the token in your wallet.

Users use Shake Coins to claim tokenized stock rewards. The reward is not a discount or an abstract in-app benefit. A successful claim delivers a stock token to the user's wallet on Robinhood Chain.

### System overview

The reward path connects phone activity with an on-chain asset:

```
Shake phone
  → Earn Shake Coins
  → Choose a stock
  → Enter Shake Coins to spend
  → Confirm claim
  → Smart contract processes transaction
  → Stock token lands in wallet
  → Verify on Blockscout
```

The SHAKESTOCK token, Shake Coins, and stock tokens have separate roles. Keeping them distinct explains how a claim works.

| Component   | Role                                                                                                                        |
| ----------- | --------------------------------------------------------------------------------------------------------------------------- |
| SHAKESTOCK  | Tradeable token on Robinhood Chain and access requirement. Holding 1,000 SHAKESTOCK provides access to stock reward claims. |
| Shake Coins | Off-chain, non-tradeable, non-transferable points used to make a claim.                                                     |
| Stock token | The ERC-20 tokenized stock reward delivered after a successful claim.                                                       |

{% hint style="info" %}
Shake Coins determine the claim. They are not themselves sent to the blockchain. The claimed stock token is the on-chain asset.
{% endhint %}

### From activity to wallet

Shaking earns Shake Coins within SHAKESTOCK. A user then selects an available asset and chooses how many Shake Coins to spend. The claim requires confirmation and network gas paid by the user.

The smart contract processes the claim on Robinhood Chain. After successful processing, the tokenized stock reward arrives in the user's wallet. The resulting transaction can be checked on Blockscout.

### Explore the reward system

Each child page covers a different part of the same flow:

* **Available Stocks** defines the day-one stock and ETF assets users can claim.
* **Claiming Stock** details the claim request, gas payment, contract execution, and verification path.
* **Tokenized Stock** explains the ERC-20 reward, self-custody model, supported handling, and limitations.

The available asset list can expand over time. Only the six assets specified in Whitepaper v1.1 are documented as available from day one.


---

# 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://shakestock.gitbook.io/whitepaper/stock-rewards.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.