GOIF
The curve completed in the same batch of events as the 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.
findingOnly 4 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
At launch
| Created | 2026-10-01 03:01 UTC |
| Creator | HGyshHSNM65qQwibaRt8wvAwEU6TkQzBGBsxVJJdYC5m |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 4 distinct wallets, not counting the creator, bought on the bonding curve: 4 within the first 30s, 4 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 6.4 h ago and it was finished. Checked 2026-10-01 03:31 UTC. |
| Creator sold | not while we watched |
| Recorded from | 54PnpskNScg5m5Xh3Cr64p… slot 452,160,200
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-01 03:01:43 UTC Slot 452,160,200, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-01 03:01:43 UTC +0s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-10-01 03:01:43 UTC +0s
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 | 4 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 13 launches from 13 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 21 launches from 20 creator wallets, including this one. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 4 other creator wallets, 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 | 4753.0 SOL |
| Read from chain | 2026-10-01 09:56 UTC, just now |
What this launch claimed to be
| Name | GOIF |
| Description | GOIF (GOIF) |
| Metadata held | sha256 f34c632e231c46e982d0add6fce19a31d6ced650c41b44b621f221f411fff4e1 · 326 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 6f658777cc60f0100ea1b38c32370fdf6366269edd965d5e3e21a61d7680692f · 245,989 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 03:01 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.