1,298,396 launches on record
Coverage from 2 Sep 2026
Archive read 18:03 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

BOT GO

No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.

Also recorded, and not part of the finding above: this picture is on 2 other launches from 3 creator wallets in all, and this creator has 474 other launches on record. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 44.7% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

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.

8aursyKkbyqL7T6cWKsosG8ES1oBGVfS8sJ4UmPApoT3 Solscan pump.fun

At launch

Created2026-10-03 07:59 UTC
CreatorCALQ1EwjARtaW6FW6KQDZj4jhye9Vt4NvTzFwmg4JHqC
Creator took13.6% of supply in the first block
Outside buyers875 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 21 within the first 30s, 4 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduatednot while we were watching
Curve on chainNothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them.
Creator soldnot while we watched
Recorded from3VqYWkVxunKXJ7rKrbzEkJ… slot 452,873,054
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Order of events

Created2026-10-03 07:59:36 UTC
Slot 452,873,054, which is the chain's own clock for this moment.
Creation block4 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in21 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 seen2026-10-03 08:31:38 UTC +32m 02s
2.897e-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 pictureOn 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 14 launches from 7 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. See this ticker's page →
This documentThe same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. See them →
This creator474 earlier launches, 7 confirmed complete on chain. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 293 other creator wallets, across 435 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. 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

The picture this launch published at birth
NameBOT GO
Descriptionhttps://bot-de-go-beta.serio-ai.chatgpt.site/ Grokbot icon 스타일을 이용한 새 오픈소스 프로젝트를 하나 공개해 봅니다. 올려주신 아이콘 중 인상깊었던 열차 및 대중교통 봇 아이콘들 중 일본 철도 관련한 것들만 모아서 실제 노선에 대응하는 Grokbot icon + 철도교통 노선지도 입니다. 철도 자료는 일본 국토교통성, 지도는 일본 국토지리원 지도 Api를 사용했습니다. 둘 다 비상업 이용 허가라, 사이트로 비상업적 오픈소스로 운영됩니다. 아이콘을 만들고, 업로드하고, 노선에 대응시킨 뒤 노선 위에서 가상의 운행을 해 보실 수 있습니다. 현재 운행되고 있는 노선에 최대한 대응하려 했고 여러번의 자료 검수를 통해 최대한 오류를 잡아내려 노력했습니다만, 이번은 자료가 많아 오류가 꽤 있을 거 같습니다. 제가 철도를 잘 모르기도 하구요. 더 수정과 수정을 하려다가 또 저장소에 잠자는 프로젝트가 될 거 같아 여기서 한번 1차 공개하고
Metadata heldsha256 b849d694db2e5c2c347ec81f5489035ba53b1b4d5837d4d21e49615f3d672de7 · 1,627 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 heldsha256 829d7f8b5c4358c9aa8bacbf760eed173469c26e5855cba4b5ab3882570045c9 · 13,168 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-10-03 07:59 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.

Check another