Back to explore
V

Vested Proof

$VPRFtemplate v1

About

Robinhood Chain Testnet

No verified description is on record for this token.

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

Supply

1.0M VPRF

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

Description hash0x736409c6f0196c7b75f3c2c88ee43e6ba6da68616fe5ce0a56cbf40c6ef16678
Journey hash0x4fc8244ba29240d78010775b3a1c85c3e1f923a589c05914b8b6ea4193cf6788
Salt0x5199300b47d91a6c537faec0d59e1b63210489fa95c58c73d7c0ee61ae76bc48
Launch feeFree
Block96210264
NetworkRobinhood Chain Testnet

Vesting

Read from chain
Released0 VPRF
Releasable now76.4K VPRF
Still locked123.6K VPRF
Vested amount200.0K VPRF
StartAug 2, 2026
Cliff endsSep 1, 2026
Fully vestedJan 29, 2027
Beneficiary (live owner)0x955fc594dd992Ef7bb7d175b6C9a68Be2b622DEB
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 vesting pipeline end to end: a fifth of the supply locked in an on-chain VestingWallet clone at launch, with the schedule committed in the VestingCreated event and surfaced by the indexer.

Supply rationale

1,000,000 tokens: 20% vests linearly over 180 days with a 30-day cliff; the remaining 80% goes to the creator at launch.

Roadmap

  1. 2026-08-31 Cliff passes

    First tokens become releasable.

  2. 2027-01-28 Fully vested

    Entire locked share released.

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.