Skip to content
operating intelligence runtime · —Sign in
Menu
Sign in

verification

Proof

Every action ZERO takes is journaled, signed, and anchored. Verify it yourself — no account, no trust required.

Latest journal root

as of 2026-07-07 02:55 UTC

sha256:d8101fe475e852dd5a5a7032902f67b1581bd79eeb3cf59bb9714e02222bdc8c

public entries under this root
4
Ed25519 signature
not asserted by this feed
anchor provider
opentimestamps
anchor status
submitted to calendar · bitcoin attestation pending

an OpenTimestamps calendar holds this hash. The bitcoin attestation lands on the calendar’s schedule, not ours — pending is the expected state for a fresh root.

Signature: daily roots are signed at source; this feed does not republish the signature, so this page makes no signature claim. Verify it yourself with the steps below.

root artifactanchor artifact

Finality ledger

as of 2026-07-07 02:55 UTC
total roots
43
calendar attested
43
chain confirmed
36
awaiting bitcoin
7

Awaiting bitcoin is the normal state of a fresh root: the calendar accepts the hash first, and the public-chain attestation follows on the calendar’s schedule.

Verify it

Three requests, one terminal, under a minute. Every number on this page comes from the first one.

  1. 1 · fetch the live root index

    curl -s https://getzero.dev/api/journal-roots

    Serves the finality counts above and every public root hash. If this page and that response disagree, trust the response.

  2. 2 · fetch the root artifact

    curl -s https://getzero.dev/api/journal-roots/sha256-d8101fe475e852dd5a5a7032902f67b1581bd79eeb3cf59bb9714e02222bdc8c

    Every public entry under the root, hash-linked entry to entry — each record carries its own digest and the digest of the one before it. Recompute any of them and it must match.

  3. 3 · fetch the anchor artifact

    curl -s https://getzero.dev/api/journal-anchors/sha256-d8101fe475e852dd5a5a7032902f67b1581bd79eeb3cf59bb9714e02222bdc8c

    The timestamp receipt for the same hash. The calendar address inside it resolves on OpenTimestamps infrastructure ZERO does not control — that receipt, not this site, is the proof.

Signature check: the public MCP endpoint at /oss/mcp exposes a verify tool (zero_verify_journal_root) that checks a root hash against the stored artifact, and verifies the hash and Ed25519 signature offline when you supply the full signed root object. The open-source engine ships the same verifier.

Machine-readable