Evidence and methodology

Last updated 2026-10-28. Information as of Oct 28 2026.

Every factual statement on this site is meant to be checkable. This page lists the primary sources and shows how each finding was derived. Third-party files are not republished here; the manifest gives the original or archive URL and the SHA-256 of the file as we retrieved it, so you can re-fetch and compare.

On-chain evidence

All six transactions can be opened in any Dogecoin block explorer. The full IDs, block heights, input and output counts, fees and explorer links are in transactions.csv. Per-input results (sighash byte and where each inscription ended up) are in inputs.csv.

• Recipient address: D6ZJAGkdFJn9cb3y2QAVwv5QtMXfVHihZ4 (SoChain).
• Blocks: 6431226 (confirmed 2026-10-26 11:09:31 UTC) and 6431231 (confirmed 2026-10-26 11:13:08 UTC).

Methodology

1. Transactions. We read the six transactions and their previous outputs from a public block-explorer API (BlockCypher transaction format; SoChain links are given for convenience), and parsed each input script to read the final byte of the signature (the sighash type).
2. Inscription location. For each input we looked up which inscription it held using a public inscription-lookup API for inscription numbers and holdings, and computed its position with the ordinals sat-flow rule (units flow from inputs to outputs in order, and then to the fee, then to the miner). This gave 201 delivered and 63 to coinbase outputs. Indexers can differ. The six transactions are public, so the computation can be repeated and checked.
3. Client code. We downloaded the live marketplace pages, JavaScript chunks and publicly served source maps on Oct 27 and Oct 28 2026, hashed them, and extracted the signing source file. We compared archived chunks from the Internet Archive across 2025 and 2026 to see when the 0x82 constant appeared.
4. Deployment comparison. We diffed the client code of an archived deployment (Oct 4 2026) with the live deployment (Oct 27 2026). The differences we found were a maintenance banner, a new “Trading temporarily paused” notice component, deployment identifiers and styling classes. We found no change in the signing code or listing structures.
5. Live-site re-check. On Oct 28 2026 we re-fetched the same files. The homepage, terms page and the JavaScript chunks we listed were byte-identical (same SHA-256) to the Oct 27 files. See the status log.
6. Prices. Documented on scale and value.

Limits

• The Internet Archive does not capture every file on every day. Absence of a capture is not evidence of absence of a change.
• Source maps show the source that was compiled. We did not see the marketplace’s server-side code or databases.
• Our reading of 0x82 describes what the signature commits to. It does not tell us how the signed inputs were obtained (see what we cannot know).
• We may be wrong. If you find an error, use the corrections process.

How to verify a hash

Download the file from the URL in the table (for archived files use the “id_” raw form where given) and run sha256sum file. The value should match. For live files, the live site may have changed since the capture time shown.

Evidence manifest (44 items)

Machine-readable: evidence_manifest.json.