CanHavCanHav Research
Log In
All tokens
J

Journey Proof

$JRNYtemplate v1
Token address0x6c3b058b0c73c0d618dc94c7daf38c18d4da58a1
Creator0x955fc594dd992ef7bb7d175b6c9a68be2b622deb
Total supply1.0M JRNY
Website—
Description hash0x08bd89e708d0b3bd4c84ebffa0074bf5fac4ab55b9b1d389cdb072c78bd4eb79
Journey hash0x1e7e079277eaa49bb1dd35a39a144297ae9e78dc27e0c93cd58a792caf665e97
Salt0x56cc01dd0e755c73b74fc8e1b50cf5e24aa9490517fd291a91647090da5b9ef2
Launch transaction0x24de01b20a6075aff851790d4d77a87d2d19c2db520370eaf78d5b4e83f32534
Block95621000
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.

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.