XALYHP
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, XALYHP (xalyhP), mint 36NictugdCwzGyEtBn6rh579xzzTGH3CF6As3xjo87M9, observed at creation 2026-11-01 00:15 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/36NictugdCwzGyEtBn6rh579xzzTGH3CF6As3xjo87M9
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-01 00:15 UTC |
| Creator | Aca3XFjK4MuMvgd8Kw2tSsJ1iJXpbdXxV6XeUn4TGsqo |
| Creator took | 0.0% 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 | 5 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 | not recorded - this venue's trades do not name the wallet |
| Recorded from | YRsNU27ybCPy3XWHZfmz1u… slot 463,886,564
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. |
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-11-01 00:15:04 UTC Slot 463,886,564, which is the chain's own clock for this moment. |
| Curve completed | 2026-11-01 00:20:28 UTC +5m 24s Confirmed against the venue's own completion state. |
Times are the blocks' own timestamps, to the second: events in the same block share one, so their order within a block is not shown here.
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 | xalyhP |
| Description | Static analysis against known Solana vulnerability classes (account validation, CPI, PDA, ownership, signer, reinitialization, arithmetic, oracle/clock issues, etc.) Local dynamic analysis via LiteSVM / Mollusk-style simulation Multi-agent LLM layer for hypothesis and remediation suggestions Structured reports (JSON + Markdown) |
| Metadata held | sha256 74f4f492fc0b62ae1c96fdfbb8da435c074bf4f5344cf7ec5ed526c0d4cba4df · 621 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 48966536ccc8580153d12d2639f0fcd1f3fa01721eddba0f80c23a1fccf095d7 · 46,573 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-01 00:15 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.