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

# Governance

**Available now.**

Token Launch separates **immutable after launch** from **timelocked admin**. Each chain has its own deployment and its own timelock. Nothing on one chain governs the other.

## TimelockController

| Item               | Detail                                                                                                        |
| ------------------ | ------------------------------------------------------------------------------------------------------------- |
| Address            | One per chain. See [Contract addresses](/token-launch/contract-addresses.md)                                  |
| Owns               | On its own chain: the CurveLauncher, the TokenFactory, LaunchAMM admin surfaces, and FeeSplitter payee config |
| minDelay (testnet) | 300 seconds on both chains. Anything closer to production should use 24h+.                                    |
| Proposer           | Deployer EOA (testnet), the same address on both chains                                                       |
| Executor           | Open                                                                                                          |
| Admin              | None on the timelock itself                                                                                   |

Every sensitive admin change (launch fee, treasury, pauser, implementation bumps, unpause) waits out the public delay.

## What can change, and what cannot

| Item                                                                  | Can it change?                                                                               |
| --------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| Launch fee                                                            | Yes, through the timelock, up to the hard cap `MAX_LAUNCH_FEE = 0.05 ether`                  |
| Default protocol fee for new opted-in pools                           | Yes, through the timelock, up to 50 bps. Existing pools keep the rate they were created with |
| Curve threshold, curve share, snipe window and tax, developer buy cap | No. Immutables of the launcher                                                               |
| A launched token (supply, name, ticker)                               | No. The token has no owner                                                                   |
| A graduated pool's liquidity                                          | No. It cannot be withdrawn                                                                   |

## What pause does

* **Launcher pause** stops new launches and curve **buys**. Curve **sells** can never be paused.
* **Factory pause** stops new factory launches.
* Already launched tokens are not paused by either. The token has no pause.
* **Pausing is immediate.** A pauser address (the deployer on testnet) can pause without waiting. **Unpausing** goes through the timelock and waits out the delay.
* On Robinhood Chain Testnet the older factories (v1 to v3) are paused permanently after migrations; their tokens stay live and indexed.

## Reading the governance page

The site shows all of this live at `/launch/governance`, with a toggle for each chain:

| Section             | What it shows                                                                                                  |
| ------------------- | -------------------------------------------------------------------------------------------------------------- |
| Economic terms      | Everything the platform charges, with the current value read from the chain, the ceiling, and what enforces it |
| Trading (AMM)       | The pool fee terms                                                                                             |
| Timelock operations | Every admin action, past and pending, from the timelock's event log, decoded                                   |

An agent can read the same through the `get_launch_governance` MCP tool, which takes an optional `chain`. See [Markdown export and MCP](/ai-and-ide/export-and-mcp.md).

## Related

* [Fees and economics](/token-launch/fees-and-economics.md)
* [AMM and fees](/token-launch/amm-and-fees.md)
* [Contract guarantees](/token-launch/contract-guarantees.md)
* [Contract addresses](/token-launch/contract-addresses.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://docs.canhav.com/token-launch/governance.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.