JITDEPLOY
Also recorded, and not part of the finding above: this picture is on 9 other launches from 3 creator wallets in all, and this creator has 27 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. Across the archive, 48.9% 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, JITDEPLOY (JIT DEPLOY), mint 2g3Q2o68Y8bmjgNA6ZvZBbLFbskt2qDXQR4BLQ3gA7qQ, observed at creation 2026-10-12 17:56 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/2g3Q2o68Y8bmjgNA6ZvZBbLFbskt2qDXQR4BLQ3gA7qQ
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-12 17:56 UTC |
| Creator | HTPMc2prDS1JuRx65QN1EkTuG8pBAzknkdfdxnTt83g7 |
| 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 | 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 | not recorded - this venue's trades do not name the wallet |
| Recorded from | 4UbZjHm2YR8enRe8p2uJJH… slot 456,136,676
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.
Order of events
| Created | 2026-10-12 17:56:56 UTC Slot 456,136,676, which is the chain's own clock for this moment. |
| Curve completed | 2026-10-12 17:57:00 UTC +4s 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.
Seen before
| This picture | On 10 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 48.9% of the launches whose picture we hold carry one a different creator also used. See them → |
| This document | The same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. Across the archive, 25.7% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| This creator | 27 earlier launches, 22 confirmed complete on chain. Across the archive, 70% of launches come from a creator with more than one launch on record. See the creator's launches → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 32 other creator wallets, across 53 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, 58.4% 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 | JIT DEPLOY |
| Description | JIT DEPLOY |
| Metadata held | sha256 6f1835633dc10e4d9b51305b3219be6d0c592a865c6ae2865e0c58fa54de4f94 · 208 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 8ac5027707aee748b6f91e37245e355ae8a6678869f98d6a10db5353a1a60d9c · 32,312 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-12 18:10 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.