HALLOWEEK
Also recorded, and not part of the finding above: this creator has 4 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, HALLOWEEK, mint Hw9s2Si2MUXxZasQhNrorqueGKWEwLy8nXzWcvJ7iray, observed at creation 2026-10-20 02:29 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/Hw9s2Si2MUXxZasQhNrorqueGKWEwLy8nXzWcvJ7iray
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-20 02:29 UTC |
| Creator | AB2mPLaGbxSvxvy4KffbUcnkp5doTbBAXantfYLSyQuM |
| Creator took | 79.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 | in the same batch of events as the 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 | not recorded - this venue's trades do not name the wallet |
| Recorded from | 2aZBAVqqWCEC5oKBYD7KY8… slot 459,064,971
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. |
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-20 02:29:12 UTC Slot 459,064,971, which is the chain's own clock for this moment. |
| Curve completed | 2026-10-20 02:29:12 UTC Confirmed against the venue's own completion state. |
| Highest price seen | 2026-10-20 02:29:12 UTC
2.796e-8 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. |
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 | 4 earlier launches, 1 confirmed complete on chain, 2 with findings on record. Across the archive, 70% of launches come from a creator with more than one launch on record. See the creator's launches → |
Who took the curve
One transaction bought 86 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
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 | HALLOWEEK |
| Description | HALLOWEEK IS LIVE NOW!!! |
| Metadata held | sha256 6a6de014d16ea8dd0240aefb54fb61a0a07e5c6b75781d177f5af51efdb3c9b6 · 207 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 | Not captured, so we cannot show what it published. That is our storage budget, not a finding about the launch. |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-20 02:29 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.