> 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/10-spawn-token.md).

# 10. The SPAWN token

## Identification

SPAWN has an official Solana token. The full mint address is its identifier; names, tickers, images and address suffixes can be copied or confused with other projects.

Use the official [SPAWN website](https://spawnmeme.com/) and the main SPAWN community bot's `/ca` response to obtain the current official mint, then compare it with the token being viewed or transacted. This edition does not freeze a potentially outdated address into every imported copy of the whitepaper.

## Documented holder benefits

The reviewed NFT fee schedule gives wallets holding at least **1,000,000 SPAWN** a **50% reduction in the NFT collection deployment platform fee**. The exact applicable quote is shown before approval. The discount does not imply that storage, network or protocol costs are also halved.

Holding SPAWN is also one documented eligibility path for the creator-airdrop whitelist. Prior qualifying SPAWN trading is an alternative. Eligibility provides access to a selection process, not a guaranteed distribution or financial return.

## Separate from Spawn Points

Spawn Points are off-chain participation records with no cash or token value. They are not an allocation of SPAWN and do not establish an exchange rate, conversion right or future distribution entitlement.

Specific promotions or giveaways must be evaluated under their own published terms. A general community announcement should not be interpreted as a permanent token right.

## Scope of this paper

This whitepaper does not establish equity, dividends, a platform revenue share, staking yield, buyback obligations, voting rights or guaranteed redemption for holders. It describes the documented product benefits without inferring additional rights from the token's association with SPAWN.

Token price, circulating supply and holder concentration are time-sensitive on-chain or market facts. They are not reported as fixed values in this edition.

## Allocation and governance disclosures

This edition does not specify a verified token allocation schedule, vesting plan, treasury-control policy or formal token-governance mechanism. Such matters require separate explicit disclosures and supporting records before they can be presented as established tokenomics.

The standard supply used for project launches should not be substituted for a verified allocation or circulating-supply statement about the official SPAWN token. Readers should distinguish a platform launch default from the particular history and state of an individual asset.

***

[Previous: 9. Fees and creator economics](/spawnmeme-docs/whitepaper/09-economics.md) · [Next: 11. Security, controls and limitations](/spawnmeme-docs/whitepaper/11-security.md)


---

# 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/10-spawn-token.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.