> 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/technology/robinhood-chain.md).

# Robinhood Chain

How Robinhood Chain serves as the execution layer for SHAKESTOCK token transfers, stock claims, and verifiable on-chain state.

Robinhood Chain is SHAKESTOCK's on-chain execution environment. It is where the SHAKESTOCK token and tokenized stock rewards exist, and where stock claim transactions execute.

The chain layer records the completed claim and delivers the resulting stock token to the user's wallet. Blockscout can then expose that transaction for inspection.

### Transaction lifecycle

```
User
  → Claim request
  → Smart contract
  → Robinhood Chain transaction
  → Stock token delivery
  → Wallet
  → Blockscout
```

The application initiates the claim request. Contract execution turns it into an on-chain transaction. After successful processing, the stock reward is delivered as an ERC-20 token to the user's wallet.

At this layer, the claim becomes a permanent blockchain transaction record. The chain is the authoritative record for the executed claim and resulting token ownership.

### State boundary

| State                                       | System layer               |
| ------------------------------------------- | -------------------------- |
| Shake Coin balance and user interaction     | Application / off-chain    |
| Claim transaction and stock-token ownership | Robinhood Chain / on-chain |

Shake Coins are off-chain points. They are not transferred on-chain during a claim. The on-chain result is the tokenized stock reward, not the Shake Coin balance.

### ERC-20 rewards

Whitepaper v1.1 states that stock rewards are ERC-20 tokens on Robinhood Chain. This representation lets the claimed asset exist in the user's wallet as an on-chain token.

The whitepaper does not specify token addresses, decimals, or custom token interfaces. Those details are not implied here.

### Gas

Users pay their own network gas when confirming stock claims. The source describes Robinhood Chain gas as very small, but no fixed gas price or guaranteed cost is documented.

Gas is separate from the Shake Coins used to determine a claim. Shake Coins remain application-layer points.

### Chain dependency

{% hint style="warning" %}
If Robinhood Chain is unavailable, stock claims cannot execute. This is a platform dependency identified by the source.
{% endhint %}

This dependency applies to on-chain claims. It does not mean every application-level SHAKESTOCK function requires chain execution.


---

# 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/technology/robinhood-chain.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.