> 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/glossary.md). # Glossary **Available now** as reference. Terms for Token Launch, Projects, and Agent Launch match how CanHav uses them in product and contracts. ## Product | Term | Meaning | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | CanHav | Research platform and testnet product suite. Product site: [canhav.com](https://canhav.com). | | Token Launch | Testnet launchpad on Robinhood Chain Testnet for creating fixed-supply tokens with optional vesting, journeys, sales, and AMM liquidity. Available now. | | Projects | Ideation studio with independent Product and Token design tracks, computed outputs, and public pages. Available now. | | Agent Launch | Intended ERC-8004 agent identity track. **Not started.** | | Journey | Off-chain document describing a token's plan and milestones. Its hash is committed on-chain at launch. | | Research preview | Content and software that is experimental, testnet-only, and not financial advice. | | Status declaration | Team-stated status for legal, governance, or security work (already in place, handled by legal/ops, planned before mainnet, not yet). Not enforced by the token contract. | ## Projects | Term | Meaning | | ---------------- | --------------------------------------------------------------------------------------- | | Product track | Ideation document for what you are building (sector, users, architecture, security). | | Token track | Ideation document for token design (eight sections from rationale through post-launch). | | Computed outputs | Float, FDV:float, unlock calendar, and warnings derived from token design answers. | | Clerk | Intended account provider for studio (in development). | ## Token Launch | Term | Meaning | | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | Robinhood Chain Testnet | Arbitrum Orbit testnet used by CanHav Token Launch. Chain ID `46630`. Not affiliated with Robinhood brokerage distribution. | | TokenFactory | Contract that deploys token clones (CREATE2 / LibClone). Current live factory is v4. Older factories are paused; their tokens remain indexed. | | LaunchToken | Fixed-supply ERC20 implementation cloned per launch. No mint after initialize; no owner; not upgradeable. | | Launch fee | ETH paid to the factory on launch. Hard-capped in bytecode (`MAX_LAUNCH_FEE`); current documented testnet value 0.0002 ETH. | | userSalt | Creator-chosen salt. Combined with `msg.sender` so predicted addresses cannot be front-run by others. | | journeyHash | On-chain commitment to the full journey document. | | descriptionHash | On-chain commitment to the short form description field. | | Vesting wallet | Clone that locks a percent of supply for a beneficiary with duration and optional cliff. | | MilestoneEscrow | Admin-less singleton for milestone-dated token lockups. | | JourneyUpdates | Admin-less singleton that anchors content-addressed progress updates. | | AllocationSale | Admin-less fixed-price sale contract. Fee-free; proceeds unlock on milestone dates. | | LaunchAMM | Minimal token/ETH AMM. LP fee plus optional protocol fee routed through FeeSplitter. Per-pool protocol fee frozen at creation. | | FeeSplitter | Timelock-owned destination for platform fee share; permissionless distributions to configured payees. | | TimelockController | Owns factory and AMM admin knobs. Admin changes wait out a public delay (300s on testnet). | | Indexer | Ponder app that indexes launch events for explore and token detail pages. | ## Agent Launch | Term | Meaning | | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | Base Sepolia | Base L2 testnet. Chain ID `84532`. Home of CanHav Agent Launch. | | ERC-8004 | Standard for on-chain agent identity and related registries. | | Identity Registry | Public ERC-721 registry where each agent is a token. CanHav does not own this contract. | | Reputation Registry | Related ERC-8004 registry. Used for wiring checks; full reputation flows are out of scope for v1. | | Vanity prefix | Testnet Identity Registry addresses start with `0x8004A818`. Mainnet starts with `0x8004A169`. Mixing them up fails silently unless checked. | | MCP (Agent Launch) | Model Context Protocol as intended agent capability endpoint for registration gating. | | MCP (Projects / AI) | CanHav MCP server for reading design documents in an IDE (in development). Separate from Agent Launch MCP notes. | | Registration file / URI | Metadata URI attached to an agent identity (URL or inline `data:` URI). | | Agents indexer | Separate Ponder app for ERC-8004 events (not shared with the launchpad indexer). | --- # 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/getting-started/glossary.md?ask=&goal= ``` `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.