What is Verify?
Verify records that a document fingerprint existed at a given time and which organization registered it, without the document being stored by iBlockTechs.
When you choose a file, your browser computes its SHA-256 fingerprint and sends only that fingerprint. It changes if a single byte of the file changes; the fingerprint cannot be used to reconstruct the file.
Verify keeps a salted commitment of that fingerprint and anchors it in a registry contract on a public EVM blockchain. The document itself is not kept. Each record also gets a public verification link and a QR code.
A proof establishes registration and byte-for-byte integrity. It does not certify the truth, ownership or legal validity of a document. Issuer trust and blockchain confirmation are separate checks.
Record statuses
- Awaiting proof: the record is queued or waiting for blockchain confirmations.
- Verified: the proof is confirmed on-chain. Checking a candidate document still requires a matching fingerprint.
- Failed: the proof could not be written. Your dashboard shows it under Needs your attention.
- Revoked: your organization withdrew the record. Public checks show it as revoked.
Checking a document
Anyone with the verification link can open it and select the file they received. Verify compares it with the published proof and shows whether it matches and whether the record has been revoked.
For salted proofs, the full link carries a secret part after #s= that browsers do not send in HTTP requests. With it, the fingerprint comparison happens on the viewer’s device. Treat the full link as the key to checking the document and share it only with the people who need it. Keep it out of logs and analytics.
Older proof links may use the legacy verification flow. Always preserve the full verification URL returned when you register a document.
Revoking and erasing
Editors and admins can revoke a record, for example when a certificate is withdrawn. The public page then shows it as revoked instead of valid.
Admins can erase a salted record after its on-chain revocation is confirmed. Its stored fingerprint and salt are removed, so iBlockTechs can no longer match a document to it. Older records created before salted commitments cannot be erased. Erasure does not remove transactions already recorded on the public blockchain or copies of links already shared.