Every record on ProofChain is signed, hashed, and anchored to public blockchains.

You don't need a wallet, a browser plug-in, or any crypto knowledge to use ProofChain. But when it matters — a $2M sale, an insurance dispute, a warranty claim — every event we display can be cryptographically proven back to a public Bitcoin transaction.

Step 1

Event fingerprint

Every renovation, inspection, permit or claim is serialized into canonical JSON and hashed with SHA-256.

H(evt) = SHA-256('pcv1:evt:' + canonicalJSON)

Step 2

Property Merkle root

All event hashes for one home are combined into a Merkle tree. The 32-byte root is the property's tamper-evident summary.

root = merkle([h₁, h₂, … hₙ])

Step 3

Weekly batch root

Every 7 days we compute a Merkle-of-Merkles across every updated property in that window.

batchRoot = merkle([rootA, rootB, …])

Step 4

On-chain commitment

The batch root is written to Bitcoin (OP_RETURN) and Ethereum (calldata to the ProofChain registrar).

OP_RETURN 0x504301 <batchRoot>

Why not put everything on-chain?

Blockchain-anchored, not blockchain-native.

Writing every permit photo directly to a public chain would be slow, expensive, and would leak private data (invoice amounts, home addresses, contractor identities). Instead, we keep records in a fast, private database and publish a single cryptographic fingerprint — the batch Merkle root — to Bitcoin and Ethereum every week. That's the same approach used by Cloudflare's Time Machine, ProofOfExistence, and CertiK for the same reasons.

✓ Cheap: one BTC + one ETH tx per week covers unlimited events
✓ Private: the chain sees only a 32-byte root, never your data
✓ Portable: any auditor can rebuild the root offline and verify
✓ Irreversible: once anchored, tampering would break the Merkle chain

Try it now

Verify any hash from a sample property

Pick a property, open any event, and click its hash chip to see the full Merkle inclusion proof and the on-chain commitment.

Open a sample home