All launches
I

Indexer Proof

$IDXtemplate v1x.com/canhav
Total supply500.0K IDX
Description hash0xd0ceabb05fee515ab3631f83e19e3bb541e1a45f86d5c911d446884be02aab90
Journey hash0x7adc366aaeeaf9471399af2768ace1b6d41dab9527854cd0de2c3ecc2fad8ff7
Salt0x07aebf545dc3d2ccd06434b91e7ab4d9074579114441dead6970a0ba20322b51
Block95611866
NetworkRobinhood Chain Testnet

Escrow actions

No design record. The committed hash 0x7adc366aaeeaf9471399af2768ace1b6d41dab9527854cd0de2c3ecc2fad8ff7 resolves to neither a journey document nor a published token design on this site.

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