Launch record · observed at creation 2026-11-10 20:28 UTC
HERMES
hermes-agent
Also recorded, and not part of the finding above: this picture is on 4 other launches from 5 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, 56.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.
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-10 20:28 UTC |
| Creator | 5HrG7PNn9UnA3GFRnp7bZMRevgthQTLo6JSUJuYCFpNi |
| Creator took | 0.3% 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 7.8 h ago and it no longer existed, so the reading settles nothing either way. Read 2026-11-11 15:00 UTC. |
| Creator sold | not recorded - this venue's trades do not name the wallet |
| Recorded from | kks2RzksJLx7SpJ35AwpCf… slot 467,855,040
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.
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-10 20:28:54 UTC Slot 467,855,040, which is the chain's own clock for this moment. |
| Highest price seen | 2026-11-10 20:28:54 UTC +0s
1.972e-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. |
| 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 | On 5 launches from 5 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.2% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 168 launches from 147 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. Across the launches we watched at birth that stated a ticker, 89.5% wear one that more than one creator wallet has launched. See this ticker's page → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 1 other creator wallet, across 2 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, 64% of launches come from a creator linked to at least one other wallet this way. 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
| Name | hermes-agent |
| Metadata held | sha256 2971858a31de1177435f42c5e86cc475d1e1e6e18cec65a93efcca7c9b584824 · 311 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 bc336f4bb9d1768c2a8128dff466c6bd63a5810cf7cacb1bb3e761122435850d · 15,224 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-10 20:28 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.