ZY
Also recorded, and not part of the finding above: this picture is on 1 other launch from 2 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, 55.7% 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, ZY (Zenity), mint CRLqLK8AXvQgErbP4WRGnKxix8nvHGMY84PhxBWypump, observed at creation 2026-10-26 00:38 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/CRLqLK8AXvQgErbP4WRGnKxix8nvHGMY84PhxBWypump
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-26 00:38 UTC |
| Creator | A9fupPE7HvURzGmMVwULNR8TCf7Wsz7GwHzfzHJVMVtb |
| Creator took | 1.0% of supply in the first block |
| Outside buyers | 9 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: 9 within the first 30s, 9 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 | 0 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 | not while we watched |
| Recorded from | AgXoTbWfDh5744t3cRCXHx… slot 461,463,641
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
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-26 00:38:43 UTC Slot 461,463,641, which is the chain's own clock for this moment. |
| Creation block | 9 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-26 00:38:47 UTC +4s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 9 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. |
| Highest price seen | 2026-10-26 00:40:07 UTC +1m 24s
1.894e-6 SOL per token.
Reported by a third-party price feed with no trade witnessed, which is a materially weaker claim than a
decoded one.
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 picture | On 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 55.7% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 7 launches from 7 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.4% 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 1 other launch, across 2 creator wallets in all. Across the archive, 32.5% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 1 other creator wallet, across 3 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, 63.9% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
Pool
| Liquidity | 224.0 SOL |
| Read from chain | 2026-11-08 07:10 UTC, just now |
What this launch claimed to be
| Name | Zenity |
| Description | Zenity is a security and governance platform for AI agents and AI overall. Copilots, autonomous agents and apps built by business users are spreading fast inside organizations, and most of them sit outside traditional security controls. Zenity gives security teams visibility and control over all of them. The platform covers the whole agent lifecycle. It keeps an inventory of every agent and app, runs posture management to catch misconfigurations and excessive permissions, and does runtime detection and response to block threats like prompt injection, data exfiltration and unsafe actions, effectively protecting against rogue ai. It supports major enterprise platforms including Microsoft 365 Copilot, Copilot Studio, Power Platform, Salesforce Agentforce and ServiceNow. With a high demand for Zenity's software the team is opening up investing through the blockchain backed 1:1. Each token would be backed by underlying equity held in custody, with regular third-party attestations published on chain. Regulated access. On chain transfers. Holders could transfer tokens on approved trading venues, subject to the transfer restrictions built into the token’s smart contract. Transparent records. Ownership, supply and corporate actions such as dividends or splits would be recorded on chain. |
| Metadata held | sha256 a8139056b29aea16533e2ce85f7630b2b82779135415ce172c9807a1a8be4ebd · 1,784 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-11-02 00:40 UTC. |
| Picture held | sha256 2c552046a13ae36362c07fdee4b4cdab64930c13064e678b0054180506ad2844 · 31,496 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-26 00:38 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.