This is a supplier-side artefact a commissioner can demand. It is not a receipt a citizen can use against the state. It is not a chain product.
- Leaf =
sha256(Ed25519 signature bytes) - Tree = RFC 6962 SHA-256, one slot per UTC hour
- Open slot = our log. Sealed root + public commitment = the clock.
Slot 20260827T02Z · 8 signature hashes · committed
Root f8ce0d45bcf9a34b02e7110797a5f5dc0f2c55a280d610f7bc5463f191e5085d
Bitcoin tx 7849891a92b8c31b8c68057db3386016a189bc6fcf035c39a3cde8f9ffbfb66f (in a block; ots verify after calendar 6-conf release)
Bitcoin write: 7849891a92b8c31b8c68057db3386016a189bc6fcf035c39a3cde8f9ffbfb66f (block 964237, 1 conf) — calendar OP_RETURN c40b503edd77a79f3fb1f35744193f69bc996e6e413f5f8aca551aad57d40635
Files: genesis.json · genesis.ots · sample receipt (ots verify completes after the calendar releases the Merkle path, typically 6 Bitcoin confirmations)
python scripts/verify_clock.py --genesis site/public/clock/genesis.json
Check it without this page
Leaf = sha256 of the raw 64-byte Ed25519 signature (compact JWS sig segment). Tree = RFC 6962 SHA-256. Recompute the root from genesis.json leaves; it must match the published root. Anyone holding a signature can do this without Metrecept.
python scripts/verify_clock.py --genesis site/public/clock/genesis.jsonLive slots: GET /v1/public/clock. Honesty map: GET /v1/public/honesty → proofs.merkle_clock.