Every receipt says valid: true — but we compute that, so it is
our word about our own honesty. Below, your browser recomputes the hash itself. We are not
consulted.
Or open any receipt and use the link there. Try the current chain tip below.
Every receipt commits to the one before it, so the tip commits to all of them. We sign that tip with the same key that owns ASP #5262. Archive it anywhere and we can never quietly rewrite what came before it.
loading…0xce24645d29636447d736a16098b02ae473682b6f0xd652707a7c67552d629fe4d6e84d5c9c98a6dc0d8ea9a37aa216c457dea8e76eEvery receipt is covered by this checkpoint.
The signing identity committed to this hash-chain tip no later than the block timestamp. It does not establish that any receipt's own checkedAt is accurate, and it says nothing about receipts newer than the anchored sequence — those are pending on-chain timestamp proof.
The hash covers the target, the evidence, the risk, the verdict and the previous hash. Change any of them and the digest changes. Your browser checks this above.
Each hash is signed by the agent's TEE-held key. Recover the signer and it resolves to our published address — so a receipt is ours, not merely well-formed.
Each finding cites the upstream response it was read from, with a digest
of the exact bytes. While the source still returns that answer,
curl … | sha256sum reproduces it. This is the weakest link and we say so:
it binds us to our record of the answer, not the source to the answer.