The proofs: what the chain can attest to
You will be able to name the kinds of proof this chain carries, and say for each whether it establishes a fact about the world or only about a document.
The family
Several proof types, one shape.
Beyond payments the chain carries attestations: that a file existed, that a process ran in a stated order, that an artifact came from a stated source, that a recovery path was exercised. They share a shape — a commitment, a signature over it, and a height — which is why they can be verified by the same machinery.
What a signature establishes
Who signed, and nothing beyond that.
A valid post-quantum signature says that the holder of a key authorised this exact bytes. It does not say the holder is who they claim to be, that they were entitled to authorise it, or that what they signed is accurate. Identity and entitlement live outside the chain, and a page that blurs the two is selling certainty it does not have.
Order without a clock
Heights are the only timestamp that means anything here.
Nothing in a proof depends on a wall clock. What the chain can say is that one commitment appeared before another, because one is in an earlier block. That is weaker than a notarised time and far stronger than a file date, and it is the guarantee to reason with when a process has to be shown to have happened in order.
Reading the status honestly
Each layer publishes what it actually is.
The layer pages on this site carry a status — running, pilot, proven, partial, implemented, designed — and those words are chosen by what the code does, not by the roadmap. A layer marked designed has no implementation. Read the status before you build on the promise; the menu shows it, and so does the page.
In short
- The proof types share one shape: a commitment, a signature over it, and a height.
- A signature establishes which key authorised bytes — not identity, entitlement or truth.
- Order is proved by block height; no proof here depends on a wall clock.
- Every layer publishes a status set by its code, and designed means not implemented.