Skip to content

Transparency log / checkpoint

The log's head,
signed.

Every receipt the router signs is appended to a Merkle log. A checkpoint is the signed size and root of that log; its root is anchored on Robinhood Chain every hour, so a missing or rewritten receipt shows up.

Latest checkpoint

Not published yet
The log starts with the first routed call. There is no checkpoint to serve yet, and none is invented here.

Format

A checkpoint is a short signed note in the common transparency-log style: an origin line, the tree size, the root hash, then one signature line per signer. Clients keep the last checkpoint they saw and ask for a consistency proof before trusting a newer one.

text/plain · checkpoint
verifyroute.tech/receipts/v1
<tree size, decimal>
<root hash, base64 SHA-256>

— verifyroute.tech <key id> <Ed25519 signature, base64>
  • Inclusion proof: shows one receipt is in the tree at a given size.
  • Consistency proof: shows a newer tree extends an older one without rewriting it.
  • On-chain anchor: the root is written to Robinhood Chain hourly, so the router cannot quietly fork the log.
Receipts spec Check a receipt