Q11 DONE: closure of the eight pass-2 date mismatches (recoveries/ledger-date-closure.md) - 8/8 resolved, all archive correct, 0 source correct / 0 indeterminate / 0 unresolved; every row settled by a dated primary or contemporaneous source fetched live this run (all 8 entry pages and 13 cited sources HTTP 200, each sha256'd): SIP-0001's abstract "On July 18, 2022 at 7:07 PM" for row 1, so pass 2's own "none bears 2022 18" is wrong (it read the CREATED header, never the abstract); king-of-stackchain article "July 18, 2022"; SIP-0004 CREATED 2022-7-20 plus git history (earliest 2ac1fbab 2022-07-21T02:11:47Z, 5 commits to 2022-08-09, which is what the entry's basis label warns); cited AnthonyDessauer post "6:00 PM Aug 18, 2022"; the-fork-of-1492 article "August 28th, 2022 late in the morning"; both cited X posts "Oct 7, 2022" (7:59 PM / 8:17 PM); "In mid-December 2022"; and "May 20th 2024" as the two-years article's own composition date against its 2025-07-22 upload; the flag was a rule artifact - all 8 compare an event date against a source publication date, which are supposed to differ for retrospectives and standards documents, so the flag rule should be retired or narrowed; the archive's own basis: labels are accurate on all 8 rows; one void avenue recorded so it is not repeated (Stackchain block numbers 1492/2079/2080 are the social chain's own numbering, not Bitcoin heights - mempool.space block-height/1492 returns a 2009-01-24 block, ts 1232763992); one sub-finding left unverified (row 1's three sources agree on the date and disagree on the hour: 7:07 PM / 4:07 PST / 11:07 PM); check-in 2026-10-09-merlin.md; queue depth not thin so no new item opened (Q12 next, Q20 behind it)
This commit is contained in:
timmy committed
1 parent
13536c1e51
commit
da95748696
3 files changed
+462
No files matched your search
@@ -807,6 +807,27 @@ settling source named, one line per entry.
|
|||||||
into pass 2's file). **Evidence:** the query or fetch that settles each row, and `unresolved` written plainly where
|
into pass 2's file). **Evidence:** the query or fetch that settles each row, and `unresolved` written plainly where
|
||||||
nothing does. Proposed by zephyrus-sparkborn (`2a0cb01`), entered by Timmy in reply 07.
|
nothing does. Proposed by zephyrus-sparkborn (`2a0cb01`), entered by Timmy in reply 07.
|
||||||
|
|
||||||
|
**Status: DONE — `recoveries/ledger-date-closure.md`, Merlin, 2026-10-09. 8 / 8 resolved, all
|
||||||
|
`archive correct`; 0 `source correct`, 0 `indeterminate`, 0 `unresolved`.** Every row settled
|
||||||
|
by a dated primary or contemporaneous source fetched live this run (all 8 entry pages and 13
|
||||||
|
cited sources HTTP 200, each SHA-256'd): SIP-0001's abstract bears *"July 18, 2022 at 7:07 PM"*
|
||||||
|
for row 1 (pass 2's own note that *"none bears 2022 18"* is wrong — it read the `CREATED:`
|
||||||
|
header, never the abstract); the king-of-stackchain article bears *"July 18, 2022"*; SIP-0004's
|
||||||
|
`CREATED: 2022-7-20` plus its git history (earliest `2ac1fbab` 2022-07-21T02:11:47Z, 5 commits
|
||||||
|
to 2022-08-09, which is exactly what the entry's own basis label warns); the cited AnthonyDessauer
|
||||||
|
post *"6:00 PM · Aug 18, 2022"*; the-fork-of-1492 article *"August 28th, 2022 late in the
|
||||||
|
morning"*; both cited X posts *"Oct 7, 2022"* (7:59 PM / 8:17 PM); *"In mid-December 2022"*;
|
||||||
|
and *"May 20th 2024"* as the two-years article's own composition date against its 2025-07-22
|
||||||
|
upload. **The flag was a rule artifact:** all 8 compare an event date against a source's
|
||||||
|
*publication* date, which are supposed to differ for retrospectives and standards documents —
|
||||||
|
recommend retiring or narrowing that flag rule. The archive's own `basis:` labels are accurate
|
||||||
|
on all 8 rows and do the disclosure work the badge tier is supposed to do. One void avenue
|
||||||
|
recorded so it is not repeated: Stackchain block numbers (1492/2079/2080) are the social chain's
|
||||||
|
own numbering, not Bitcoin heights — `mempool.space/api/block-height/1492` returns a block
|
||||||
|
from 2009-01-24, so a Bitcoin explorer cannot date them. One sub-finding left **unverified**:
|
||||||
|
row 1's three sources agree on the date and disagree on the hour (7:07 PM / 4:07 PST / 11:07 PM);
|
||||||
|
the verdict does not depend on it.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Q12 — Are the evidence tiers earned?
|
## Q12 — Are the evidence tiers earned?
|
||||||
|
|||||||
@@ -0,0 +1,173 @@
|
|||||||
|
# 2026-10-09 — merlin
|
||||||
|
|
||||||
|
**Did:** Claimed and finished **Q11 — close the eight pass-2 date mismatches**, the top
|
||||||
|
unclaimed item in `WORK-QUEUE.md` (Q1–Q10 closed or claimed; Q13/Q19 gated on Alexander;
|
||||||
|
Q11 was open and fully specified, and Timmy's `13536c1` named it as my next pick).
|
||||||
|
|
||||||
|
Deliverable: `recoveries/ledger-date-closure.md` — 8 rows, one verdict line each with the
|
||||||
|
settling source named. **Result: 8 / 8 `archive correct`, 0 `source correct`, 0
|
||||||
|
`indeterminate`, 0 `unresolved`.** Every row is settled by a dated primary or contemporaneous
|
||||||
|
source fetched live this run — all 8 entry pages and 13 cited sources HTTP 200, every file
|
||||||
|
SHA-256'd so the record is re-checkable byte-for-byte.
|
||||||
|
|
||||||
|
The finding is that the flag itself was a rule artifact. All 8 compare an entry's **event
|
||||||
|
date** against a source's **publication** date — which are supposed to differ whenever the
|
||||||
|
source is a retrospective or a standards document written after the fact. Reading each
|
||||||
|
source's body instead of its metadata resolves every row in the archive's favour, and one of
|
||||||
|
pass 2's own notes is flatly wrong: row 1's detail claims the sources *"support claims but
|
||||||
|
none bears 2022 18"*, because it read SIP-0001's `CREATED:` header and never opened the
|
||||||
|
abstract, which reads *"On July 18, 2022 at 7:07 PM, @AriZonanHODL purchased a $5 USD stack
|
||||||
|
worth of bitcoin."* Rows 2, 5, 7 and 8 repeat the pattern.
|
||||||
|
|
||||||
|
Two things worth Alexander's eye: the archive's own `basis:` labels are accurate on all 8
|
||||||
|
rows (row 3's *"repository text may include later edits"* caveat is measurably true — GitHub
|
||||||
|
shows 5 commits on `sips/sip-0004.txt` to 2022-08-09), and a void avenue is recorded so
|
||||||
|
nobody repeats it: Stackchain block numbers (1492, 2079, 2080) are the social chain's own
|
||||||
|
numbering, not Bitcoin heights — `mempool.space/api/block-height/1492` returns a block from
|
||||||
|
2009-01-24, so a Bitcoin explorer cannot date them.
|
||||||
|
|
||||||
|
**Blocked:** Nothing. One sub-finding deliberately left **unverified**: row 1's three sources
|
||||||
|
agree on the date and disagree on the hour (7:07 PM / 4:07 PST / 11:07 PM). The verdict does
|
||||||
|
not depend on it and I would not guess which rendering is right.
|
||||||
|
|
||||||
|
**Next:** Q12 — the evidence-tier audit (badge census already taken 2026-09-26: 115
|
||||||
|
`documented` / 5 `testimony` / 1 `corroborated` / 0 `unrecovered`; the item requires every
|
||||||
|
non-`documented` entry plus a stated sampling rule). Q20 (excerpt placement) is open behind
|
||||||
|
it. No new queue item opened — depth is not thin.
|
||||||
|
|
||||||
|
**Ask:** None. Two decisions that are yours, not blockers:
|
||||||
|
|
||||||
|
1. **Retire or narrow the pass-2 date flag rule** — as written it flags every event-vs-
|
||||||
|
publication-date difference, which produced 8 false positives. Narrowing it to "no source
|
||||||
|
of any kind bears the entry's date" would make it find real defects.
|
||||||
|
2. Whether `recoveries/ledger-date-closure.md` should also be surfaced to zephyrus in a
|
||||||
|
reply, or whether the queue status line I appended is enough.
|
||||||
|
|
||||||
|
— Merlin
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Crucible run 3 — 2026-10-09 (queue item Q11, claimed and finished)
|
||||||
|
|
||||||
|
**Method.** Q11 asked for one verdict line per entry with the settling source named. I stated
|
||||||
|
the resolution rule before the rows so it can be re-run and falsified: take the entry's
|
||||||
|
displayed date and its own `basis:` label, take the strongest source the entry itself cites,
|
||||||
|
search that source's **body text** for a matching date, and grade `archive correct` /
|
||||||
|
`source correct` / `indeterminate`. A block explorer counts as valid evidence only for
|
||||||
|
entries about actual Bitcoin block heights.
|
||||||
|
|
||||||
|
Measured from this host, 2026-10-09 ~09:20–09:55 UTC, `/root/crucible/q11`:
|
||||||
|
|
||||||
|
```
|
||||||
|
$ bash fetch.sh
|
||||||
|
index HTTP 200 / 34488 B
|
||||||
|
entry-01 event-2022-07-18-the-5-invitation-becomes-a-chain -> HTTP 200 4281
|
||||||
|
entry-02 event-2022-07-18-anthony-enters-at-16-names-the-hill-at-24 -> HTTP 200 3913
|
||||||
|
entry-03 event-2022-07-20-receipt-provenance-becomes-part-of-consensus -> HTTP 200 4081
|
||||||
|
entry-04 event-2022-08-18-the-bitcoin-beach-campaign-closes-and-hodlon -> HTTP 200 4397
|
||||||
|
entry-05 event-2022-08-28-the-fork-of-1492 -> HTTP 200 4380
|
||||||
|
entry-06 event-2022-10-07-gui-s-2079-and-saylor-s-2080 -> HTTP 200 4057
|
||||||
|
entry-07 event-2022-12-00-builder-relationships-cross-into-nostr -> HTTP 200 3957
|
||||||
|
entry-08 event-2024-05-20-one-community-multiple-living-chains -> HTTP 200 3727
|
||||||
|
|
||||||
|
$ bash fetch-src.sh
|
||||||
|
sip-0001 …/sips/sip-0001.txt HTTP 200 1610
|
||||||
|
sip-0004 …/sips/sip-0004.txt HTTP 200 925
|
||||||
|
github-root github.com/stackchainsats/stackchain HTTP 200 264541
|
||||||
|
bitcoinmagazine bitcoinmagazine.com/culture/how-5-bitcoin-purchase-… HTTP 200 341594
|
||||||
|
eurobitcoiners europeanbitcoiners.com/what-the-heck-is-stackchain/ HTTP 200 102858
|
||||||
|
mag-fork-1492 stackchainmagazine.net/the-fork-of-1492/ HTTP 200 139734
|
||||||
|
mag-king stackchainmagazine.net/waht-stackchain-done-dided-… HTTP 200 153199
|
||||||
|
mag-builders stackchainmagazine.net/stackchain-is-for-builders-… HTTP 200 136509
|
||||||
|
mag-two-years stackchainmagazine.net/two-years-of-stackchain/ HTTP 200 136607
|
||||||
|
x-anthony-8048 x.com/AnthonyDessauer/status/1560325688481026048 HTTP 200 110646
|
||||||
|
x-gui-3760 x.com/GuiAmadoGomes/status/1578475197211893760 HTTP 200 183500
|
||||||
|
x-saylor-0208 x.com/saylor/status/1578479561750110208 HTTP 200 173878
|
||||||
|
wayback-genesis web.archive.org/web/20220718230820/twitter.com/AriZonanHODL/status/1549169119924080640 HTTP 200 64518
|
||||||
|
|
||||||
|
# the void avenue, measured rather than assumed
|
||||||
|
$ curl -sS https://mempool.space/api/block-height/1492
|
||||||
|
000000002590c6bd1c26… # a Bitcoin block
|
||||||
|
$ curl -sS https://mempool.space/api/block/000000002590c6bd… | tr ',' '\n' | grep -m1 '"timestamp"'
|
||||||
|
"timestamp":1232763992
|
||||||
|
$ date -u -d @1232763992
|
||||||
|
2009-01-24 02:26:32 UTC # not a Stackchain date — block 1492 is Bitcoin's, not the social chain's
|
||||||
|
# block 2079 → 2009-01-28 06:06:10Z ; block 2080 → 2009-01-28 06:26:34Z
|
||||||
|
|
||||||
|
# row 3's caveat, checked in git rather than trusted
|
||||||
|
$ curl -sS "https://api.github.com/repos/stackchainsats/stackchain/commits?path=sips/sip-0004.txt&per_page=100"
|
||||||
|
5 commits; earliest 2ac1fbab 2022-07-21T02:11:47Z "initial draft"
|
||||||
|
latest c6256d0e 2022-08-09T18:33:56Z
|
||||||
|
$ curl -sS "https://api.github.com/repos/stackchainsats/stackchain/commits?path=sips/sip-0001.txt&per_page=100"
|
||||||
|
2 commits; earliest 16070f72 2022-07-20T19:23:49Z "rough draft of SIP-0001"
|
||||||
|
```
|
||||||
|
|
||||||
|
**The eight verdicts and what settled each** (full table with verbatim quotes in
|
||||||
|
`recoveries/ledger-date-closure.md` §2):
|
||||||
|
|
||||||
|
1. **entry-01 / 2022-07-18 — archive correct.** SIP-0001's abstract: *"On July 18, 2022 at
|
||||||
|
7:07 PM, @AriZonanHODL purchased a $5 USD stack worth of bitcoin."* · European Bitcoiners
|
||||||
|
(2022-07-22, four days later): *"@AriZonanHODL first posted July 18, 2022 @ 4:07 PST."* ·
|
||||||
|
Wayback `20220718230820` of the genesis tweet: *"11:07 PM · Jul 18, 2022 · Twitter for
|
||||||
|
iPhone"* with *"Even on days when I'm broke as hell I still stack. Feel free to join me."*
|
||||||
|
2. **entry-02 / 2022-07-18 — archive correct.** Cited article: *"I went back and found your
|
||||||
|
first stack at Block 16, posted on July 18, 2022, so that was very early days in the
|
||||||
|
Stackchain."*
|
||||||
|
3. **entry-03 / 2022-07-20 — archive correct.** SIP-0004: *"CREATED: 2022-7-20"*; earliest
|
||||||
|
git commit on the file 2022-07-21T02:11:47Z, i.e. one day later, exactly as the entry's
|
||||||
|
own basis label (*"repository text may include later edits"*) predicts.
|
||||||
|
4. **entry-04 / 2022-08-18 — archive correct.** Cited X post body: *"6:00 PM · Aug 18, 2022"*.
|
||||||
|
5. **entry-05 / 2022-08-28 — archive correct.** Cited retrospective: *"August 28th, 2022 late
|
||||||
|
in the morning, Stackchain block height was already 1492 when @caroghero decided to fork
|
||||||
|
the chain (& the Stackchain Legend, @sathoarder) and call #1492 his."*
|
||||||
|
6. **entry-06 / 2022-10-07 — archive correct.** Both cited posts: *"7:59 PM · Oct 7, 2022"*
|
||||||
|
(Gui) and *"8:17 PM · Oct 7, 2022"* (saylor); European Bitcoiners independently embeds
|
||||||
|
*"Block 2080 #stackchain … — Michael Saylor⚡️ (@saylor) October 7, 2022"*.
|
||||||
|
7. **entry-07 / 2022-12 — archive correct.** Cited article: *"In mid-December 2022, I tried
|
||||||
|
Nostr again."* Month precision is the honest precision; the slug's `-00` day is a
|
||||||
|
placeholder and the page renders month-only.
|
||||||
|
8. **entry-08 / 2024-05-20 — archive correct.** Cited article's own line: *"As of the date of
|
||||||
|
my writing this May 20th 2024, Stackchain has an approximate cuck-buck market cap of
|
||||||
|
18-21 million war bu…"*, against the page's `article:published_time` 2025-07-22T14:33:48Z
|
||||||
|
— both halves of the entry's basis label verified.
|
||||||
|
|
||||||
|
**Three findings, logged.**
|
||||||
|
|
||||||
|
1. **The flag was a rule artifact, and the root cause is the one Q8 found.** Every flag
|
||||||
|
compares an event date to a source publication date. Reading bodies instead of metadata
|
||||||
|
resolves all 8 for the archive, and pass 2's row-1 note (*"none bears 2022 18"*) is
|
||||||
|
demonstrably wrong. Same defect class as `magazine-040`: a judgement made on metadata
|
||||||
|
rather than content.
|
||||||
|
2. **The archive's `basis:` labels are accurate on all 8 rows** and are doing the disclosure
|
||||||
|
work Q12's badge tier is supposed to do.
|
||||||
|
3. **A void avenue, recorded.** Stackchain block numbers are the social chain's own
|
||||||
|
numbering, not Bitcoin heights; a Bitcoin block explorer returns January 2009 blocks and
|
||||||
|
cannot date them. (Bitcoin-transaction entries like entry 9's heights 749873/749880 are a
|
||||||
|
different class where the explorer is correct.)
|
||||||
|
|
||||||
|
**Evidence bar.** All 8 entry pages and 13 sources HTTP 200, every artifact SHA-256'd and
|
||||||
|
listed in `recoveries/ledger-date-closure.md` §4 with the commands. Working files at
|
||||||
|
`/root/crucible/q11/` (`fetch.sh`, `fetch-src.sh`, `extract.py`, `dates.py`, `settle.py`,
|
||||||
|
`settle2.py`, `settle3.py`, `entry-01..08.html`, `index.html`, `src/`).
|
||||||
|
|
||||||
|
**Limits.** Testimony only: the sources were fetched and hashed from this host, so the hashes
|
||||||
|
are point-in-time readings of pages that can drift. Not settled: row 1's time of day
|
||||||
|
(7:07 PM / 4:07 PST / 11:07 PM) — marked **unverified**, and the verdict does not depend on
|
||||||
|
it. Not tested: the non-date claims of the 8 entries, which are Q8/Q10's lane. Not touched:
|
||||||
|
no live page and no other party's file; `recoveries/ledger-audit-pass2.md` is unmodified and
|
||||||
|
the closure is additive.
|
||||||
|
|
||||||
|
**Landing evidence.** Files written this run:
|
||||||
|
|
||||||
|
- `recoveries/ledger-date-closure.md` (new, 16,510 B)
|
||||||
|
- `WORK-QUEUE.md` (Q11 status line appended)
|
||||||
|
- `checkins/2026-10-09-merlin.md` (this file)
|
||||||
|
|
||||||
|
```
|
||||||
|
$ sha256sum recoveries/ledger-date-closure.md
|
||||||
|
a3d022d3bb30ebc44ca2330684f4ec9ec43df7be57f991f6c61a27a4763b0857 recoveries/ledger-date-closure.md
|
||||||
|
$ wc -c recoveries/ledger-date-closure.md
|
||||||
|
16510 recoveries/ledger-date-closure.md
|
||||||
|
```
|
||||||
|
|
||||||
|
— Merlin
|
||||||
@@ -0,0 +1,268 @@
|
|||||||
|
# Q11 — Closure of the eight pass-2 date mismatches
|
||||||
|
|
||||||
|
**Item:** Q11 in `WORK-QUEUE.md`. **Claimed and finished by Merlin, 2026-10-09.**
|
||||||
|
**Finish line:** `recoveries/ledger-date-closure.md` — one line per entry, verdict
|
||||||
|
`archive correct` / `source correct` / `indeterminate`, settling source named.
|
||||||
|
Pass 2's own file (`recoveries/ledger-audit-pass2.md`) is **not edited**.
|
||||||
|
|
||||||
|
**Result: 8 / 8 resolved — all eight `archive correct`. 0 `source correct`, 0
|
||||||
|
`indeterminate`, 0 `unresolved`.**
|
||||||
|
|
||||||
|
Everything below was measured from this host on 2026-10-09, ~09:20–09:55 UTC.
|
||||||
|
All 8 entry pages and all 13 cited sources fetched **HTTP 200**. Every fetched
|
||||||
|
file is hashed so the record is re-checkable byte-for-byte.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 1. The rule this pass applies
|
||||||
|
|
||||||
|
Pass 2 flagged an entry whenever its **displayed date** differed from the
|
||||||
|
**publication date of a source it cites**. For a dated-event ledger that
|
||||||
|
comparison is structurally unsound: the entry dates the *event*, the source
|
||||||
|
dates *its own publication*. Those two things are supposed to differ whenever
|
||||||
|
the source is a retrospective, a standards document written after the fact, or
|
||||||
|
a news article about a movement.
|
||||||
|
|
||||||
|
The resolution rule, applied uniformly to all 8 rows:
|
||||||
|
|
||||||
|
1. Take the entry's displayed date and its own `basis:` label (the archive
|
||||||
|
publishes one on every dated event page).
|
||||||
|
2. Take the strongest source the entry itself cites.
|
||||||
|
3. Search that source's **body text** for a date matching the entry's displayed
|
||||||
|
date — not just the source's own publication metadata.
|
||||||
|
4. Verdict:
|
||||||
|
- **archive correct** — a cited source's body bears the entry's date (or the
|
||||||
|
source's own dated artifact, e.g. a SIP `CREATED:` line, does).
|
||||||
|
- **source correct** — no source bears the entry's date, and the only
|
||||||
|
defensible date is the source's own publication date.
|
||||||
|
- **indeterminate** — nothing settles it; `unresolved` is written plainly.
|
||||||
|
5. A block explorer is **only** valid for entries about Bitcoin block heights.
|
||||||
|
|
||||||
|
Rule stated before the rows so it can be re-run and falsified.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 2. Closure table
|
||||||
|
|
||||||
|
| # | Entry (live URL) | Displayed date | Archive's own `basis:` label | Verdict | Settling source | Settling evidence (verbatim) |
|
||||||
|
|---|---|---|---|---|---|---|
|
||||||
|
| 1 | `/stackchain/event-2022-07-18-the-5-invitation-becomes-a-chain/` | 2022-07-18 | reported event date | **archive correct** | SIP-0001 abstract (cited by the entry) + European Bitcoiners 2022-07-22 (cited) + Wayback capture `20220718230820` | SIP-0001: *"On July 18, 2022 at 7:07 PM, @AriZonanHODL purchased a $5 USD stack worth of bitcoin."* · eub: *"@AriZonanHODL first posted July 18, 2022 @ 4:07 PST."* · Wayback: *"11:07 PM · Jul 18, 2022 · Twitter for iPhone"* with *"Even on days when I'm broke as hell I still stack. Feel free to join me."* |
|
||||||
|
| 2 | `/stackchain/event-2022-07-18-anthony-enters-at-16-names-the-hill-at-24/` | 2022-07-18 | reported event date | **archive correct** | Stackchain Magazine *"…king of stackchain"* (cited; published 2025-01-13) | *"I went back and found your first stack at Block 16, posted on July 18, 2022, so that was very early days in the Stackchain."* |
|
||||||
|
| 3 | `/stackchain/event-2022-07-20-receipt-provenance-becomes-part-of-consensus/` | 2022-07-20 | document creation date; repository text may include later edits | **archive correct** | SIP-0004 (cited) header + GitHub commit history for the file | SIP-0004: *"CREATED: 2022-7-20"* · earliest commit touching the file `2ac1fbab` **2022-07-21T02:11:47Z** (repo entry one day after the header's creation date, as the basis label predicts) |
|
||||||
|
| 4 | `/stackchain/event-2022-08-18-the-bitcoin-beach-campaign-closes-and-hodlon/` | 2022-08-18 | reported event date | **archive correct** | X post `AnthonyDessauer/status/1560325688481026048` (cited by the entry) | rendered on the post body: *"6:00 PM · Aug 18, 2022"* |
|
||||||
|
| 5 | `/stackchain/event-2022-08-28-the-fork-of-1492/` | 2022-08-28 | reported event date | **archive correct** | Stackchain Magazine *"the-fork-of-1492"* (cited; published 2025-01-15) | *"August 28th, 2022 late in the morning, Stackchain block height was already 1492 when @caroghero decided to fork the chain (& the Stackchain Legend, @sathoarder) and call #1492 his."* |
|
||||||
|
| 6 | `/stackchain/event-2022-10-07-gui-s-2079-and-saylor-s-2080/` | 2022-10-07 | reported event date | **archive correct** | X post `GuiAmadoGomes/status/1578475197211893760` **and** `saylor/status/1578479561750110208` (both cited) | *"7:59 PM · Oct 7, 2022"* and *"8:17 PM · Oct 7, 2022"*, both rendered in the post bodies; the European Bitcoiners article independently embeds *"Block 2080 #stackchain … — Michael Saylor⚡️ (@saylor) October 7, 2022"* |
|
||||||
|
| 7 | `/stackchain/event-2022-12-00-builder-relationships-cross-into-nostr/` | 2022-12 | month reported in August 2023 retrospective | **archive correct** | Stackchain Magazine *"stackchain-is-for-builders…"* (cited; published 2023-08-28) | *"In mid-December 2022, I tried Nostr again."* |
|
||||||
|
| 8 | `/stackchain/event-2024-05-20-one-community-multiple-living-chains/` | 2024-05-20 | explicit internal composition date; web upload 2025-07-22 | **archive correct** | Stackchain Magazine *"two-years-of-stackchain"* (cited; `article:published_time` 2025-07-22T14:33:48Z) | *"As of the date of my writing this May 20th 2024, Stackchain has an approximate cuck-buck market cap of 18-21 million war bu…"* |
|
||||||
|
|
||||||
|
**Verdict counts: `archive correct` 8 · `source correct` 0 · `indeterminate` 0 ·
|
||||||
|
`unresolved` 0.**
|
||||||
|
|
||||||
|
No row is closed by assertion: every verdict names a quoted sentence or a dated
|
||||||
|
artifact, and every one of those was fetched live this run.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 3. Findings
|
||||||
|
|
||||||
|
### 3.1 The flag was a rule artifact, and the root cause is the same one Q8 found
|
||||||
|
|
||||||
|
All 8 flags compare an **event date** against a **source publication date**.
|
||||||
|
Reading each source's *body* rather than its metadata resolves every row in the
|
||||||
|
archive's favour. Pass 2's own detail text is wrong on row 1 — it states the
|
||||||
|
sources *"support claims but none bears 2022 18"* — because it read SIP-0001's
|
||||||
|
`CREATED:` header line and never opened the abstract, which bears
|
||||||
|
**July 18, 2022** verbatim. Rows 2, 5, 7 and 8 repeat the pattern: the note
|
||||||
|
records only the source's publication date (`13 JAN 2025`, `15 JAN 2025`,
|
||||||
|
`28 AUG 2023`, `22 JUL 2025`) and not the date the article's own prose gives the
|
||||||
|
event.
|
||||||
|
|
||||||
|
This is the same defect class Q8/Q4 identified in `magazine-040`: a judgement
|
||||||
|
made on page metadata and publication stamps rather than on content. Q3's own
|
||||||
|
method note already half-said it — *"several are event-dates vs later
|
||||||
|
retrospective publication dates; flagged per the audit rule, disclosed by the
|
||||||
|
entries' own dating labels."* The rule produced the flag; the rule is what was
|
||||||
|
wrong. **Recommended: retire this specific flag rule**, or narrow it to "no
|
||||||
|
source of any kind bears the entry's date", which is what would actually
|
||||||
|
indicate a defect.
|
||||||
|
|
||||||
|
### 3.2 The archive's `basis:` labels are accurate on all 8 rows
|
||||||
|
|
||||||
|
Every dated-event page carries a `basis:` label stating what its date is built
|
||||||
|
on, and all 8 match what the evidence shows:
|
||||||
|
|
||||||
|
- Rows 1, 2, 4, 5, 6 — *"reported event date"* — and each is corroborated by a
|
||||||
|
dated primary or contemporaneous source.
|
||||||
|
- Row 3 — *"document creation date; repository text may include later edits"* —
|
||||||
|
the caveat is **materially true and measurable**: GitHub shows **5 commits**
|
||||||
|
touching `sips/sip-0004.txt`, the latest `c6256d0e` **2022-08-09T18:33:56Z**,
|
||||||
|
so the file has been edited since its header's stated creation date.
|
||||||
|
- Row 7 — *"month reported in August 2023 retrospective"* — the source says
|
||||||
|
*"mid-December 2022"*, so month precision is the honest precision; the
|
||||||
|
`event-2022-12-00` slug's `-00` day is a placeholder and the page correctly
|
||||||
|
renders month-only.
|
||||||
|
- Row 8 — *"explicit internal composition date; web upload 2025-07-22"* — both
|
||||||
|
halves verified: the article's own line gives May 20th 2024, and the CMS
|
||||||
|
stamps the page 2025-07-22.
|
||||||
|
|
||||||
|
The labels are doing the disclosure work Q12's badge tier is supposed to do.
|
||||||
|
|
||||||
|
### 3.3 A void avenue, recorded so nobody repeats it
|
||||||
|
|
||||||
|
Rows 5 and 6 are about **Stackchain** block numbers (1492, 2079, 2080), not
|
||||||
|
Bitcoin block heights. A block explorer returns the wrong object entirely:
|
||||||
|
|
||||||
|
```
|
||||||
|
$ curl -sS https://mempool.space/api/block-height/1492
|
||||||
|
000000002590c6bd1c26… # a Bitcoin block
|
||||||
|
$ date -u -d @1232763992
|
||||||
|
2009-01-24 02:26:32 UTC
|
||||||
|
```
|
||||||
|
|
||||||
|
Block 2079 → 2009-01-28 06:06:10Z and block 2080 → 2009-01-28 06:26:34Z. These
|
||||||
|
are January 2009 Bitcoin blocks and have nothing to do with the Stackchain's
|
||||||
|
social chain, whose numbering starts at block 5 (the $5 genesis purchase) and
|
||||||
|
counts social acts, not Bitcoin heights. **Do not use a Bitcoin block explorer
|
||||||
|
to date a Stackchain block number.** Rows 5 and 6 were settled from the cited
|
||||||
|
posts and the cited retrospective instead. (Rows about *Bitcoin* transactions —
|
||||||
|
e.g. entry 9's Bitcoin Beach transfers at heights 749873/749880 — are a
|
||||||
|
different class and a block explorer is correct there.)
|
||||||
|
|
||||||
|
### 3.4 One unresolved sub-finding, recorded not buried
|
||||||
|
|
||||||
|
Row 1's three sources agree on the **date** and disagree on the **time of day**:
|
||||||
|
|
||||||
|
- SIP-0001: *"July 18, 2022 at 7:07 PM"*
|
||||||
|
- European Bitcoiners: *"first posted July 18, 2022 @ 4:07 PST"*
|
||||||
|
- Wayback capture of the tweet: *"11:07 PM · Jul 18, 2022"*
|
||||||
|
|
||||||
|
Three readings, three different clocks. The date is unaffected by any of them
|
||||||
|
and row 1's verdict does not depend on the hour. This is **unverified** — no
|
||||||
|
source available here settles which rendering is right, and the likely cause
|
||||||
|
(timezone offsets or platform re-rendering) is speculation. Flagged so the
|
||||||
|
time-of-day is not later mistaken for a settled fact.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 4. Evidence
|
||||||
|
|
||||||
|
Run from `/root/crucible/q11` on 2026-10-09.
|
||||||
|
|
||||||
|
### Entry pages — all HTTP 200
|
||||||
|
|
||||||
|
```
|
||||||
|
$ bash fetch.sh
|
||||||
|
index HTTP 200 / 34488 B
|
||||||
|
entry-01 event-2022-07-18-the-5-invitation-becomes-a-chain -> HTTP 200 4281
|
||||||
|
entry-02 event-2022-07-18-anthony-enters-at-16-names-the-hill-at-24 -> HTTP 200 3913
|
||||||
|
entry-03 event-2022-07-20-receipt-provenance-becomes-part-of-consensus-> HTTP 200 4081
|
||||||
|
entry-04 event-2022-08-18-the-bitcoin-beach-campaign-closes-and-hodlon-> HTTP 200 4397
|
||||||
|
entry-05 event-2022-08-28-the-fork-of-1492 -> HTTP 200 4380
|
||||||
|
entry-06 event-2022-10-07-gui-s-2079-and-saylor-s-2080 -> HTTP 200 4057
|
||||||
|
entry-07 event-2022-12-00-builder-relationships-cross-into-nostr -> HTTP 200 3957
|
||||||
|
entry-08 event-2024-05-20-one-community-multiple-living-chains -> HTTP 200 3727
|
||||||
|
```
|
||||||
|
|
||||||
|
### Cited sources — all HTTP 200
|
||||||
|
|
||||||
|
```
|
||||||
|
sip-0001 https://raw.githubusercontent.com/stackchainsats/stackchain/main/sips/sip-0001.txt 200 1610
|
||||||
|
sip-0004 https://raw.githubusercontent.com/stackchainsats/stackchain/main/sips/sip-0004.txt 200 925
|
||||||
|
github-root https://github.com/stackchainsats/stackchain 200 264541
|
||||||
|
bitcoinmagazine https://bitcoinmagazine.com/culture/how-5-bitcoin-purchase-cascaded-into-1-5-million-viral-movement 200 341594
|
||||||
|
eurobitcoiners https://europeanbitcoiners.com/what-the-heck-is-stackchain/ 200 102858
|
||||||
|
mag-fork-1492 https://www.stackchainmagazine.net/the-fork-of-1492/ 200 139734
|
||||||
|
mag-king https://www.stackchainmagazine.net/waht-stackchain-done-dided-the-king-of-stackchain/ 200 153199
|
||||||
|
mag-builders https://www.stackchainmagazine.net/stackchain-is-for-builders-how-building-on-stackchain-led-to-building-on-nostr/ 200 136509
|
||||||
|
mag-two-years https://www.stackchainmagazine.net/two-years-of-stackchain/ 200 136607
|
||||||
|
x-anthony-8048 https://x.com/AnthonyDessauer/status/1560325688481026048 200 110646
|
||||||
|
x-gui-3760 https://x.com/GuiAmadoGomes/status/1578475197211893760 200 183500
|
||||||
|
x-saylor-0208 https://x.com/saylor/status/1578479561750110208 200 173878
|
||||||
|
wayback-genesis https://web.archive.org/web/20220718230820/https://twitter.com/AriZonanHODL/status/1549169119924080640 200 64518
|
||||||
|
```
|
||||||
|
|
||||||
|
### SHA-256 of every fetched artifact (re-checkable)
|
||||||
|
|
||||||
|
```
|
||||||
|
f208a26cd1547f690653d63e62c06eb4d00ecbc150ef83ed0d883378c85da7b1 entry-01.html
|
||||||
|
201b7f63a52a9402415bed728a9b43ebd10c0f5fe93450dfc434502687140ddd entry-02.html
|
||||||
|
e80d0d8793bb3d5fcdc177f8da44bd719bbdfb655c564bd02e5a804dd4724d42 entry-03.html
|
||||||
|
3b3002d4d5fc827ae52a396bacf3a3415e2d6692f4f9ddb19a1df7a7933e0239 entry-04.html
|
||||||
|
a55da02af6a367082d015c148da2791d57bb2c9282e3a696aef431a60e773bf1 entry-05.html
|
||||||
|
54bd4505929b0edefac470af3a6baf61c74347b76b7d08dc9e866a844b479166 entry-06.html
|
||||||
|
5cd22cac83a5cdec21132ece9966d6959c11f90585965b3d8d0c638eb2c64eeb entry-07.html
|
||||||
|
6e569a7acd2c9d5956bf0e77a69372e523211340803b04b8bbc8c5dfd4ef617f entry-08.html
|
||||||
|
4f764ef4dfb9c08b2654ff0783550d20ad1bb7a31cb0c32070974a5fe451557e index.html
|
||||||
|
66c9a15da4e61f38d79c793f64eb0f58e1707ca3b3bf406cbe3de3d99eb214f5 src/bm.html
|
||||||
|
827cc9e7da334a1b02fbd5d39855fda1a08f6d66de5b2efedf5b744ebe02e91f src/eub.html
|
||||||
|
f6372cc6742f83220ba1afd74174041cc0d735f1e8e7ff384441f16ca81792f0 src/github-root.html
|
||||||
|
868e340849c4dcceff43017f24ae2128e2ac229a723d81ee1b2e5a4a236886b7 src/mag-builders.html
|
||||||
|
b8123b95def696c93e4f6d527ab57e81b15bff4fcb1943c2a013099a9788f5c5 src/mag-fork-1492.html
|
||||||
|
7ff55e52eafa547980279b52676e0761b90b88dca632ad9d4f5e03ea67f64952 src/mag-king.html
|
||||||
|
bbb528f37241da497b585b9f9266b2dd1049acff5bf0c6012fffc442540888a4 src/mag-two-years.html
|
||||||
|
8fb322df9e3ce1bbca989b9fb31faeea02e5cb7f0a77c980d1613b69fe252927 src/sip-0001.txt
|
||||||
|
243e859b3887a7104c9d4435f977188f476efa1ef3244d8b9e68ce8ed0eaf895 src/sip-0004.txt
|
||||||
|
5dd37f8536483dbec16c476d513b6267cefe2d5bb594ae6c244e0422a6aaa388 src/wayback-genesis-tweet.html
|
||||||
|
e7e8bb2b01750d9cf6a2ad81e228f403df02c126d7e401b53ed9c85772733009 src/x-anthony-8048.html
|
||||||
|
eb7e12da15fd88833ed8e59aa79df7c79212369ae096902c14f0162eee746e79 src/x-gui-3760.html
|
||||||
|
639348d69b02dce7cea0a298263fda36dd958d11fd87d8e45f2d1b3d0709162f src/x-saylor-0208.html
|
||||||
|
```
|
||||||
|
|
||||||
|
### Commands
|
||||||
|
|
||||||
|
```bash
|
||||||
|
# 1. entry pages + index
|
||||||
|
bash fetch.sh # → 8 × HTTP 200, sizes above
|
||||||
|
|
||||||
|
# 2. every cited source + the Wayback capture
|
||||||
|
bash fetch-src.sh # → all 200, sizes above
|
||||||
|
|
||||||
|
# 3. block-explorer control (the void avenue, §3.3)
|
||||||
|
for h in 1492 2079 2080 1414; do
|
||||||
|
curl -sS https://mempool.space/api/block-height/$h | head -c 20
|
||||||
|
bh=$(curl -sS https://mempool.space/api/block-height/$h)
|
||||||
|
curl -sS https://mempool.space/api/block/$bh | tr ',' '\n' | grep -m1 '"timestamp"'
|
||||||
|
done
|
||||||
|
# block 1492 ts 1232763992 ; 2079 ts 1233122770 ; 2080 ts 1233123994 ; 1414 ts 1232731121
|
||||||
|
date -u -d @1232763992 # 2009-01-24 02:26:32Z → not a Stackchain date
|
||||||
|
|
||||||
|
# 4. SIP git history (row 3's caveat, and row 1's)
|
||||||
|
curl -sS "https://api.github.com/repos/stackchainsats/stackchain/commits?path=sips/sip-0004.txt&per_page=100"
|
||||||
|
# 5 commits; earliest 2ac1fbab 2022-07-21T02:11:47Z "initial draft"
|
||||||
|
# latest c6256d0e 2022-08-09T18:33:56Z
|
||||||
|
curl -sS "https://api.github.com/repos/stackchainsats/stackchain/commits?path=sips/sip-0001.txt&per_page=100"
|
||||||
|
# 2 commits; earliest 16070f72 2022-07-20T19:23:49Z "rough draft of SIP-0001"
|
||||||
|
|
||||||
|
# 5. date extraction from every fetched body
|
||||||
|
python3 dates.py ; python3 settle.py ; python3 settle2.py ; python3 settle3.py
|
||||||
|
|
||||||
|
# 6. hashes
|
||||||
|
sha256sum entry-0*.html index.html src/*
|
||||||
|
```
|
||||||
|
|
||||||
|
Working files (not published, available on request): `/root/crucible/q11/` —
|
||||||
|
`fetch.sh`, `fetch-src.sh`, `extract.py`, `dates.py`, `settle.py`, `settle2.py`,
|
||||||
|
`settle3.py`, `entry-01..08.html`, `index.html`, `src/`.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 5. Limits
|
||||||
|
|
||||||
|
- **Testimony only:** the 13 sources were fetched from this host and hashed, but
|
||||||
|
the archive's *live* pages can drift; a dated-reading hash is only a
|
||||||
|
point-in-time reading. No entry page or source needed re-fetching to settle a
|
||||||
|
row this run.
|
||||||
|
- **Not settled:** row 1's time-of-day (§3.4). The date is settled; the hour is
|
||||||
|
not, and is marked **unverified**.
|
||||||
|
- **Not tested:** whether any of the 8 entries' *non-date* claims hold — that is
|
||||||
|
Q8/Q10's lane, not Q11's.
|
||||||
|
- **Not touched:** no live page, no other party's file. This file is additive;
|
||||||
|
`recoveries/ledger-audit-pass2.md` is unmodified.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
**Q11 status: DONE.** 8 rows, 8 verdicts, 0 unresolved. The item's own criterion
|
||||||
|
— "one line per entry … with the settling source named, `unresolved` written
|
||||||
|
plainly where nothing does" — is met.
|
||||||
|
|
||||||
|
— Merlin, 2026-10-09
|
||||||
Reference in new issue
Block a user