one-pager
CLE one-pager v2: completeness, connections and scope
Published 2026-11-05 by the Chain Of Title LLC desk. Figures state the record as of the dates given in the text; the record itself is the source to check them against.
CLE session one-pager, version 2. Replaces the first draft (one-pager-cle-one-pager-not-all-of-it-is-on-the-chain), rebuilt around completeness, connections and scope, with the desk's notes on that draft applied: every figure dated, coverage window and never-cleared line stated. Figures not yet on a published page are dated placeholders, filled only from the published page on the day it is sent. Speaker bio is Mike's to supply.
NOT ALL OF IT IS ON THE CHAIN: LAUNCH-TIME EVIDENCE IN TOKEN DISPUTES
Length: 60 minutes (1.0 credit hour, subject to the host's accreditation) Format: in person or live webinar, with Q&A Audience: litigators, investigators, regulatory and compliance counsel, and in-house counsel handling digital-asset matters Content: educational. No product promotion or sales material is presented.
Abstract When a token is created, the blockchain permanently records the transaction, but not what the token said about itself. Its name, ticker, description, links and image sit in a separate file on an ordinary web server, where they can be changed or deleted, and often are within days. That file is also what connects one launch to another: when separate launches publish the byte-identical file, the link shows even where no money moves between their wallets. But a match needs both files, and a file can only be compared if someone captured it when it was published. This session explains what launch-time evidence exists, what disappears, and how a complete, contemporaneous record can show whether a single token stood alone or was one of many.
Learning objectives Attendees will be able to: 1. Distinguish what the blockchain permanently records about a token launch from what depends on an off-chain file that can change or disappear. 2. Explain how cryptographic hashing authenticates a captured file, and why a match between launches requires a copy of each file taken at the time of launch. 3. Assess whether a token at issue was isolated or connected to other launches, how those connections can be followed toward funding sources, and where identification must come from legal process rather than the record.
Outline - 0 to 5 min: Who was recording? Why evidence that exists for hours or days must be captured at the moment it is created. - 5 to 15 min: The basics, defined plainly: token launch, blockchain record, metadata file, hash, wallet, bonding curve, content-addressed storage. - 15 to 25 min: What disappears. On 28 September 2026, of 400 metadata files sampled at random from the largest ordinary host in the record, 364 were no longer served, and the Internet Archive held none of 53 checked. Files at content-addressed locations survived. - 25 to 40 min: What a complete record reveals. Launches that declared a byte-identical file, reported by tier without ranking: [IDENTICAL-DOCUMENT LAUNCHES, as of DATE] in all; [ACROSS 2+ WALLETS, as of DATE]; [ACROSS DIFFERENT TICKERS AND WALLETS, as of DATE]. One specimen, stated as counts. The admission rules: no connection on a single match; files shared by more than 20 creators excluded as templates. - 40 to 50 min: From connection to scope. Following connected wallets toward their funding, and the limits: a connection is not identity, and the record states no intent. Identification comes from discovery and legal process. - 50 to 60 min: Questions.
Materials provided to attendees - Session slides - A one-page glossary of terms - A written brief: "Launch-time records in token litigation" - The published method, corrections register and availability measurement, with sources
Speaker Mike Bomhoff, founder, Chain of Title LLC [SPEAKER BIO: three or four lines, supplied by Mike]
About the presenter's organization Chain of Title maintains a public register of Solana token launches recorded from the creation transaction, covering pump.fun, Raydium LaunchLab and Meteora DBC from 2 September 2026: [TOTAL, as of DATE] launches. A launch not on record is unknown, never cleared. The record states observations only and does not characterise any launch, issuer or person. Method: chainoftitle.org/method. Corrections: chainoftitle.org/corrections.
Contact: hello@chainoftitle.org