Verifying without Audrie

Every claim Audrie makes about when a record existed is checkable against a public ledger Audrie does not operate. This page is the procedure.

What you are checking

Every Audrie record is committed to Hedera Consensus Service, a public ledger Audrie cannot rewrite. The commitment proves one thing precisely: this record existed, in this form, no later than this consensus timestamp.

That is narrower than "this document is genuine". It is also arithmetic rather than assertion, which is what makes it worth having.

What you have to work with

Every match in a verification response carries an anchor block:

{
  "anchor": {
    "topicId": "0.0.4915623",
    "transactionId": "0.0.1234@1746223981.000000000",
    "sequenceNumber": 8814,
    "consensusAt": "2026-05-02T22:14:51.221Z",
    "mirrorNodeUrl": "https://mainnet-public.mirrornode.hedera.com/api/v1/transactions/0.0.1234-1746223981-000000000"
  }
}

The procedure

1. Confirm the submission reached consensus. Fetch mirrorNodeUrl directly. It resolves the transaction on a public Hedera mirror node and reports the consensus timestamp, the topic it landed on, and whether the submission succeeded.

Compare what it returns against consensusAt and topicId in the response. Hedera's timestamp is assigned by network consensus, not by Audrie.

2. Read the committed message. The transaction lookup confirms that a submission happened; it does not return the message bytes. For those, ask the topic directly, using the topicId and sequenceNumber the response gave you:

GET https://mainnet-public.mirrornode.hedera.com/api/v1/topics/0.0.4915623/messages/8814

3. Compare the message against the record Audrie reported. The commitment carries the document's SHA-256 and nothing else about it — no content, no filename, no identity. That hash is what lets you bind the ledger entry to the file in your hand.

You can substitute any mirror node you prefer, or run your own. topicId and sequenceNumber are all either step needs; the mirror node in mirrorNodeUrl is a convenience, not a dependency.

If Audrie's response and the mirror node disagree, believe the mirror node.

What this does and does not prove

Does prove: a record with these contents was committed at or before that consensus timestamp, and has not been altered since. Hedera's history is append-only and Audrie holds no privileged write to it.

Does not prove: that the person named signed willingly, that the document says what you think, or that the signer's key was uncompromised at the time.

The ledger also cannot contradict the parts of a verdict that are Audrie's own state. verdict, checksPerformed, status, revocation and signerStanding are ours to report; the anchor is what an outside party can check. Knowing which is which is the point of doing this at all.

If Audrie is gone

The anchor survives. Hedera keeps the record whether or not Audrie exists, and the mirror node network is independent of us. What you lose is the mapping from a hash to a human-readable record — so if independent long-term verifiability matters to you, retain the verification response itself alongside the document. It carries the topic id and sequence number you need.