Verifiable Compliance Engine
Compliance evidence
anyone can verify.
Hubz VCE anchors cryptographic evidence of compliance events on Horizen mainnet and proves compliance claims with zero-knowledge proofs verified on zkVerify. Personal data never goes on-chain.
527,442
Read from the contract on Horizen mainnet, refreshed every ten minutes.
- Network
- Horizen mainnet · chain 26514
- Contract
- EvidenceAnchor
- Address
- 0xAB258C03…FFd9E0
- Live since
- January 2025
What it does
An audit trail that doesn't depend on trusting the auditor.
Evidence anchoring
Each compliance event is reduced to a cryptographic hash and anchored by the EvidenceAnchor contract on Horizen mainnet, in batches of up to 100 events per transaction. Every record gets a sequential ID, a type, and a timestamp that anyone can query.
Zero-knowledge circuits
Circom circuits and Groth16 proofs let a claim be checked without disclosing what it is about. Only commitments and hashes reach the chain; personal data never does.
Independent verification
Proofs are verified on zkVerify, and the evidence lives on a public blockchain. Anyone can confirm a record with a standard RPC call, without an account and without trusting DataHubz.
How it works
From an event to evidence on a public blockchain.
Hubz VCE runs alongside the systems where compliance work happens. Each event produces a proof and an anchored hash, so the record can be checked later by anyone, and changed by no one.
- 01
A compliance event happens
A document is uploaded, signed, reviewed, or a security scan completes.
- 02
A commitment is formed
The event is hashed. For signatures, a Poseidon commitment binds the signer, the signature, the document, and the time.
- 03
A proof is generated
A Groth16 proof shows the claim holds, without revealing the private inputs.
- 04
The proof is verified
zkVerify checks the proof and records the verification.
- 05
The evidence is anchored
The evidence hash is anchored on Horizen mainnet, batched for efficiency, and becomes part of an immutable audit trail.
Circuits
Prove the claim. Keep the details private.
Document signature
Binds a signature to its signer, the document, and the moment it was made, through a Poseidon commitment. The proof shows the signature is valid; the signer, the signature, and the document stay private.
document_signature.circom · Groth16
Security scan
Proves a security scan met a bar without disclosing its findings, its score, or the tools that produced it.
- No critical vulnerabilities
- No high-severity vulnerabilities
- No critical and no high vulnerabilities
- Security score meets a threshold
- Full compliance: all of the above
security_scan_proof.circom · Groth16
In production
The engine behind compliance proofs in DataHubz Attest.
DataHubz Attest uses the Hubz VCE security-scan circuit for its compliance proofs. An organization can prove, for example, that a scan found no critical vulnerabilities, without handing over the scan. Each proof is verified on zkVerify mainnet and its receipt is anchored on Horizen.
No critical vulnerabilities
Proven over a private security scan
- Groth16 proof valid
- Verified on zkVerify mainnet
- Receipt anchored on Horizen
- Scan findings never disclosed
Verify it yourself
No account. No API key. Just the chain.
Every figure on this page can be checked independently against Horizen mainnet with standard tooling. The contract keeps a monotonic counter, and each record can be read back with its hash, type, submitter, and timestamp.
# total evidence records cast call 0xAB258C03CEd211cD1be12e00Ac4a7007a7FFd9E0 \ "evidenceCounter()(uint256)" \ --rpc-url https://horizen.calderachain.xyz/http # read one record cast call 0xAB258C03CEd211cD1be12e00Ac4a7007a7FFd9E0 \ "getEvidence(uint256)(bytes32,string,string,address,uint256)" 1 \ --rpc-url https://horizen.calderachain.xyz/http