Audit Chain Verification
Publicly verify the integrity of all VeriBureau data.
What is the audit chain?
Every event in VeriBureau — every review, business response, dispute, token generation, and score recalculation — is recorded in a cryptographic chain. Each record contains a SHA-256 hash of the previous record. If any record were altered, deleted, or reordered, the hash chain would break.
This means that even VeriBureau operators cannot tamper with historical data without the tampering being publicly detectable. You can verify this yourself by clicking the button below.
Verify now
Chain intact. No tampering detected.
How it works
1. Every event creates a new record with a SHA-256 hash
2. Each record’s hash includes the previous record’s hash
3. This creates a chain: Record₁ → Record₂ → Record₃ → ...
4. Changing any past record would change its hash
5. All subsequent hashes would then be wrong
6. The verification process re-computes every hash from scratch
7. If all hashes match → chain is intact → no tampering
API access
You can also verify programmatically:
GET https://veribureau.net/api/v1/audit/verifyReturns JSON with chain validity, total records, and root hash.
DNS anchoring
The current chain head hash is periodically published as a DNS TXT record on_audit.veribureau.com. This creates an external witness that cannot be controlled retroactively — even if we wanted to rewrite history, the DNS record proves what the chain state was at that point in time.
Verify the anchor yourself:
dig TXT _audit.veribureau.comOr fetch the current anchor via API:
curl https://veribureau.net/api/v1/audit/anchorVerify anchor matches chain (live):
curl https://veribureau.net/api/v1/audit/anchor/verifyVerify without trusting us
Download the complete audit chain, disconnect from the internet, and verify locally. If we tampered with anything, you will detect it. Zero trust required.
Step 1: Download the chain
curl https://veribureau.net/api/v1/audit/chain -o chain.jsonStep 2: Disconnect from the internet
Turn off WiFi. Unplug ethernet. Airplane mode. This step is the point.
Step 3: Run the verifier
python3 verify.py chain.jsonor: node verify.js chain.json
The verifier scripts use only standard library functions. No external dependencies. No network calls. The chain format is documented JSON — you can write your own verifier in any language. The algorithm is: each record's previousHash equals SHA-256(id + ":" + dataHash + ":" + previousHash) of the preceding record. First record's previousHash is the genesis hash (64 zeros).