BOUNTY
Checked, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record; none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.
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.
noteOnly 3.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-27 19:20 UTC |
| Creator | 68B42Y7RnVhTjR9Y47sZJKkBnwPPR77eLUNsgFWzRpE3 |
| Creator took | 1.9% of supply in the first block |
| Outside buyers | 779 distinct wallets, not counting the creator, bought on the bonding curve: 157 within the first 30s, 3 bundled into the creation block. |
| Graduated | 6 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 | 4NRCS3wPLPLbSr3HicYYak… slot 451,089,148
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-27 19:20:31 UTC Slot 451,089,148, which is the chain's own clock for this moment. |
| Creation block | 3 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 157 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. |
| Curve completed | 2026-09-27 19:26:19 UTC +5m 48s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-27 19:26:19 UTC +5m 48s
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. |
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 29 launches from 29 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 123 launches from 88 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
Pool
| Liquidity | 3.0 SOL |
| Read from chain | 2026-09-27 23:09 UTC, just now |
What this launch claimed to be
| Name | Bounty |
| Description | hackathons fueled by trading fees — no sponsors needed, just pure on-chain prize pools where devs farm bounties and token holders watch the magic happen, because every L1 and AI lab knows the real move is letting builders build. |
| Metadata held | sha256 7c76cb64a37af73e22d090ead17d7b1dde9c59a60f100114a58acc2cb97dc529 · 492 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 b3fb41a1837e0c6bf69a69de91993d518a555c599b69ce9bbf16487c19f64b83 · 2,951 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-27 19:20 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.