Preliminary report · preview, read 2026-11-14 23:49:42 UTC
10 launches from this wallet. 6 other wallets launched with the identical files.
Bqm1Kshx8yPnDYFTdTTPo976KjiWsKTnGf3sr3HVo2f8
On its own, a launch reads as one launch. This is what the record ties to the wallet behind it.
Every count here is real, and free. Which wallets, which launches and which files: each is struck out like this ██████████ until you open the report.
Preliminary report
Bqm1…o2f8
What the record ties to it.
Wallets that launched with the same files
6 other creator wallets launched with a file byte-identical to one this wallet launched with. The 6 listed have 65 launches on record between them. Most shared files first.
| Other wallet | Kinds of file | Files shared | Its launches | First launch | Latest launch | |
|---|---|---|---|---|---|---|
| 1 | ██████████ | 3 | 3 | 13 | 2026-11-08 | 2026-11-08 |
| 2 | ██████████ | 3 | 3 | 12 | 2026-11-09 | 2026-11-09 |
| 3 | ██████████ | 3 | 3 | 13 | 2026-11-08 | 2026-11-08 |
| 4 | ██████████ | 3 | 3 | 13 | 2026-11-09 | 2026-11-09 |
| 5 | ██████████ | 3 | 3 | 13 | 2026-11-08 | 2026-11-08 |
| 6 | ██████████ | 2 | 2 | 1 | 2026-11-09 | 2026-11-09 |
An independent reuse is a separate occasion on which the two wallets carried the same file: several shared files riding one pair of launches count once. "Not read" is a figure this document did not read, never a zero.
The files they share
5 files shared between this wallet and those wallets, the ones carried by the most of them first. A picture and a launch document are matched by the sha256 of their bytes.
| Kind | File | Paired wallets carrying it | Launches on record carrying it | Creator wallets on record carrying it |
|---|---|---|---|---|
| Launch document | ██████████ | 5 | 8 | 6 |
| Picture | ██████████ | 5 | 8 | 6 |
| Ticker and name | ██████████ | 5 | ||
| Picture | ██████████ | 1 | 5 | 2 |
| Ticker and name | ██████████ | 1 |
The group
The chain of shared files leading out from this wallet passes the size at which this register states a group, so none is stated. A chain that long usually runs through a file many unrelated wallets used. The direct pairings above are unaffected: each one is this wallet and one other, and the files they share.
This wallet's launches
10 launches, the first on 2026-11-09 and the most recent on 2026-11-09, on 1 separate day. Its busiest day was 2026-11-09, with 10. It has used 6 tickers, one of them 4 times.
| Launched | Ticker | Name | Mint |
|---|---|---|---|
| 2026-11-09 12:46:00 UTC | ██████████ | ██████████ | ██████████ |
| 2026-11-09 12:45:27 UTC | ██████████ | ██████████ | ██████████ |
| 2026-11-09 12:41:55 UTC | ██████████ | ██████████ | ██████████ |
| 2026-11-09 12:33:14 UTC | ██████████ | ██████████ | ██████████ |
| 2026-11-09 12:29:26 UTC | ██████████ | ██████████ | ██████████ |
| 2026-11-09 12:24:35 UTC | ██████████ | ██████████ | ██████████ |
| 4 more launches in the report. | |||
What this is, and what a signed report adds
- This is the register's own output, read at the moment above. It carries no signature, no custodian declaration and no addressee.
- It states what was recorded and never what it means. A shared file establishes that the same file was used. It does not establish who used it.
- It covers the launches this register holds, which is not every launch on chain.
- A provenance report ($7,500) is scoped in writing to your matter and adds: the custody of each file from capture to the page, the per-launch ledger with the transaction behind every figure, the funding of the wallets traced hop by hop, and a custodian declaration executed on request.
Open this report
Everything above with the wallets, the launches and the file hashes in it: 6 paired wallets, 5 shared files and 10 launches from this wallet, each by its address. Frozen at the moment you buy it, at a permanent link, with a clean PDF from the page.
One payment, by card, no account. The link arrives by email and is permanent. If you go on to a signed provenance report on this matter, the $750 comes off its $7,500.
Chain Of Title LLC. The method is published at https://chainoftitle.org/method and does not vary by customer; corrections are at https://chainoftitle.org/corrections.