CHAIN HEAD · EPOCH {{ headEpochFmt }} VERIFIED IN THIS TAB

sha256 chain root · recomputed, not reported · every receipt since genesis chains to this value

REF_SPOT · REFERENCE READING

{{ spotBig }} {{ deltaFmt }} last 32 min

ref_spot ref_ewma_fast ref_ewma_slow

WAD strings are the data; this chart is display. Withheld epochs render as gaps, never zeros.

HEARTBEAT · WALL-CLOCK TRUTH

UNBROKEN FOR{{ unbroken }}

NEWEST RECEIPT{{ lastPub }}

NEXT EPOCH{{ nextIn }}

EXPORT | CHECK{{ exportStr }}

LIVE VERIFICATION NEVER STOPS

epoch{{ l.epochFmt }}receipt OKlink OK

ANCHOR CHAIN · ROOTS COMMITTED INTO BITCOIN BLOCKS ALL {{ tickAnchors }} ANCHORS →

MATURING next anchor 3 calendars committed
awaiting bitcoin attestation

BITCOIN TIP

BLOCK{{ a.age }} ago

{{ a.block }} epochs {{ a.range }}

{{ a.rootPfx }}…PROVEN

Rewriting this history now means rewriting Bitcoin. The only forgeable history is a future one; the accrued past is the moat.

LATEST RECEIPTS · VERIFIED ON ARRIVAL FULL TIMELINE →

EPOCHUTCREF_SPOTROOTSTATUS

{{ r.epochFmt }} {{ r.time }} {{ r.spotFmt }} {{ r.rootPfx }}… {{ r.stText }}

Open any receipt to climb its proof ladder: integrity → continuity → recomputation → anchor → full replay.

READINGS · RECOMPUTED SERIES ALL →

1e18 WAD · content-addressed program

Each series is re-derived in this tab by the reference implementation, state threaded from genesis. Nothing here is quoted from anyone.

DAILY SEGMENTS · A DAY IS IMMUTABLE ONCE COMPLETE

UTC DAYEPOCHSRECORDSSEGMENT SHA256LOADEDX-RAY

{{ d.date }}{{ d.range }}{{ d.records }}{{ d.sha }}…{{ d.loaded }}{{ d.bytes }}

a day is immutable once complete; today's partial re-shards each export and its predecessor is pruned (the manifest chain records every state).

{{ rf.id }}latest {{ rf.latest }} · WAD strings are the data, this chart is display

withheld epochs render as gaps, never zeros.

{{ receiptsTotal }}RECEIPTS RECORDED

743ANCHORS COMMITTED

741BITCOIN-PROVEN

2026-06-28UNBROKEN SINCE

{{ receiptsTotal }}REPLAYED IN THIS TAB

32DAILY SEGMENTS

Deliberately absent

visitor counts, country maps, "verified by N people," mirror totals without signed attestations. This site has no analytics and therefore cannot know those numbers; every figure above is derivable from public artifacts, and several impressive-sounding statistics are absent rather than invented. Mirror and verifier attestations render here when the standing ledger publishes them; until then this section stays quiet on purpose.

ANCHORSEVIDENCE

EPOCHROOTCALENDARSBITCOIN.OTS

{{ ar.epoch }}{{ ar.root }}…3 committed{{ ar.btc }}download

BITCOIN ATTESTATIONSEVIDENCE

BITCOIN BLOCKATTESTS ROOT OF EPOCHTIMESTAMP (UTC)ROOT

{{ br.block }}{{ br.epoch }} {{ br.gen }}{{ br.ts }}{{ br.root }}…

block-header confirmation is the CLI path (anchor-verify); any explorer link would be informative only, and none is required.

NIGHTLY FULL REPLAYPUBLISHER ATTESTATION, INFORMATIVE

the operator's machine re-derives the entire history every night; a red line here is the system catching itself. Independent proof is the same command on your machine: node verify.mjs config.json

RUN (UTC)VERDICTRECORDSHEAD EPOCHROOTTOOK

{{ rr.run }}OK{{ rr.records }}{{ rr.head }}{{ rr.root }}…{{ rr.took }}

VERIFICATION LEDGEREVIDENCE

one dated line per audit run on the recorder host; the frontier only ever moves forward:

{{ p.id }}v1.0.0 · CONTENT-ADDRESSED

{{ p.json }}

the file bytes are exactly the hashed preimage; verification is byte equality, and the dependency walk (program to reading to parameters) grows with the catalog.

every 60th link of {{ receiptsTotal }}; a break would render red here, and the replay says: UNBROKEN

EPOCHPREVROOT → ROOTLINK

{{ ro.epoch }}{{ ro.link }}OK

no match in the loaded prefix

FIELDA → BDELTA

TIME MACHINEMANIFEST CHAIN

Walks prevManifestHash backwards (served mode) and renders the head as it was: no future exists in that view. Complete past days resolve exactly; a then-current partial segment may have been pruned and says so.

PRESS RELEASESEVERY CLAIM IS A MERKLE LEAF

RELEASECLAIMSROOTANCHOREDCREATED (UTC)

{{ pr.title }}{{ pr.claims }}{{ pr.root }}…YES{{ pr.created }}

a claim is either evidence-backed or it is not published; there is no confidence field anywhere in this system.

Things we cannot fake

Bitcoin timestampsroots committed into blocks (genesis: block 955,756); rewriting them means rewriting Bitcoinproof

Historical rootseach chains to the last; one changed byte anywhere breaks every root after itproof

Receipt hashesrecomputed in your tab from the logged bodiesproof

Program identitycontent-addressed; the file bytes are the hashed preimageproof

The outputsre-derived by the reference implementation running in this pageproof

What could be faked without anchoring, and why it cannot be now

A publisher can fabricate an internally consistent history at any time; that is level 1 and 2's honest residual. What it cannot do is fabricate one that existed in the past: the Bitcoin attestations pin each root to a block time, so the only forgeable history is a future one, and the accrued past is the moat. The observation caveat remains and is stated rather than hidden: a timestamp proves when, recomputation proves what follows from the logged inputs, and re-observation (archive access) closes the last gap.