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

# Tokenized Stock

How SHAKESTOCK represents stock rewards as ERC-20 tokens on Robinhood Chain and what users can do with the claimed assets.

The reward is not a coupon. It is not a discount. It is represented on-chain as an ERC-20 token.

SHAKESTOCK Whitepaper v1.1 states that all stock rewards are ERC-20 tokens on Robinhood Chain. After a successful claim, the token is the stock reward that arrives in the user's wallet.

### Technical model

```
Underlying stock exposure
        ↓
Tokenized representation
        ↓
ERC-20 token
        ↓
Robinhood Chain
        ↓
User wallet
```

This model describes the representation stated in the whitepaper. It does not define a contract address, custody provider, settlement process, redemption mechanism, or other underlying infrastructure.

### What tokenization means here

Tokenization represents the stock reward as a blockchain token. The claimed token:

* exists on Robinhood Chain;
* is held in the user's wallet;
* can be verified through its on-chain claim transaction.

The whitepaper states that users can hold, transfer, or sell tokenized stock assets. These actions concern the tokenized reward, not the off-chain Shake Coin balance.

| Capability            | Supported by source |
| --------------------- | ------------------- |
| Hold                  | Yes                 |
| Transfer              | Yes                 |
| Sell                  | Yes                 |
| On-chain verification | Yes                 |

### Ownership and custody

SHAKESTOCK describes the model as self-custodial: “Your tokens in your wallet. Your stock in your wallet. We don't hold them.”

In this stated model, the claimed token is held in the user's wallet. This is a product description, not a legal conclusion about the underlying instrument.

### On-chain visibility

Every completed claim creates an on-chain transaction on Robinhood Chain. Users can verify that transaction on Blockscout.

This creates an observable record of the claim and token delivery. Blockscout is an explorer and verification layer. It does not execute the claim.

### Holding, transfers, and sales

The whitepaper supports three ways to handle a claimed stock token:

| Action   | Meaning in the stated model                                           |
| -------- | --------------------------------------------------------------------- |
| Hold     | Keep the token in the user's wallet.                                  |
| Transfer | Move the token to another wallet, subject to applicable restrictions. |
| Sell     | Sell the tokenized stock asset.                                       |

No specific interface, venue, or trading flow is specified. This documentation does not assume one.

### Important limitations

{% hint style="warning" %}
Tokenized stock represents exposure to the underlying instrument. It is not a physical share certificate. Some stock tokens may have transfer restrictions. Check applicable restrictions before transferring a token.
{% endhint %}

On-chain visibility does not remove all asset or platform risks. The whitepaper does not specify custody arrangements, collateralization, or redemption. Those mechanisms are not implied by ERC-20 representation.


---

# 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/tokenized-stock.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.