stackchain/troupe-standup
2
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
b38533ea04e2c19fc8473ffcbcc2017133cd7ae5
troupe-standup/recoveries/falsification-pass.md
T

7.9 KiB
Raw Blame History

Falsification pass — Q4

Date: 2026-09-24 · By: zephyrus-sparkborn · Method: public sources only, no credentials, no pushes.

Three public claims from the Stackchain community archive (https://alexanderwhitestone.com/stackchain/), each attacked as hard as this environment allows. "It survived" counts as success — the point is testing the archive, not finding a scalp. Every factual statement below carries its source or the word unverified.

Claim 1 — the profile counts

The claim (verbatim, https://alexanderwhitestone.com/stackchain/):

"18 public profiles 13 documentary-backed 5 candidate portraits"

Break attempt — recount the profiles from public pages, independently of the archive's own arithmetic:

  1. browser.open https://alexanderwhitestone.com/stackchain/people/ → fetch failure (browser-service could not fetch the page).
  2. browser.open https://alexanderwhitestone.com/stackchain/people (no trailing slash) → fetch failure.
  3. browser.open https://alexanderwhitestone.com/sitemap.xml → fetch failure.
  4. Web search for profile pages (alexanderwhitestone.com stackchain profile portrait "documentary-backed") → no profile pages surfaced; only the index page is indexed (consistent with Timmy's reply 03 note that the site: operator cannot corroborate profile-page indexing either).
  5. Wayback availability API for alexanderwhitestone.com/stackchain/people/ → {"archived_snapshots": {}} — no snapshots exist.
  6. Two Wayback CDX prefix queries for person/profile/people URL patterns → fetch failures from this environment.
  7. Grep of the troupe-standup repo (checkins, recoveries, replies) → no profile page URLs known locally.

Raw results: no independent enumeration was possible. The arithmetic is internally consistent — 13 + 5 = 18 (Timmy verified the same in reply 04) — but the underlying counts could not be recounted.

Verdict: Partial. The arithmetic holds and nothing contradicts it, but the claim's substance (18 public profiles; the 13-vs-5 tier split) is unverified by this pass: the listing page is unreachable from here, profile pages are not indexed by search engines, and Wayback holds no copy of the listing. Not disproven — untested.

Claim 2 — the SJ Lottery publication date

The claim (verbatim, https://alexanderwhitestone.com/stackchain/):

"Published January 30, 2023 · excerpt from 02:07.00–03:52.70 in the original recording"

The ledger event page (https://alexanderwhitestone.com/stackchain/event-2023-01-30-burnchain-and-loko-s-sj-lottery-are-already/) states the basis explicitly:

"Date: 2023-01-30 · basis: podcast publication timestamp: 22:15 UTC"

Break attempt — find any public source that disagrees with January 30, 2023, or shows the date is ambiguous:

  1. Fresh fetch of the publisher's RSS feed, https://anchor.fm/s/c64de45c/podcast/rss (2026-09-24): the Stackchain SJ Lottery item carries guid 6ec57334-604d-42b5-a2e7-54662739c504 and pubDate Mon, 30 Jan 2023 22:15:54 GMT — matching the archive's "22:15 UTC" basis to the minute.
  2. The old ambiguity, checked at the source: the feed's own ordering places Stackchain Ordinals What's the deal? (Sun, 05 Feb 2023 22:42:30 GMT) immediately before SJ Lottery — confirming the "Feb 05" stamp that misled a pass-1 reading belongs to the adjacent Ordinals episode, not to SJ Lottery.
  3. Third-party directory: https://www.podcastrepublic.net/podcast/1654425194 (episode table, date-follows-title layout independently validated against Apple in reply 03) lists "Stackchain SJ Lottery — Jan 30, 2023".
  4. podcasters.spotify.com episode-list snippet shows a "Feb 05, 2023 02:00:11" stamp immediately before the SJ Lottery heading — the known card-boundary artifact (the stamp closes the preceding Ordinals card; reply 04 traced it in the raw DOM). It is not a competing date for SJ Lottery.

Raw results: RSS pubDate Mon, 30 Jan 2023 22:15:54 GMT; podcastrepublic Jan 30, 2023; Apple record 2023-01-30T22:15:54Z (per reply 04). No source found assigning any other publication date to SJ Lottery.

Verdict: Survived. Three independent sources agree on January 30, 2023, and the single apparent disagreement is a documented layout misread, not a real conflict.

Side observation (not an archive claim, flagged for the pipe): today's feed gives SJ Lottery itunes:duration 02:00:10, while reply 04 recorded itunes:duration 01:23:22 as matching the episode — in the same feed, 01:23:22 belongs to the adjacent episode Stackchain 1 more Sat. No archive page asserts a duration for SJ Lottery, so no archive claim breaks; but the reply-04 record looks misattributed (cause unverified — feed may have been misread, or the value compared against a non-public record).

Claim 3 — "the last block he mined" (block 97,250)

The claim (verbatim, https://alexanderwhitestone.com/stackchain/magazine-040/, "What happened"):

"It closes with Satoshi resting on the 97,250th block, a nod to the last block he mined."

Break attempt — check against independent Bitcoin sources whether block 97,250 is plausibly Satoshi's last mined block:

  1. Web search "Satoshi Nakamoto last block mined 97250":
    • Whale Alert analysis (reported by u.today / bitcoinethereumnews, 2025-07-31): "Satoshi Nakamoto remained active until Bitcoin block 54,316", estimating 1,125,150 BTC "mined up to block 54,316".
    • Bitquery reconstruction (tradingview.com, Sep 2026): "The mining pattern began with the genesis block… and ceased around block 54,000 in mid-2010."
  2. mempool.space API (independent chain data):
    • GET https://mempool.space/api/block-height/97250 → hash 0000000000051607bb75bde078238fd652a72da21b049b438837ee159c67606c; block details → timestamp 1292189407 = 2010-12-12 21:30:07 UTC (command: date -d @1292189407, TZ=UTC).
    • GET https://mempool.space/api/block-height/54316 → hash 000000000d1e2cf92a7e6afdbed6d34fc3ac2cc863d9a236ca4db394a94ece2e; block details → timestamp 1272892627 = 2010-05-03 13:17:07 UTC (command: date -d @1272892627, TZ=UTC).

Raw results: the best-known public analyses place the end of Satoshi's mining activity around block 54,316 (May 2010) — 42,934 blocks (~7.3 months) before block 97,250 (Dec 12, 2010). No source found ties 97,250 to Satoshi's last mined block. (Notably, 2010-12-12 is the date of Satoshi's last known forum post — the satire may be nodding to his last public activity, not his last block.)

Verdict: Broken — on the interpretive gloss. The entry itself is heavily hedged ("Machine-written summary, not an editorial statement"; "Archive summary of a published article, not the article itself"), which limits the blast radius, and the descriptive part (the satire piece ends at block 97,250) was not tested: the article-level URL is not published on the page (the Q3 citation-flag finding), so the original piece could not be checked. But "a nod to the last block he mined" is not supported by any public analysis found — the analyses found contradict it.

Limits — what this pass did not test

  • Only three claims: one site-wide count (Partial — unrecountable from here), one publication date (Survived), one interpretive gloss on a satire piece (Broken). Nothing else.
  • Not tested: paraphrase fidelity of the 91 magazine entries (the open Q3-leftover item); the absolute placement of the burnchain excerpt inside the original recording; the 13-vs-5 profile split beyond arithmetic; any testimony-only claim; the original magazine article behind entry 40 (article-level URLs are unpublished on the page).
  • Environment limits: no JS rendering (the people listing is likely a JS app), no logged-in X session, no Wayback CDX access from this environment, and search engines index only the archive's index page. All verdicts are point-in-time, 2026-09-24.
Reference in new issue View Git Blame Copy Permalink