Verification Process
Verification is the mathematical proof that a file has not changed by a single bit since it was sealed. It consists of Integrity Checks (Hashing) and Authenticity Checks (Signatures).
Cross-Platform Interoperability
Our hashing algorithm (BLAKE3-Merkle) is deterministic. You can seal a file on the Web App and verify it using the Python CLI (and vice versa). The generated Root Hash will always be identical for the same file byte-stream.
The Verification Pipeline
1. Fingerprint Generation
The verifier (Web App or CLI) reads the file stream locally and calculates the Merkle Root Hash.
Privacy Note: The file itself is NEVER uploaded. Only this 32-byte hash is sent to the server.
2. Query Ledger
The system queries the BitSeal Global Ledger for the exact operational history of this hash.
3. Cryptographic Validation
The client independently verifies the Ed25519 Signature returned by the ledger to ensure the record wasn't forged.
Troubleshooting & Errors
| Error | Cause | Resolution |
|---|---|---|
| HASH_MISMATCH | File altered | Even a single bit change (e.g. metadata save) alters the hash. Locate the exact original file. |
| RECORD_NOT_FOUND | Not sealed yet | The file hash does not exist in the ledger. Please seal the document first. |
| SIG_INVALID | Forgery Attempt | Security Alert. The record exists but was not signed by our key. |
| STATUS_REVOKED | Asset Revoked | If the status is "Revoked," the asset has been explicitly flagged as unsafe or invalid by the BitSeal Authority. |
Understanding Entropy
BitSeal calculates the Shannon Entropy of every file (0.00 - 8.00 bits/byte) to detect its structural density.
Low Entropy (0.0 - 5.0)
Indicates plain text, HTML, source code, or highly structured data.
High Entropy (7.5 - 8.0)
Indicates compressed data (ZIP, Images) or Encrypted content.