GARP
The curve completed 9s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.
findingIt left the curve 9s after launch.
noteOnly 11.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 04:44 UTC |
| Creator | JDQKDrc1TQgBRvdFh56tkta5sYcDj1SoP52Eiu64rSrT |
| Creator took | 15.3% of supply in the first block |
| Outside buyers | 120 distinct wallets, not counting the creator, bought on the bonding curve: 120 within the first 30s, 0 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | not while we watched |
| Recorded from | 4KwFChG3u2gZWVzUCLsEjT… slot 451,860,449
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 04:44:32 UTC Slot 451,860,449, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-09-30 04:44:41 UTC +9s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 04:44:41 UTC +9s
4.109e-7 SOL per token.
Decoded from an on-chain transaction that executed at that price.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
| Thirty seconds in | 120 distinct buyers, within the first thirty seconds. A snapshot taken off a tick at the thirty-second mark, so
it carries no moment of its own; it is placed here because that is where it happened. |
Times are receipt times: the moment we decoded the event, not the block's own timestamp. Events that arrived in one batch carry one timestamp, so ordering within a batch is not established, and a second or two here is our latency rather than the chain's.
Seen before
| This picture | On 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 110 launches from 58 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 748 earlier launches, 50 confirmed graduated on chain, 7 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 459 other creator wallets, across 621 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 11.0 SOL |
| Read from chain | 2026-10-01 20:07 UTC, just now |
What this launch claimed to be
| Name | GARP |
| Description | GARP |
| Metadata held | sha256 da207b45d2f092e4c57f20191f91276f1303190613610d26aea13b2d122484d9 · 345 bytes Read the document, the bytes themselves rather than our reading of them. The hash above is what the record commits to, so anyone can check the two agree. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-10-01 04:45 UTC. |
| Picture held | sha256 89ddeadb8bcfa10177922bfb72986aa79325e0baa46fda5bc7036f48094f633f · 123,361 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 04:44 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.