BIDDY
The creator took 50% of supply at 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.
noteThe creator took 49.8% of supply at launch.
noteThe creator sold while we were watching.
At launch
| Created | 2026-09-18 23:59 UTC |
| Creator | A1mVoRdCVTZpfvVzYWD2MBwjzmiFe8RUdBfWX5Yb2A4e |
| Creator took | 49.8% of supply in the first block |
| Outside buyers | 670 distinct wallets, not counting the creator, bought on the bonding curve: 164 within the first 30s, 11 bundled into the creation block. |
| Graduated | 31 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 | yes |
| Recorded from | 3hPhM4HCm5Lofz5BqWTz3a… slot 448,238,732
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-18 23:59:17 UTC Slot 448,238,732, 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. |
| Thirty seconds in | 164 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-19 00:30:41 UTC +31m 24s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-19 00:30:41 UTC +31m 24s
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 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 53 launches from 40 creator wallets, including this one. See them → |
| This document | Byte-identical to 3 other launches' metadata document. See them → |
| This creator | 7 earlier launches, 4 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 12 other creator wallets, across 14 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 | 223.0 SOL |
| Read from chain | 2026-09-19 04:55 UTC, just now |
What this launch claimed to be
| Name | Getbiddy.fun |
| Metadata held | sha256 86dbabcebf4123ccc22be1690c36048ad827f652ca9429f501d07922366ccddc · 349 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 033db0feda01a83c2256b2f7659b90253eab84857636f8aef59dcd1c72344b1b · 4,722 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-18 23:59 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.