> 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/getting-started/welcome-to-canhav.md). # Welcome to CanHav **Available now** for Token Launch, Projects, accounts and AI/IDE export, all on testnet. **Deferred** for a Foundry scaffold generator. **Not started** for Agent / ERC-8004. CanHav is a research-led platform for EVM builders and capital-markets practitioners. The product site at [canhav.com](https://canhav.com) focuses on DeFi ecosystem solutions. These docs cover the testnet products that ship alongside that research. ## Important: Robinhood CanHav has **no affiliation** with Robinhood Markets, Inc. or its affiliates. Robinhood Chain does **not** provide distribution to Robinhood brokerage customers. Deploying a token or app on Robinhood Chain or its testnet puts your work in front of nobody by default. Listing on CanHav is not a channel to Robinhood users either. ## What you will find here | Section | What it covers | Status | | ---------------------------------------------------------------- | -------------------------------------------------------------------------- | ------------- | | [What CanHav is](/getting-started/what-canhav-is.md) | What CanHav is (and is not) | Available now | | [The two ideation tracks](/getting-started/two-tracks.md) | Product and Token tracks, linking | Available now | | [The three answer types](/getting-started/three-answer-types.md) | Decisions, computed outputs, status declarations | Available now | | [Product track](/product-track/product-track.md) | Sector, users and payers, architecture, security decls | Available now | | [Token track](/token-track-ideation/token-track.md) | Eight design sections, computed outputs, warnings | Available now | | [Public pages](/public-pages/public-pages.md) | Separate `/p` and `/t` pages, scoped signals | Available now | | [Token Launch](/token-launch/overview.md) | Launch and trade tokens on Robinhood Chain Testnet and Arbitrum Sepolia | Available now | | [Quickstart](/token-launch/quickstart.md) | From wallet to a live token in five steps | Available now | | [Deploy paths](/token-launch/deploy-paths.md) | Quick deploy vs design deploy | Available now | | [Studio](/studio/studio.md) | Your launches, projects and token designs in one place | Available now | | [Fees and guarantees](/token-launch/fees-and-economics.md) | Fee switches, caps, timelock, contract guarantees | Available now | | [Accounts](/accounts/clerk-accounts.md) | Clerk-based accounts | Available now | | [AI and IDE](/ai-and-ide/export-and-mcp.md) | Markdown export, AGENTS.md, MCP servers for designs, launches and projects | Available now | | [Agent Launch](/agent-launch-not-started/overview.md) | ERC-8004 on Base Sepolia | Not started | ## Product surfaces (today) 1. **Token Launch** on Robinhood Chain Testnet (chain ID `46630`) and Arbitrum Sepolia (chain ID `421614`). Bonding curve launches, trading, optional on-chain commitments, escrow, sales, AMM, hosted indexers, explore. 2. **Projects** (Product and Token ideation tracks, studio, public pages, design deploy). Available now on testnet. **Deferred:** Foundry scaffold generator (not a product feature yet). **Not started:** Agent / ERC-8004 track. Existing pages in that section are retained for history only and are marked Not started. All product surfaces described here are **testnet only**. Nothing here is financial advice, and nothing here is a mainnet product yet. ## Site appearance The app itself is dark by default and has a light theme on an off white canvas. The sun or moon button in the navigation switches between them; the choice is remembered in your browser, and a first visit follows your system setting. The docs site should use a **light** theme with a white background. That is a GitBook Customization setting, not a content-file change. You (or anyone with GitBook access) must apply it: dashboard → Customization → theme **Clean** → default mode **Light** → Publish. Full steps: [SETUP.md](https://github.com/wazarat/canhav.dev/tree/main/docs/SETUP.md). ## Who this is for * Protocol engineers and founders launching on testnets * Teams that want on-chain commitments (journey hashes, milestone lockups) instead of opaque off-chain claims * Teams designing a product, a token, or both before they deploy ## Where to go next * New here: [What CanHav is](/getting-started/what-canhav-is.md), then the [litepaper](/getting-started/litepaper.md). * Product design: [Product track](/product-track/product-track.md). * Token design: [Token track](/token-track-ideation/token-track.md). * Ready to launch: [Quickstart](/token-launch/quickstart.md), then the [Token Launch overview](/token-launch/overview.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/getting-started/welcome-to-canhav.md?ask=&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.