CanHav
Log in
Back to explore
J

Journey Proof

$JRNYtemplate v1

About

Robinhood Chain Testnet

No verified description is on record for this token.

Creator 0x955f…2deb · launched Aug 2, 2026

Supply

1.0M JRNY

Fixed at launch

Explorer

Project and commitment

Project

No project is linked to this token.

Commitment

2 milestones committed on chain.

Read the commitment →

Fees

Trade fee
0.30% of each swap, kept in the pool

These contracts have no creator trading fee and no fee sharing with holders.

Trade

This token has no bonding curve and no pool with liquidity, so there is nothing to trade against yet.

Price

n/a

Market cap

n/a

Liquidity

n/a

Market

No market yet

No trades yet, so there is no price history to chart.

Recent trades

0

No trades yet.

On-chain record

Token address0x4bc75f2a8b6ea48c2392200dc46f35f5d4446985
Creator0x955fc594dd992ef7bb7d175b6c9a68be2b622deb
Description hash0x08bd89e708d0b3bd4c84ebffa0074bf5fac4ab55b9b1d389cdb072c78bd4eb79
Journey hash0x1e7e079277eaa49bb1dd35a39a144297ae9e78dc27e0c93cd58a792caf665e97
Salt0x804976cb1e5f18cbe8e898529d3538d5af6c0b2f5c97e1a853b6fe53d3a96cd5
Launch fee0.0002 ETH
Launch transaction0x6897bcdd6350512f5f2483d3d88761800eed21529aa56a5a794e35305193e16f
Block96245718
NetworkRobinhood Chain Testnet
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 description text and the committed document, a journey or a design snapshot, are stored off-chain; each keccak256 hash is recomputed on every page load and compared to the hash in the event. The Telegram link is stored with the description and is not committed on-chain.