Example project. Figures, activity and addresses are illustrative.
01
0.30 SOL
Paid02
8.00 SOL
deployed · Builder03
100% of creator fees and Recovery Tranche sales go to the Launch Reserve until the threshold is reached. No deadline, nothing owed by the builder. 9 days to the Day-31 review.
04
05
Founder allocation
14%
of initial supply
Cliff
30 days
0% unlocked during cliff
Unlock cap
1.5%
per rolling 30 days
Next unlock
Sep 30, 2026
0.00% unlocked so far
Day 22 of 330. Unlocked so far 0.00% of initial supply, capped at 1.5% per rolling 30 days over 10 monthly periods.
06
1.50%
Vesting delivery07
5HgTk2Wq8Ln4Zc7Xv1Nb9Md3Jy6Sf0Pe2Au5KrQdpster ExplorerEvery realize Verified Launch is minted with a branded on-chain identity: a contract address ending in pster. The vanity keypair was generated in realize infrastructure, used once for creation and destroyed.
Verify on explorer08
09
Merchant SDK 1.0
Sep 20, 2026Checkout SDK published to npm with webhooks.
First 50 merchants
Sep 12, 2026Pilot cohort onboarded in Lisbon and Berlin.
Settlement engine
Sep 5, 2026Sub-second settlement to merchant wallets.
Builder: Gridpay @gridpay
10
Day-31 position policy
For the first 31 days realize holds its Support Position and does not sell, except in a Security Exit. From Day 31, if the token is a zombie, realize may sell its own Support Position, gradually and under the public caps below. Founder-locked tokens are never sold.
A token is a zombie when it fails the published Day-31 criteria with no meaningful progress: no builder updates, no meaningful trading volume or creator-fee activity, and no evidence of active building. This token is on day 22 of 31.
Evaluation criteria (defined before launch)
Public selling rules
11
0.21 SOL creator fees routed to the Launch Reserve
1hFounder Purchase settled: 1.50% of supply, 4.31 SOL paid
21d8.00 SOL Launch Support deployed inside the launch
21dHolder checklist