> 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/on-chain-verification.md).

# On-Chain Verification

How SHAKESTOCK claims become verifiable blockchain transactions and how users can inspect the resulting record on Blockscout.

Every stock claim creates an on-chain transaction. Users can verify that transaction on Blockscout.

The claim is not only an internal application entry. It produces a blockchain transaction record that can be inspected independently.

### Verification flow

```
Stock claim
  → Transaction submitted
  → Robinhood Chain
  → Transaction confirmed
  → Blockscout
  → Public verification
```

The smart contract executes and enforces the claim. Robinhood Chain records the blockchain transaction. Blockscout exposes the resulting record for inspection.

### What the record can show

The transaction record can provide evidence of the completed on-chain claim. Depending on what the explorer exposes, users can inspect:

* transaction existence, status, hash, and block inclusion;
* sender and recipient or contract interaction;
* token transfer information.

The whitepaper does not promise specific explorer fields or a specific Blockscout interface. The verification model depends on the resulting on-chain record, not a particular UI layout.

### Permanent and auditable record

Whitepaper v1.1 describes every claim as an on-chain transaction with a permanent record. That record provides an auditable history of the executed claim and resulting token delivery.

It does not, by itself, prove the economic value of the stock token. It also does not establish legal or regulatory ownership of an underlying financial instrument. On-chain token ownership and legal ownership are separate concepts.

### Stated self-custody model

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

This describes the product's stated self-custodial token model. It remains separate from the legal status of tokenized stock.

### Unique claims

The system states that each claim is unique and cannot be used twice. The transaction record provides the observable history of claims that have executed.

The whitepaper specifies the replay-protection property but not its implementation. No claim identifier, nonce structure, signature scheme, or contract storage design is assumed.

### Verification is not execution

| Component       | Responsibility                                                 |
| --------------- | -------------------------------------------------------------- |
| Smart contract  | Executes and enforces the on-chain claim.                      |
| Robinhood Chain | Records and settles the blockchain transaction.                |
| Blockscout      | Lets users inspect and verify the resulting blockchain record. |

{% hint style="info" %}
Blockscout is an explorer and verification layer. It does not execute claims or determine their outcome.
{% 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://shakestock.gitbook.io/whitepaper/technology/on-chain-verification.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.