CanHavCanHav Research
Log In
All tokens
J

Journey Proof

$JRNYtemplate v1
Token address0xc5a1540aef885444cfe110d851c5e456645ead56
Creator0x955fc594dd992ef7bb7d175b6c9a68be2b622deb
Total supply1.0M JRNY
Website—
Description hash0x08bd89e708d0b3bd4c84ebffa0074bf5fac4ab55b9b1d389cdb072c78bd4eb79
Journey hash0x1e7e079277eaa49bb1dd35a39a144297ae9e78dc27e0c93cd58a792caf665e97
Salt0x2d917f1eca9a73370d4276c56a148a62ba4aae11be6f2e21d2d6a61f3bc57ce0
Launch transaction0x279df02f192792bc29259057b29f583a7f41f5f13a3a818b68a4bb61c6c3dcdd
Block96204930
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.