Escrow Proof
Milestone escrow
No admin: time-locked on-chain- M1 Escrow visible on the token page2026-08-09100.0K ESCPClaimed
- M2 Second tranche unlocks2026-09-3050.0K ESCPClaimable
Locked by 0x955f…2deb · escrow transaction
Unlocked tranches can be claimed by anyone; tokens always go to the creator.
Journey
Hash verified against chainWhy this token
This token proves the milestone escrow pipeline end to end: supply locked in the admin-less escrow singleton against journey milestones, a progress update anchored on-chain, and a tranche claimed after its unlock passes.
Supply rationale
1,000,000 tokens; part locked in the milestone escrow to demonstrate the commitment device, the rest stays with the creator.
Roadmap
2026-08-09 Escrow visible on the token page
Tranches render with milestone titles.
Escrow is live on the token page — this update was posted by the e2e script and its hash is anchored on-chain.
Creator update · Aug 2, 2026 · hash anchored on-chain
2026-09-30 Second tranche unlocks
Claimable after the date passes.
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.
curl -fsSL https://claude.ai/install.sh | bash
claude mcp add --transport http canhav https://www.canhav.com/mcp
Use the canhav get_launch tool for 0xe772ace5d705a8ef85b546c9bfcab8361426af8f 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.