All launches
S

Sale Proof

$SLPRtemplate v1
Total supply1.0M SLPR
Websiten/a
Description hash0x4394db4c85d6b19941f46c797c9e5878c8d080eadb632cae3ce72913d1b670ec
Journey hash0x952031a05c598b1ac1c4ea7f22a48d0ed8dc7d65e09ad6a1a747126977cbdfc7
Salt0xfed81055c0ad1ada347b610ed8f107eeb5805a20306f1889a52445f76f3ff146
Launch feeFree
Block96231278
NetworkRobinhood Chain Testnet

Allocation sale

Zero platform cut

0.000001 ETH per SLPR

Ended
500 SLPR / 200.0K SLPR sold0.0005 ETH raised
WindowAug 2, 2026 → Aug 2, 2026
Per-wallet cap500 SLPR

Proceeds schedule

  • M1 Sale completes60%Claimed 0.0003 ETH
  • M2 Second proceeds tranche unlocks40%Claimable

Recent purchases

100% of proceeds go to the creator's milestone-locked schedule; the platform takes nothing. sale transaction

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 proves the allocation sale pipeline end to end: a fixed-price fee-free sale with a hard window and per-wallet cap, and proceeds locked in a milestone-dated schedule the creator cannot bypass.

Supply rationale

1,000,000 tokens; a 200,000 allocation sold at a fixed price, the rest held by the creator for later phases.

Roadmap

  1. 2026-08-16 Sale completes

    Allocation sold or window ends.

  2. 2026-09-30 Second proceeds tranche unlocks

    40% of the raise.

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