Verify
Drop the file or the bundle you were sent and read the result. The check runs in this page, on your device.
Records, bundles, ledgers, sidecars, .wvshare files and zips of them. What can I check?
Accepted: a record's manifest.json with the file it sealed, an export bundle, a locker ledger, a pair sidecar, a .wvshare container, or a zip of any of those. A folder keeps the files beside each other, which is how a bundle proves it is complete. How this check works
Drop files here
Hashing on this device
Each file is read in one megabyte pieces and hashed as it goes, so a four gigabyte video never has to fit in memory.
- Reading
- Read so far
- Rate
- Hashing progress
Result
Not proved here.
Something a verdict needs was not supplied, so nothing is claimed either way.
A verified result proves that these exact bytes were sealed by the key shown and have not changed since. It does not prove what the picture shows, or who held the device.
Checks
Trusted time stamp
A time stamp proves that this content hash existed at the time shown. It says nothing about the content, the device or the person.
Revocation was not checked. This verifier has no network access.
Encrypted share
Nothing below is authenticated yet. The header is text the sender wrote, and it is shown so you know what you were handed.
The payload is an Apple Archive (aar1). It cannot be unpacked in a browser. Download it, unpack it on an Apple device, and drop the files here.
Files read
This check
What this receipt is, and is not
What this receipt is, and is not
This receipt records a verification performed in a web browser by the WiseVerify verifier at wiseverify.mrwise.ca. Every check listed above was computed on this device from the files named above. Nothing was uploaded. The receipt is not signed by anyone. It is a record of a reproducible process, and anyone holding the same files can repeat it and obtain the same report, byte for byte, with the archived verifier or with the open verification core.
How the fields relate to evidence rules
The wording below describes where each field may be relevant. It is not legal advice, and whether a record is admitted is always a decision for the court.
United States, Federal Rules of Evidence 902(13) and 902(14). Rule 902(14) allows data copied from an electronic device, storage medium or file to be self-authenticating when authenticated by a process of digital identification, as shown by a certification of a qualified person. Rule 902(13) does the same for a record generated by an electronic process or system that produces an accurate result, shown by a certification in the same way. This receipt is neither certification. It supplies the material a qualified person may rely on when making one: the hash algorithm (SHA-256), the hash value of each file, the signature algorithm (ECDSA P-256) and public key that sealed the record, the time-stamp authority and the time it asserted, and the version of the verification core that produced the report.
Both subsections also require the proponent to meet the notice and opportunity-to-inspect procedure of Rule 902(11). That is a step for counsel, not something a receipt can satisfy on its own.
Canada, Canada Evidence Act sections 31.1 to 31.3. The party tendering an electronic document must prove its authenticity, and the best evidence rule may be satisfied by proof of the integrity of the electronic documents system. The content hash comparison speaks to whether these bytes are the bytes that were sealed. The signature and the time stamp speak to the system that sealed them and to when. The integrity of the capturing device and of the storage between capture and this check remain matters for the party to establish.
What a verified result proves, and what it does not
A verified result proves that these exact bytes were sealed by the key shown, that the sealed metadata has not changed since, and, where a time stamp is present, that a time-stamp authority attested the content hash existed at the stated time. It does not prove who held the device, what the picture shows, or that the scene was real. Revocation of time-stamp certificates was not checked; the verifier has no network access to check it.
Certificate
A certificate, not a verdict.
This link identifies a record. It does not verify one: a QR code does not carry the signing digest, so the signature cannot be rechecked from it alone. Drop the record's files to check them.