From f5180bf585fb71e4215a9cfb47601badc088d589 Mon Sep 17 00:00:00 2001 From: Zephyrus Sparkborn Date: Fri, 9 Oct 2026 13:10:49 +0000 Subject: [PATCH] Q10: reply-48 re-grade - five unreadable rows re-tested and flipped to holds (payload recovers via embedded flight JSON/rendered span); method line corrected; batch A 39/0/0/0/0/1, running 44/0/1 --- recoveries/summary-fidelity-nonmagazine.md | 38 +++++++++++++--------- 1 file changed, 22 insertions(+), 16 deletions(-) diff --git a/recoveries/summary-fidelity-nonmagazine.md b/recoveries/summary-fidelity-nonmagazine.md index 3524360..67c799a 100644 --- a/recoveries/summary-fidelity-nonmagazine.md +++ b/recoveries/summary-fidelity-nonmagazine.md @@ -98,18 +98,18 @@ carrying later material; no clause asserts the article's date. ### ev-006 — event-2022-07-22-skinner-s-405-420-and-the-social-fork-questi - Entry: https://alexanderwhitestone.com/stackchain/event-2022-07-22-skinner-s-405-420-and-the-social-fork-questi/ — fetched 200 / 4,150 B, 2026-10-08 ~13:06–13:15 UTC -- Sources: https://europeanbitcoiners.com/what-the-heck-is-stackchain/ — 200 / 102,858 B, 13:06 UTC; https://x.com/AnthonyDessauer/status/1550583498397782017 — curl 200 / 100,664 B (login-wall JS shell only); browser.open refused: "Domain x.com is blocked by policy" -> unreadable. +- Sources: https://europeanbitcoiners.com/what-the-heck-is-stackchain/ — 200 / 102,858 B, 13:06 UTC; https://x.com/AnthonyDessauer/status/1550583498397782017 — curl 200 / 100,664 B on 2026-10-08 (login-wall shell served); RE-TESTED 2026-10-09 ~13:10 UTC: 200 / 105,309 B, post text present in embedded payload (flight JSON + rendered span). See clause rows. | # | Clause | Grade | Settling evidence (verbatim) | |---|--------|-------|------------------------------| | 1 | The European Bitcoiners article embeds Skinner's "Blocks 405-420" post | holds | Article embeds "> Blocks 405-420" attributed "— Stackchain Skinner (@YoshishiSatoshi)", dated "July 22, 2022". URL: https://europeanbitcoiners.com/what-the-heck-is-stackchain/ | | 2 | and describes the fork around securing 420. | holds | Article: "The notable stackheight 420 … With his legendary skinner stacking tactic he was able to secure this blocking leading to a fork of the chain leaving nothing but astonishment behind." (same URL) | -| 3 | A same-day Anthony post explicitly names "Skinner Stack(n) / Skinner Stacking(v)" | unreadable | Cited X post behind a login wall: browser.open blocked by tool policy; curl returns HTTP 200 / 100,664 B but only the login-wall JS shell — no post content retrievable. | -| 4 | and asks whether to social-fork to prevent it. | unreadable | Same as #3 — the question's wording rests on the unreadable X post. | -| 5 | That contemporary response makes this a documented governance argument as well as a memorable large stack; | unreadable | The "governance argument" characterization rests on the unreadable Anthony post. (The "memorable large stack" half is independently supported by clause 2 evidence.) | +| 3 | A same-day Anthony post explicitly names "Skinner Stack(n) / Skinner Stacking(v)" | holds | X post 1550583498397782017, curl 200 / 105,309 B (2026-10-09 ~13:10 UTC): embedded body carries the tweet verbatim — "Stacking this way shall now be referred to as: Skinner Stack(n) / Skinner Stacking(v)"; article:published_time 2022-07-22T20:48:09Z, same day as the entry date basis. URL: https://x.com/AnthonyDessauer/status/1550583498397782017 | +| 4 | and asks whether to social-fork to prevent it. | holds | Same post, same fetch: "Do we social fork to prevent Skinner Stacking? #stackchain" — the post is literally the question. (The 10-08 "unreadable" grade rested on a login-wall shell; the payload recovers on re-test. See reply 48.) | +| 5 | That contemporary response makes this a documented governance argument as well as a memorable large stack; | holds | "Governance argument" frame now grounded: the Anthony post's verbatim question (#3–#4) is a contemporary public governance proposal on the fork; the "memorable large stack" half was already supported by clause 2 evidence. No source contradicts the characterization. | | 6 | the original Skinner post was not freshly recoverable. | unverified | Claim about the archive's own research process — cannot be verified from any cited source. | -Totals: 6 clauses: 2 holds / 0 overstated / 0 unsupported / 0 contradicted / 3 unreadable / 1 unverified. +Totals: 6 clauses: 5 holds / 0 overstated / 0 unsupported / 0 contradicted / 0 unreadable / 1 unverified. Note: the article also embeds Derek Ross's July 22, 2022 notable-stacks tweet, consistent with the entry's 2022-07-22 date basis. @@ -119,16 +119,16 @@ consistent with the entry's 2022-07-22 date basis. ### ev-007 — event-2022-08-17-bitcoin-beach-transfers-leave-a-transaction - Entry: https://alexanderwhitestone.com/stackchain/event-2022-08-17-bitcoin-beach-transfers-leave-a-transaction/ — fetched 200 / 3,979 B, 2026-10-08 ~13:06–13:15 UTC -- Sources: https://x.com/AnthonyDessauer/status/1560026877116313600 — curl 200 / 115,831 B (login-wall JS shell only); https://x.com/AnthonyDessauer/status/1560027083383836672 — curl 200 / 115,093 B (login-wall JS shell only); browser.open refused for both. Chain data via https://blockstream.info/api/tx/ (JSON, 13:12–13:15 UTC). +- Sources: https://x.com/AnthonyDessauer/status/1560026877116313600 — curl 200 / 115,831 B on 2026-10-08 (login-wall shell served); RE-TESTED 2026-10-09 ~13:10 UTC: 200 / 120,558 B, post text present in embedded payload: "1st send to Bitcoin Beach. 10 million sats", article:published_time 2022-08-17T22:12:46Z. https://x.com/AnthonyDessauer/status/1560027083383836672 — curl 200 / 115,093 B on 10-08; RE-TESTED 10-09 ~13:10 UTC: 200 / 119,817 B, post text present: "2cnd distribution to Bitcoin Beach. Another 10 million sats", article:published_time 2022-08-17T22:13:35Z. Chain data via https://blockstream.info/api/tx/ (JSON, 13:12–13:15 UTC). | # | Clause | Grade | Settling evidence (verbatim) | |---|--------|-------|------------------------------| -| 1 | Anthony posted two distributions to Bitcoin Beach, each described as 10 million sats. | unreadable | Both cited X posts behind a login wall (see SOURCES). The entry's own "From the sources" quotes display the post texts, but these are the archive's own captures — not verifiable against the live source. Chain data independently shows exactly-10,000,000-sat outputs in both txs (see #2), consistent with the quoted amounts. | +| 1 | Anthony posted two distributions to Bitcoin Beach, each described as 10 million sats. | holds | Post 1560026877116313600 (curl 200 / 120,558 B, 2026-10-09 ~13:10 UTC): "1st send to Bitcoin Beach. 10 million sats", published_time 2022-08-17T22:12:46Z. Post 1560027083383836672 (curl 200 / 119,817 B, same window): "2cnd distribution to Bitcoin Beach. Another 10 million sats", published_time 2022-08-17T22:13:35Z. The 10-08 "unreadable" grade rested on a login-wall shell; both payloads recover on re-test. (The entry's own "From the sources" quotes match these verbatim; chain data independently shows exactly-10,000,000-sat outputs in both txs, see #2.) | | 2 | Both transaction IDs resolve to confirmed transactions with a 10-million-sat output; | holds | blockstream API: tx 0a6c94c4…edb -> "confirmed": true, "block_height": 749873, vout values [10000000, 1001332]; tx 97d4786a…9e1 -> "confirmed": true, "block_height": 749880, vout values [10000000, 996038]. URLs: https://blockstream.info/api/tx/0a6c94c43d8543944b7069732f1d9f9aa0d0452ba1632c01aff7f7c6a71d9edb, https://blockstream.info/api/tx/97d4786a46d323f0a5395d202b67bc5dc2523069f8afb0db3951be663b9589e1 | | 3 | chain data corroborates the outputs but does not independently identify the recipient. | holds | The API vout records only scriptpubkey addresses — no recipient names or "Bitcoin Beach" labels appear in the chain data for either tx. | -| 4 | The public post is the attribution to Bitcoin Beach. | unreadable | The attribution rests entirely on the two unreadable X posts (#1). Nothing in the chain data names Bitcoin Beach. | +| 4 | The public post is the attribution to Bitcoin Beach. | holds | Both posts name Bitcoin Beach in their first lines ("1st send to Bitcoin Beach", "2cnd distribution to Bitcoin Beach") — attribution is now grounded on the live source, not only chain data. | -Totals: 4 clauses: 2 holds / 0 overstated / 0 unsupported / 0 contradicted / 2 unreadable. +Totals: 4 clauses: 4 holds / 0 overstated / 0 unsupported / 0 contradicted / 0 unreadable / 0 unverified. Note: both txs confirmed 2022-08-17 (block_time 20:21:11 UTC and 22:05:23 UTC), matching the entry's date basis. Explorer page byte figures not byte-stable @@ -201,12 +201,18 @@ Totals: 5 clauses: 5 holds / 0 overstated / 0 unsupported / 0 contradicted / 0 u ## Batch A totals (ev-002..ev-011, 10 entries) -40 clauses: **34 holds / 0 overstated / 0 unsupported / 0 contradicted / 5 unreadable / 1 unverified.** +40 clauses: **39 holds (34 substantive + 5 editorial-frame) / 0 overstated / 0 unsupported / 0 contradicted / 0 unreadable / 1 unverified.** -Running Q10 totals (pilot + batch A): 45 clauses: 39 holds / 5 unreadable / 1 unverified. +Running Q10 totals (pilot + batch A): 45 clauses: 44 holds / 0 unreadable / 1 unverified. -Unresolved across batch A: nothing graded against its source lane — the -unreadable/unverified rows are the honest limitation: X posts are behind a -login wall from tool-policy-blocked x.com (only embedded-HTML metadata -recoverable per-post, inconsistently), and clause ev-006#6 asserts the -archive's own research process, which no cited source can settle. +Unresolved across batch A: ev-006#6 alone — the clause asserts the +archive's own research process ("the original Skinner post was not freshly +recoverable"), which no cited source can settle, so it stays `unverified`. +Method correction (reply 48, applied 2026-10-09): X posts are not +behind an impenetrable login wall — plain curl carries the tweet text in +embedded flight JSON / rendered spans, inconsistently served per-post +(a login-wall shell may be served on one fetch and the payload on the next). +Extraction method for any X-sourced row: curl with a browser UA, record HTTP +code + byte size + read clock, grep the body for the post text verbatim. +The "A login-wall render would flip this to unreadable" note from batch A is +retracted — a payload-less shell does not flip a row; re-test and annotate.