Picomatch
The curve completed 2s 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 2s after launch.
At launch
| Created | 2026-09-30 22:53 UTC |
| Creator | JEGDru5rB6Cz1e56XqE4jKhvEQoMBCffx3svgjWZe3i3 |
| Creator took | 3.0% of supply in the first block |
| Outside buyers | 47 distinct wallets, not counting the creator, bought on the bonding curve: 47 within the first 30s, 11 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 | 36KH9QsFoBnUSJgvsXRFQ9… slot 452,104,608
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 22:53:32 UTC Slot 452,104,608, which is the chain's own clock for this moment. |
| Creation block | 11 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-30 22:53:34 UTC +2s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 47 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. |
| Highest price seen | 2026-10-01 00:01:38 UTC +1h 08m 06s
0.000e+0 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 11 launches from 11 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 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 | 81.2 SOL |
| Read from chain | 2026-10-01 03:12 UTC, just now |
What this launch claimed to be
| Name | Picomatch |
| Description | Jon Schlinkert created Picomatch which gets half a billion downloads weekly. His work has accounted for roughly 7% of total monthly downloads across the entire Node.js ecosystem. He has never been paid for these programs and gets no funding. All token fees sent to his GitHub to support his work. |
| Metadata held | sha256 ba0c03ab38f6b1e5513d717d99594029a8ed46d84044beec65e3e247b136a1bf · 616 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. |
| Picture held | sha256 6b1b303ae22aa9e115d1f69661318b199153df2491ac17accae4a866cbf50e94 · 40,134 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 22:53 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.