All launches
J

Journey Proof

$JRNYtemplate v1
Total supply1.0M JRNY
Websiten/a
Description hash0x08bd89e708d0b3bd4c84ebffa0074bf5fac4ab55b9b1d389cdb072c78bd4eb79
Journey hash0x1e7e079277eaa49bb1dd35a39a144297ae9e78dc27e0c93cd58a792caf665e97
Salt0x804976cb1e5f18cbe8e898529d3538d5af6c0b2f5c97e1a853b6fe53d3a96cd5
Launch fee0.0002 ETH
Block96245718
NetworkRobinhood Chain Testnet

Escrow actions

Quick deploy, no design record. This token was launched with a journey document only; there is no published token design behind it.

Journey

Hash verified against chain

Why this token

This token exists purely to prove the launchpad's journey pipeline end to end: a document written before launch, hashed, committed on-chain in the TokenLaunched event, and verified afterwards against the stored copy.

Supply rationale

Exactly 1,000,000 tokens, all minted to the creator at launch — a test supply with no distribution story.

Roadmap

  1. 2026-08-07 Indexer shows this token

    Visible on /launch/explore within a block or two.

  2. 2026-08-14 Journey verified on the token page

    Hash recomputed server-side matches the event.

Read this launch from your agent

Every CanHav launch is readable over MCP. Connect once and ask your agent about the token, its commitment, sales and pools.

Install Claude Code
curl -fsSL https://claude.ai/install.sh | bash
Add the CanHav server
claude mcp add --transport http canhav https://www.canhav.com/mcp
Ask about this launch
Use the canhav get_launch tool for 0x4bc75f2a8b6ea48c2392200dc46f35f5d4446985 and summarize the commitment and its milestones.

The Claude desktop app can add the same server URL as a custom connector. Every tool in the docs →

Token fields are read from the on-chain TokenLaunched event via the indexer. The journey document is stored off-chain; its keccak256 hash is recomputed on every page load and compared to the hash in the event.