> 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/smart-contracts.md).

# Smart Contracts

The smart-contract layer that processes stock claims, enforces limits, prevents replay, and exposes protocol parameters on-chain.

Smart contracts are the on-chain enforcement point for stock claims. They process claims on Robinhood Chain, enforce claim constraints, prevent claim replay, maintain transparent reward parameters, and deliver tokenized stock rewards.

They do not validate physical phone movement. Movement detection, device fingerprinting, IP controls, and Telegram identity verification belong to the application layer.

### Claim execution

```
Claim request
  → Validation
  → Contract execution
  → Stock token delivery
  → Transaction receipt
```

The claim request begins in the application layer. Contract execution applies the on-chain claim rules and, after successful processing, produces the stock-token delivery and transaction record.

The whitepaper specifies these responsibilities, not function names or contract interfaces.

### On-chain enforcement

| Mechanism          | Enforcement layer |
| ------------------ | ----------------- |
| Movement threshold | Application       |
| Debounce           | Application       |
| Device fingerprint | Application       |
| IP rate limit      | Application       |
| Telegram identity  | Application       |
| Daily claim limit  | Smart contract    |
| Replay protection  | Smart contract    |
| Token state        | Blockchain        |
| Transaction record | Blockchain        |

This boundary is intentional. Application controls qualify activity. Contract controls determine whether the resulting claim can execute on-chain.

### Replay protection

The whitepaper states that each claim is unique and cannot be used twice. This is the replay-protection property of the claim process.

The source does not define the implementation mechanism. It does not specify a nonce, claim identifier, signature scheme, mapping, or storage variable. Those details should not be inferred.

### Daily claim limit

The smart contract enforces a maximum of **$10 per user per day**. The source places this constraint in the contract, rather than only in a backend service.

This makes the daily cap part of transaction execution. A backend-only limit could theoretically be bypassed if application-layer controls were compromised. The contract-level constraint remains part of the on-chain claim decision.

### Transparent parameters

Reward parameters exist in the smart contract. Parameter changes emit an event and are publicly visible.

Users can inspect parameter state and observe changes through blockchain events. The whitepaper does not name the events or describe their data structure.

### Token properties and administration

The SHAKESTOCK token has a fixed supply and a permanent liquidity lock. These properties apply to the token as stated by the source. They should not be generalized to every contract component.

The source also states that the owner can adjust parameters and withdraw pool funds. A multi-signature wallet is used for the owner. This is an explicit administrative capability and trust boundary.

### Security status

{% hint style="warning" %}
An internal audit is complete. A third-party audit has not yet been completed. Smart-contract bug risk remains.
{% endhint %}

The source does not support describing the system as fully audited or trustless.


---

# 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/smart-contracts.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.