> 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.

Token Launch is CanHav's testnet launchpad on **Robinhood Chain Testnet**. [Projects](/getting-started/two-tracks.md) (ideation and design deploy) is available now alongside it. Agent / ERC-8004 is **not started**.

You create a fixed-supply ERC20 from a factory, optionally attach vesting in the same transaction, and commit a journey hash on-chain so the plan can be checked later. Supporting contracts cover milestone escrow, progress updates, allocation sales, and a minimal AMM. You can quick-deploy or deploy from a published token design.

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                                                                                   |
| ---------- | ---------------------------------------------------------------------------------------- |
| Network    | Robinhood Chain Testnet (chain ID `46630`)                                               |
| Factory    | TokenFactory **v4** (live). v1-v3 are paused; their tokens remain indexed and browsable. |
| Product UI | Hidden URL track on the product site: `/launch`                                          |
| Audience   | Builders and testers. Not a mainnet product.                                             |

{% hint style="warning" %}
Testnet only. Do not treat launches, fees, or liquidity as production or investment advice.
{% endhint %}

## What you can do

1. [Set up the network](/token-launch/network-setup.md) (RPC, faucet, wallet)
2. [Create a token](/token-launch/create-a-token.md) with metadata and journey, or use [Deploy paths](/token-launch/deploy-paths.md) for design deploy
3. Use [vesting](/token-launch/vesting.md), [escrow](/token-launch/milestone-escrow.md), [updates](/token-launch/journey-updates.md), [sales](/token-launch/allocation-sales.md), and [AMM](/token-launch/amm-and-fees.md)
4. [Explore](/token-launch/explore-tokens.md) indexed launches and open a token detail page
5. 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 factory, not on tokens.** Stopping new launches does not freeze existing tokens.
* **Hashes for credibility.** Journey and description are committed as hashes in launch events.
* **Admin-less where it matters.** Escrow, updates, and sales have no owner.
* **Timelock for admin knobs.** Factory and AMM fee/config changes wait out a public delay.
* **Zero supply take.** No mint path for the platform after initialize.

## Next

Start with [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 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.canhav.com/token-launch/overview.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.