Proof 1 of 6 · Causal order

The chain is the clock

Two devices can disagree about wall time and still produce one verifiable order. Each frame names the SHA-256 address of its predecessor; timestamps remain evidence, but they do not decide causality.

What you are looking at

Two simulated devices append records to one chain. The displayed hashes are computed by your browser, not prewritten examples.

Do this

Select Run guided sample.
Switch to wall-clock sorting.
Tamper with a predecessor link.

Watch for

Timestamp sorting moves a later frame ahead of its dependency. Chain order stays stable. Tampering then turns chain integrity red.

What this demonstrates

Dependency links preserve causal order under clock skew, and recomputation detects a changed link. It does not prove signatures, transport security, or global consensus.

Mac

--:--:--.---

Steam Deck

--:--:--.--- Deck clock offset: -17.6 seconds

Chain integrity: waiting Append at least one frame.

Ordering comparison: waiting Run the sample, then compare the two orderings.

Shared frame history

Dependency order

No frames yet.

Independent reproduction

Ask any LLM to build a separate proof

Copy this specification into another model. Compare its implementation and failure path with this page rather than asking it to endorse this page.