Skip to main content
The signature check proves a record was not altered since Klariqo signed it. The public ledger adds an independent, outside timestamp: it shows the record existed at a specific moment on a ledger that Klariqo does not run. That makes later backdating or silent replacement detectable. When a record is anchored, Klariqo stamps a fingerprint of it (a SHA-256 hash) onto Hedera, a public, council-governed ledger. The ledger message contains the fingerprint plus minimal non-content metadata, such as the schema version and a hashed record id. No transcript, phone number, name, or recording goes on the ledger.

​
What you need

An anchored record comes with an anchor receipt (a small JSON sidecar) that tells you where the fingerprint lives on the ledger. This example is synthetic. It shows the shape of an anchor receipt, not a real call or customer record. 
{
  "schema": "klariqo.hedera_anchor.v1",
  "network": "mainnet",
  "topic_id": "0.0.EXAMPLE",
  "sequence_number": "1",
  "consensus_timestamp": "1760000000.123456789",
  "vcon_sha256": "EXAMPLE_synthetic_fingerprint",
  "mirror_url": "https://mainnet.mirrornode.hedera.com/api/v1/topics/0.0.EXAMPLE/messages/1"
}

​
Verify it yourself

1

Compute the record's fingerprint

Run SHA-256 over the exact signed record file you downloaded (.vcon.json), byte for byte. Do not pretty-print, re-save, or reformat the JSON before hashing.
sha256sum record.vcon.json
This is the same fingerprint Klariqo anchored. Nothing Klariqo-specific is involved.
2

Open the public ledger entry

Open the mirror_url from the anchor receipt in any browser, or read it on the Hedera explorer. No account and no Klariqo login are required. The entry is served by Hedera, not by Klariqo.
3

Decode and compare

In the mirror node response, copy the message value. It is base64-encoded. Decode it, then read the vcon_sha256 field in the decoded JSON.
curl -s "$MIRROR_URL" | jq -r .message | base64 -d | jq -r .vcon_sha256
Confirm that this value matches the fingerprint you computed in step 1. The mirror response also includes the consensus timestamp for the ledger entry.
If the two fingerprints match, you have independently confirmed that this exact signed record matches the bytes anchored on the public ledger at the consensus timestamp shown. Change one byte of the record and the fingerprint changes, so it no longer matches.

​
What this proves

CheckWhat it tells you
Fingerprint matches the ledger entryThis exact record, unchanged, was registered on the public ledger.
Consensus timestampThe record existed no later than that moment according to Hedera consensus time.
Entry is served by Hedera, not KlariqoThe proof does not depend on trusting Klariqo.
Anchoring proves integrity and timing: that this record existed at that moment and was not altered. It does not prove a conversation took place, does not prove consent, and does not make a call lawful or make you compliant. The record itself (recording and transcript) is the evidence of content. See the evidence boundary.

Verify a vCon

Check the signature and tamper-evidence of a record.

Third-party witnessing

See how an independent witness records that a signed record existed.