Spidoge
Also recorded, and not part of the finding above: this picture is on 7 other launches, and this creator has 1,499 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. 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.
Cite this record as: Chain of Title, Spidoge, mint 57efDh62UeTXKidU6v9qhp8JUyGrgKiy2jB8twmpump, observed at creation 2026-10-25 21:42 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/57efDh62UeTXKidU6v9qhp8JUyGrgKiy2jB8twmpump
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-10-25 21:42 UTC |
| Creator | 2JxPmU9UU5KhSQ7h5v8PfhgbxPQhHNyBqNrhPAjPiWCu |
| Creator took | 15.0% of supply in the first block |
| Outside buyers | 1,129 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: 18 within the first 30s, 5 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. |
| Graduated | 36 min after launch |
| Curve 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 | yes |
| Recorded from | 5HLBSSSa9WdEBHQeKm5Nrn… slot 461,413,990
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | 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. |
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.
Several launches in one matter
A pack of 10 of these documents is $200, redeemed one launch at a time whenever you find the next one. You get a code by email; it does not expire.
Order of events
| Created | 2026-10-25 21:42:49 UTC Slot 461,413,990, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 18 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. |
| Curve completed | 2026-10-25 22:18:21 UTC +35m 32s Confirmed: a PumpSwap pool was found for it. |
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 creator | 1,492 earlier launches, 32 confirmed complete on chain. Across the archive, 70.2% of launches come from a creator with more than one launch on record. See the creator's launches → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 628 other creator wallets, across 1,201 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. Across the archive, 61.2% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
Pool
| Liquidity | 4.9 SOL |
| Read from chain | 2026-10-26 07:37 UTC, just now |
What this launch claimed to be
| Name | Spidoge |
| Metadata held | sha256 9d3ba33e8c692949a4de42e09455a237116b6574615c70cf0ade735bf2fefe84 · 307 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 2fed1495f6e0078d4a2e3cc6ddf123500cd8b61193928b416eb6ebe9344df3c9 · 12,377 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-25 21:42 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.