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

# Roadmap

SHAKESTOCK's development path from initial launch and ecosystem growth to optimization, anti-cheat improvements, and broader stock support.

This roadmap describes the intended evolution of SHAKESTOCK from initial launch into a broader stock-reward platform. The whitepaper defines a sequence of development milestones, not dated commitments.

### Launch

Launch establishes the core product path from on-chain infrastructure to public access. This milestone connects the foundations described in [Technology](/whitepaper/technology.md) and [Stock Rewards](/whitepaper/stock-rewards.md).

Planned objectives:

* Launch SHAKESTOCK on PONS V2.
* Deploy the smart contract.
* Fund the reward pool.
* Open the Mini App to the public.

```
Mini App
   → Smart Contract
   → Reward Pool
   → Public User Access
```

### Growth

Growth focuses on product presence, documentation, communication, and user acquisition. These objectives support discovery and participation around the initial product.

| Area             | Objective        |
| ---------------- | ---------------- |
| Product presence | Landing page     |
| Documentation    | Whitepaper       |
| Growth           | Referral program |
| Communication    | Telegram + X     |

The planned work includes a live landing page, a published whitepaper, an active referral program, and announcements through Telegram and X.

### Optimize

Optimization uses observed product data to refine system parameters and improve the user experience. It strengthens the operating model after the core product is available.

Development objectives include:

* Monitor data.
* Adjust parameters.
* Deploy anti-cheat Phase 2.
* Deliver UX improvements.

Anti-cheat Phase 2 refers specifically to the anti-cheat development path. It does not define the roadmap structure. See the [Anti-Cheat System](/whitepaper/anti-cheat-system.md) and [Technology](/whitepaper/technology.md) for related controls and architecture.

### Expand

Expansion broadens the initial asset set and strengthens the platform. This milestone targets product capability, assurance work, and larger-scale operation.

Planned objectives:

* Add more stocks.
* Introduce premium features with **2x rewards**.
* Complete a third-party audit.
* Scale bigger.

The whitepaper plans the third-party audit after launch. It does not identify an audit firm or date. Expansion relates to [Stock Rewards](/whitepaper/stock-rewards.md) and [Security & Risk](/whitepaper/security-and-risk.md).

### Roadmap at a glance

```
Launch
Core infrastructure and public Mini App
       ↓
Growth
Product presence and user acquisition
       ↓
Optimize
Data-driven refinement and anti-cheat improvements
       ↓
Expand
More assets, premium features, audit, and scaling
```


---

# 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/roadmap.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.