FHOSTAGE
Also recorded, and not part of the finding above: this picture is on 2 other launches from 3 creator wallets in all. 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, 53.2% 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.
Cite this record as: Chain of Title, FHOSTAGE (FOMO hostage), mint DgpKqhvjwtsFUqyuBhaZxtp62nCWwJoKpx77iDUpump, observed at creation 2026-10-25 14:09 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/DgpKqhvjwtsFUqyuBhaZxtp62nCWwJoKpx77iDUpump
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 14:09 UTC |
| Creator | 6TZgCTHHM3QEYw2FQa8rtLMUtdVtdQmxfXGBHvyqg7YB |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 6 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 | 0 min after launch |
| Curve on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | no |
| Recorded from | 4zkRkhY2KEkcDRDko9F9nc… slot 461,285,838
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. |
Order of events
| Created | 2026-10-25 14:09:19 UTC Slot 461,285,838, which is the chain's own clock for this moment. |
| Creation block | 6 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-25 14:09:20 UTC +0s Confirmed against the venue's own completion state. |
| Thirty seconds in | 6 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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 53.2% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 4 launches from 4 creator wallets. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 88.2% wear one that more than one creator wallet has launched. See this ticker's page → |
| This document | The same launch document, byte for byte, as 2 other launches, across 3 creator wallets in all. Across the archive, 30.3% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
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 | FOMO hostage |
| Metadata held | sha256 de134cd7eb50c2ce98278ad7325dc1d8093d84bb19276d8185d7ea1ae0af3f74 · 322 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 040b37de5f971357814b0460a531a3f6b60c0328f6f1a20c91edea28db33be35 · 153,328 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-25 14:09 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.