$HONK
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.
At launch
| Created | 2026-10-02 02:34 UTC |
| Creator | HuHT85T7pUDyADEkRwLJWBRooi3hc81bXixpkoSFdTEt |
| Creator took | 0.9% of supply in the first block |
| Outside buyers | 21 distinct wallets, not counting the creator, bought on the bonding curve: 5 within the first 30s, 1 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 6.2 h ago and it was finished. Checked 2026-10-02 03:01 UTC. |
| Creator sold | not while we watched |
| Recorded from | 3quEuXZ8X7ei397fDeQYgc… slot 452,476,764
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 02:34:00 UTC Slot 452,476,764, which is the chain's own clock for this moment. |
| Creation block | 1 wallet bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-02 02:34:09 UTC +9s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-10-02 02:34:13 UTC +12s
1.561e-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 | 5 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 | No other launch we hold a picture for used this one. |
| This ticker | On 6 launches from 5 creator wallets, including this one. See them → |
| This creator | 267 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 2 other creator wallets, across 6 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
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | Aggressive Goose Protocol |
| Description | Peace was never an option. Wanders around stealing car keys, chasing toddlers, and screaming directly into the smart contract. |
| Metadata held | sha256 52e9a1a1a9658e94432dca4679129928c1dc872cb27292cc556fa3341d65213d · 438 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 63cba92acc3ad976b8d7f2d844ab783857cca610ab40a89fead190edab312263 · 284,119 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 02:34 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.