ClosedAI
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 01:41 UTC |
| Creator | EYqc8oiHabq23hA3XEBMNtqj5j7vfS1jJwKHB4Gfzq4W |
| Creator took | 79.3% of supply in the first block |
| Outside buyers | 0 distinct wallets, not counting the creator, bought on the bonding curve: 0 within the first 30s, 0 bundled into the creation block. |
| Graduated | 9 min after launch |
| Curve, read on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | not while we watched |
| Recorded from | 2P5VvVxqPzCLn4ZsaKGuLG… slot 452,465,051
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 01:41:34 UTC Slot 452,465,051, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | No buyer, 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-10-02 01:50:32 UTC +8m 58s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 01:50:32 UTC +8m 58s
0.000e+0 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 4 launches from 4 creator wallets, including this one. See them → |
Who took the curve
One transaction bought 85 SOL of this curve, in the same batch of events as the launch, from the creator's own wallet. The wallet and the transaction →
That is the same transaction the token was created in: the launch and the purchase of its float are one signature.
Our launch and trade timestamps are both taken when the events are decoded, so events that arrived together carry the same one. That it was taken at or near launch is on the record; how many seconds after is not.
Pool
| Liquidity | 0.3 SOL |
| Read from chain | 2026-10-02 06:59 UTC, just now |
What this launch claimed to be
| Name | Elon told Sam change their name |
| Description | Change your name to ClosedAI and I will drop the lawsuit |
| Metadata held | sha256 2dad7e2888cb491f5de574405b046559681211f2a2fa9ae8deff0f365b949689 · 455 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 8c3030cf1ece933878c6c4655e38224fe45b74f6989a8832f2f0d24b03b22f80 · 1,931 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 01:41 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.