> For the complete documentation index, see [llms.txt](https://spawnmeme.gitbook.io/spawnmeme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spawnmeme.gitbook.io/spawnmeme-docs/whitepaper/12-roadmap.md).

# 12. Roadmap: The Hatching Plan

### Six chapters

The Hatching Plan organizes SPAWN around the creator and participant journey. Its interactive page opens on **Next to hatch**, while earlier chapters explain the tools already described as live in the platform roadmap.

“Live” refers to the documented chapter capabilities, not a guarantee that every provider, asset or transaction is available at every moment. “Exploring” means a direction is under consideration, without a committed release date.

| Chapter              | Focus                                                      | Status for this edition |
| -------------------- | ---------------------------------------------------------- | ----------------------- |
| 01 · Dream it        | Spawn AI, Studio & Kit, project pages                      | Live                    |
| 02 · Hatch it        | Solana launches, Meteora bonding curves, creator dashboard | Live                    |
| 03 · Find your orbit | Feed, Markets, Swap, Wallet, Explorer and Incinerator      | Live                    |
| 04 · Build the Nest  | Community buy bots, Trending, quests and referrals         | Live                    |
| 05 · Make it yours   | NFT collections, creator airdrops and project visibility   | Live                    |
| 06 · Next to hatch   | Directions for SPAWN's next stage                          | Exploring               |

### Buy bots beyond the curve

The roadmap explores support for graduated pools and broader monitoring capacity. These would extend community alerts beyond the current active-bonding-curve coverage. This paper does not treat that support as already available.

### Deeper creator insights

Clearer project-level activity and community insights could help creators understand how people use their pages and tools. This direction requires attention to data quality and useful interpretation, rather than presenting activity totals as proof of project value.

### A smoother first launch

Guided creation, helpful templates and improvements inside mobile wallet browsers are being explored to make the first launch easier to understand. Wallet review and accurate confirmation remain important even when the interface becomes simpler.

### Community feedback and updates

The roadmap is intended to evolve with testing, usage and specific community feedback. A useful request explains the task, the current difficulty and the desired result. Suggestions can be shared through the community or the public GitHub repository.

The [interactive roadmap](https://spawnmeme.com/roadmap?stage=incubator) is the reference for changes after this dated edition. Exploring items are not contractual delivery commitments.

### October 9 live additions

The October 9 release includes live limit orders, private Telegram token alerts, Top holders, rich share links, content reports, published Projects, Status checks and Responsible disclosure. Availability still depends on the feature’s documented coverage and prerequisites.

These additions are live features, not future delivery commitments. Broader post-graduation Buy Bot monitoring remains a separate roadmap direction.

### October 10: creator curve earnings

Eligible creator-fee launches can now earn about 0.25% of each bonding-curve trade, with wallet-signed claims in the Creator Dashboard. Legacy pool settings remain unchanged. 50. Claim your creator fees documents the live workflow.

### October 12 documentation update

The reviewed application adds Android APK access and Mobile wallet, creator profiles, activity leaderboards and badges, wallet-based Nest participation, token-lock visibility, legacy metadata locking, RugCheck reports and DEX paid status. The Solana dApp Store submission is under review, embedded holder maps depend on configuration, and the Blink button is disabled. These distinctions separate available interfaces from conditional or paused features.

***

Previous: 11. Security, controls and limitations · Next: 13. Public resources and participation


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://spawnmeme.gitbook.io/spawnmeme-docs/whitepaper/12-roadmap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.