How BoC works
- Hash. Your file is fingerprinted with SHA-256 in your browser. The fingerprint uniquely identifies the exact bytes; the file itself stays private unless you choose to store it.
- Anchor. The fingerprint is time-stamped and recorded — by the BoC notary and, when configured, directly on Bitcoin and Ethereum. This proves the file existed in that exact form at that time.
- Custody. Every action (creation, transfer, examination, release) is written to a hash-chained log that can't be altered after the fact without detection.
- Prove. Export a printable custody certificate or a self-contained proof bundle. Anyone can verify a record independently — even without a BoC account.
What a proof shows
A confirmed anchor proves a specific fingerprint existed at or before a specific time, and (via ownership transfers) who controlled it. To prove the content, keep the original file: re-hashing it must reproduce the notarized fingerprint.