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

# Claiming Stock

A detailed walkthrough of the stock claim transaction, from selecting an asset and spending Shake Coins to smart contract execution and on-chain verification.

Claiming stock is where an off-chain Shake Coin balance produces an on-chain stock reward. Shake Coins are internal points used to determine the claim. The stock reward is the token delivered by the smart contract.

```
Shake Coins → claim request → smart contract → Robinhood Chain → stock token → user's wallet
```

### Claim flow

#### 1. Select a stock

Open the Telegram Mini App and choose a supported asset. For example, a user can select **NVDA** from the available stock list.

#### 2. Enter Shake Coins

Enter the number of Shake Coins to spend. This amount determines the value of the stock reward being claimed within the system.

The whitepaper does not specify a pricing formula. A claim amount should not be treated as a quoted market price.

#### 3. Confirm the transaction

Confirm the claim transaction in the Mini App. The user pays the required network gas for this transaction.

#### 4. Execute the smart contract

The smart contract processes the claim on Robinhood Chain. This step creates the on-chain transaction for the stock reward.

#### 5. Receive the stock token

After successful processing, the tokenized stock reward lands in the user's wallet. This ERC-20 token is the claimed asset.

#### 6. Verify the result

Check the completed transaction on Blockscout. The explorer provides an observable on-chain record of the claim.

### Technical transaction path

```
User
  → Telegram Mini App
  → Stock selection
  → Shake Coin amount
  → Claim transaction
  → Smart contract
  → Robinhood Chain
  → Stock token
  → User wallet
```

The Mini App collects the asset selection and Shake Coin amount. Confirmation submits the claim transaction. The smart contract processes that transaction on Robinhood Chain, then the resulting stock token is delivered to the wallet.

### What happens on-chain?

The claim becomes an on-chain transaction when the smart contract processes it on Robinhood Chain. The on-chain result is the stock token arriving in the user's wallet.

Shake Coins are not transferred on-chain as a token in this flow. They remain the internal points used for the claim decision.

{% hint style="info" %}
The SHAKESTOCK token is also separate from this transaction. It is the tradeable Robinhood Chain token and access requirement. Holding 1,000 SHAKESTOCK provides access to stock reward claims.
{% endhint %}

### Gas

The user pays their own network gas when confirming a claim. The whitepaper characterizes Robinhood Chain gas as small, but no specific amount is guaranteed here.

Gas is the network cost for submitting and processing the on-chain claim transaction. It is separate from the Shake Coins spent to determine the stock reward.

### Verification

Blockscout is the verification and explorer layer for the completed transaction. It does not execute the claim or decide its outcome.

Use the resulting transaction record to observe the on-chain claim. The smart contract on Robinhood Chain performs the 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/stock-rewards/claiming-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.