Launch record · observed at creation 2026-11-07 21:10 UTC
THEFATCAT
FATCAT
Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.
At launch
| Created | 2026-11-07 21:10 UTC |
| Creator | AAddkhZggU1LfdWDtjB8mWwus9Sxye9Uv3B4K76o5g9v |
| Creator took | 1.5% of supply in the first block |
| Outside buyers | unknown 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. |
| Graduated | yes; we did not record when |
| Curve on chain | Read, and the account had gone. We went to the bonding curve account 4.1 days ago and it no longer existed, so the reading settles nothing either way. Read 2026-11-08 11:11 UTC. |
| Creator sold | not recorded - this venue's trades do not name the wallet |
| Recorded from | PBvu6UKo2xTxSB3g9SbwNf… slot 466,658,468
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result. peak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against
one; it is the record declining to state something. The column names link to their full entries in the
published schema, which is where the rest of the reason is written down. |
Order of events
| Created | 2026-11-07 21:10:58 UTC Slot 466,658,468, which is the chain's own clock for this moment. |
| Curve completed | Recorded as complete; we did not record when.
Not confirmed. An inference from decoded trade volume that nobody ever confirmed, and where the curve
account has since been read, the great majority of those returned incomplete. |
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. |
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 | FATCAT |
| Description | Deployed using https://j7tracker.io |
| Metadata held | sha256 b10602a9bad15857121b8741c6f061a1245ca86cc01f1a409cefb3fca6e6134d · 283 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 a241821e3ab120d72fb45efcf7af0f4cd0ff08accafa3281bdcd6321b7a585ae · 38,872 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-07 21:10 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.