What HardState proves
A timestamp proves one thing: a fingerprint existed before a certain Bitcoin block. That is useful, and HardState uses it. OpenTimestamps is one of the two ways our records reach Bitcoin. On its own, though, a timestamp cannot say who signed, whether they were allowed to, whether anything is missing, or whether something never happened.
HardState answers those questions, and anyone can check every answer in a browser against public Bitcoin explorers, without trusting the institution or us.
Beyond a timestamp
Section titled “Beyond a timestamp”| What you need to know | A timestamp alone | HardState |
|---|---|---|
| Did it exist at that time? | Yes: the fingerprint existed before a block | Yes, through two independent roads to Bitcoin |
| Who signed it? | No | The official’s passkey or session, named by public code, title and department, never by personal name |
| Were they allowed to? | No | The institution’s own log authorized that key for that kind of step, at that moment |
| Is anything missing? | No | The record is chained to every earlier one, and an AI system’s heartbeat vouches for every record it sent, so a gap shows |
| Did something not happen? | No | A Proof of Absence: no human review of this decision, no revocation of this key, or no record of this document existed as of a given entry, anchored on Bitcoin |
| What did an AI agent do? | No | The decision and every step of the agent’s run are sealed, and an evidence package rebuilds the process step by step without publishing its contents |
| Did a person review it? | No | The review is signed with the reviewer’s own key; an AI system’s key cannot sign one |
| Is this the real verification page? | No | The verifier draws a seal from the Bitcoin block itself, which a fake “verified” page cannot reproduce |
| Can the citizen check it alone? | Only with the fingerprint and a separate tool | The receipt and QR open a check that runs in the citizen’s browser, with no need to download the institution’s whole log |
The model
Section titled “The model”HardState applies to institutions and AI systems a model the web already trusts for its certificates: public, append-only logs that anyone can audit (Certificate Transparency), and software signing anchored in public logs (Sigstore). We add three things those systems do not have:
- anchoring in Bitcoin;
- proofs that something is absent;
- proofs that a stream of records is complete.
Rolling out next
Section titled “Rolling out next”- Peer witnesses. Institutions countersign one another’s logs, so a rewritten or forked history is caught within minutes. The witnesses are chosen at random from a Bitcoin block, so nobody can pick friendly ones.
- Consistency proofs. A few kilobytes prove that today’s log extends yesterday’s exactly, with nothing removed, however many millions of entries it holds.
HardState is a Zevlat Intelligence venture. © 2026 Zevlat Intelligence.