> For the complete documentation index, see [llms.txt](https://docs.peach.ag/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/token-information.md).

# Token Information

Each Pro launch creates an 18-decimal, burnable ERC20 token and its own Curve. The full initial supply is minted once to the Curve. Read `Curve.initialSupply()` for the original amount and `Token.totalSupply()` for the current amount after burns.

Use the Pro Factory's `getLaunchedToken(token)` and `curveFor(token)` to find the launch's registered contracts and Quote asset.

### Who controls what?

| Role                                  | Purpose                                                       |
| ------------------------------------- | ------------------------------------------------------------- |
| Original Creator / `Token.deployer()` | Immutable creation identity                                   |
| `Factory.creatorController(token)`    | Controls metadata and Creator Fee Recipient changes           |
| Creator Fee Recipient                 | Address credited when Creator fees are settled into FeeEscrow |
| Distribution authority, when enabled  | Controls the selected revenue composition under its own rules |

The current Controller calls `Factory.proposeCreatorController(token, candidate)`. The candidate accepts with `Factory.acceptCreatorController(token)`; until then, the old Controller remains active. The current Controller may cancel the proposal.

This transfer does not change the fee Recipient, move balances or transfer Distribution authority. See [Revenue Distribution](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/revenue-distribution) for its management roles.

### Metadata

The current Controller can call `Token.updateMetadata(logo, description, socials)` while `metadataUpdateAllowed()` is true. Socials contains twitter, telegram, discord, website and farcaster. Name and symbol are immutable.

Limits are UTF-8 bytes: name 64, symbol 16, logo 512, description 2,048 and each social 256. Name and symbol must be nonempty. On `MetadataUpdated`, re-read the fields and `tokenInfoHash()` for the latest content.

### Recipient changes and permanent locks

While Recipient changes are enabled, the Controller can call `Factory.transferCreatorFeeRecipient(token, newRecipient)`. The new address receives subsequent fee settlements, including still-pending fees. Already credited ordinary Escrow balances stay with the old address. Factory Owner also has a three-day delayed override followed by a three-day execution window.

The Controller can permanently surrender either permission:

* `Factory.renounceRecipientUpdates(token)` disables Recipient changes, including Owner overrides, and cancels any pending override.
* `Token.renounceMetadataUpdates()` disables metadata updates.

The two locks are independent and cannot be restored by transferring control. A locked core Recipient does not freeze a Distributor's shares or authority. Continue with [Token Creation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/token-creation) and [Fees and Claims](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/fees-and-claims).

### Pool protection

`protectionDuration()` reports the Creator-selected duration in seconds. Read `restrictedPools()` and `isTransferRestricted(address)` for the actual transfer policy. Duration alone does not prove that any destination is restricted; the list may be empty.


---

# 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://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/token-information.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.
