Understand how Bernstein creates and verifies blockchain certificates using cryptographic proofs
Bernstein certificates leverage the Bitcoin blockchain to create cryptographic proof of existence, integrity, and ownership for your digital assets.
The blockchain stores a Cryptographic fingerprint (hash) of your files - never the actual files or clear-text data. Private keys are also never stored on the blockchain.
Hash each file individually with SHA-256 using sha256sum -b filename . Then sort all hashes alphabetically, concatenate them, and compute a final SHA-256 hash.
Convert the HEX hash to WIF (Wallet Import Format). This creates a valid Bitcoin private key from your project fingerprint.
Use a Bitcoin key compression tool to derive the compressed public key from the WIF private key created in Step 2.
Combine three public keys (Owner, Data, Bernstein) into a 3-of-3 MultiSig address using Bitcoin scripting (P2WSH for SegWit or P2SH for legacy).
Search for the Transaction ID from your certificate on a blockchain explorer. Find the MultiSig address in the transaction outputs and compare it with your computed address. Match = Verification successful .
| Tool | Purpose |
|---|---|
| Bernstein Validator | Official verification app (this tool) |
| File Hash Tool | SHA-256 file hashing |
| Key Compression Tool | Derive public key from private key |
| Blockchair Explorer | View Bitcoin transactions |
| Issue | Cause | Solution |
|---|---|---|
| Hash mismatch | File was modified | Use exact original file |
| Address mismatch | Wrong protocol version | Try both P2SH and P2WSH |
| Key derivation fails | Wrong hash format | Ensure lowercase HEX |
| Transaction not found | Wrong network | Use mainnet explorer |