> For the complete documentation index, see [llms.txt](https://docs.hatchr.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hatchr.fun/protocol/token-contract.md).

# Token Contract

Every Hatchr token is a deterministic minimal clone of the published `LaunchToken` implementation.

## Fixed properties

* ERC-20 with 18 decimals.
* Exactly 1 billion tokens per launch.
* Supply minted once during initialization.
* No external mint function after initialization.
* No token owner or token-admin role.
* No upgrade function.
* No transfer tax.
* No blacklist or whitelist.
* No pause switch.
* No maximum-wallet rule.
* Metadata URI has no setter.

## Initialization protection

The implementation disables its own initializer in its constructor. A clone can be initialized once and only by the immutable trusted `TokenInitializer`. That initializer accepts calls only from authorized factories.

```mermaid
sequenceDiagram
    participant F as Authorized Factory
    participant I as TokenInitializer
    participant T as Token Clone
    F->>I: initializeToken(...)
    I->>I: verify authorizedFactories[msg.sender]
    I->>T: initialize(...)
    T->>T: verify trusted initializer + one-time guard
    T->>F: mint fixed supply
```

This prevents arbitrary wallets from initializing a clone or selecting a mint recipient.

## Minimal clone model

The clone delegates token logic to a fixed implementation address embedded in its minimal bytecode. It is not a beacon proxy and has no admin-controlled implementation slot.

Changing the factory's implementation for future launches does not rewrite existing token clones.


---

# 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://docs.hatchr.fun/protocol/token-contract.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.