> 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/overview.md).

# Overview

**Available now** on Robinhood Chain Testnet and Arbitrum Sepolia.

Token Launch is CanHav's testnet launchpad. It runs on two chains from the same contracts: **Robinhood Chain Testnet** and **Arbitrum Sepolia**. The [studio](/studio/studio.md) (projects and token designs) is available alongside it. Agent / ERC-8004 is **not started**.

You create a fixed-supply ERC20 whose supply goes onto a [bonding curve](/token-launch/bonding-curve.md), and you can make your first buy inside the launch. You can also commit a plan on-chain as a hash, so it can be checked later. That commitment is optional. At 0.1 ETH raised the curve seeds a pool whose liquidity is locked forever. Supporting contracts cover milestone escrow, progress updates, allocation sales, and a minimal AMM.

CanHav has no affiliation with Robinhood. Robinhood Chain does not distribute to Robinhood brokerage customers. See [Welcome](/getting-started/welcome-to-canhav.md).

## Status

| Item       | Detail                                                                                                                                                                                                                                                                    |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Networks   | Robinhood Chain Testnet (chain ID `46630`) and Arbitrum Sepolia (chain ID `421614`). See [Network setup](/token-launch/network-setup.md).                                                                                                                                 |
| Launcher   | **CurveLauncher**, one per chain. Every launch from `/launch` goes through it. A TokenFactory is also deployed on each chain for launches made by script; on Robinhood Chain Testnet factory v4 is live and v1 to v3 are paused. Every token stays indexed and browsable. |
| Product UI | The **Launch** tab (`/launch`) and the **Explore** tab (`/explore`) on canhav.com.                                                                                                                                                                                        |
| Audience   | Builders and testers. Not a mainnet product.                                                                                                                                                                                                                              |

{% hint style="warning" %}
Testnet only. Tokens here have no value. Do not treat launches, fees, or liquidity as production or investment advice. Read [Risks](/token-launch/risks.md).
{% endhint %}

## What you can do

1. [Set up the network](/token-launch/network-setup.md) (wallet, testnet ETH), or follow the [Quickstart](/token-launch/quickstart.md)
2. Fill in [the launch form](/token-launch/launch-form.md) and launch. [Create a token](/token-launch/create-a-token.md) explains what the transaction deploys, and [Bonding curve](/token-launch/bonding-curve.md) explains the market it opens
3. [Buy and sell](/token-launch/trading.md) on the curve, then in the pool after graduation
4. Read [the token page](/token-launch/token-page.md) and browse [Explore](/token-launch/explore-tokens.md)
5. [Link the launch to a project](/token-launch/projects-and-launches.md) in the studio, and read it from an AI agent over [MCP](/ai-and-ide/export-and-mcp.md)
6. With a commitment, use [escrow](/token-launch/milestone-escrow.md), [updates](/token-launch/journey-updates.md) and [sales](/token-launch/allocation-sales.md) against your milestones
7. Review [contract guarantees](/token-launch/contract-guarantees.md), [fees and economics](/token-launch/fees-and-economics.md), [governance](/token-launch/governance.md), and [contract addresses](/token-launch/contract-addresses.md)

## Design principles

* **Pause on the launcher and factory, not on tokens.** Stopping new launches does not freeze existing tokens, and sells on a curve always work.
* **Liquidity locked by construction.** A graduated pool's shares sit in a contract with no way to remove them.
* **Hashes for credibility.** The description, and the commitment when there is one, are recorded as hashes in the launch event.
* **Admin-less where it matters.** Escrow, updates, and sales have no owner.
* **Timelock for admin knobs.** Launcher, factory and AMM fee and config changes wait out a public delay. Each chain has its own timelock.
* **Zero supply take.** No mint path for the platform after initialize.

## Next

Start with the [Quickstart](/token-launch/quickstart.md) or [Network setup](/token-launch/network-setup.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/overview.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.
