WiseVerify verifier, archive build
==================================

Archive:      wiseverify-verifier-0.1.0
Site version: 0.1.0
Core:         wv-core 0.1.0 (commit a7a3c0a26a1c42627917bcf7998855ace20294d9, wasm-bindgen 0.2.128)
Core sha256:  f984e683f5c33644bef76aeae9de08c13185c3db6a212dda02f32038998c4d1f

What this is
------------
A copy of the WiseVerify verify page that runs from this folder, in your browser, with no
network and no server. It checks a sealed record with the same wv-core WebAssembly build the
website and the apps use, and it produces the same report, byte for byte.

Nothing you check here leaves this computer. There is no upload, no analytics and no request
of any kind: the page was written so that it could be read line by line and shown to make
none.

How to use it
-------------
1. Unzip this folder anywhere.
2. Open index.html in a browser. Chrome, Edge, Firefox and Safari all work.
3. Drop the record on the page: a folder, a zip, or a manifest.json with the file it seals.
4. Read the report. Every line names what was checked and what the answer was.

The other five languages are in the folders beside this file: de, es, fr, ja and zh-Hans.
Open the index.html inside one of them.

To see what a result looks like before you have a record of your own, follow "Try a sample
record" on the page. It checks the sample that travels in wv-samples.js: the same evidence
the verification core is tested against, checked here the same way your own files would be.

Checking that this copy is the one that was published
-----------------------------------------------------
SHA256SUMS lists the SHA-256 of every file here. On macOS or Linux, in this folder:

    shasum -a 256 -c SHA256SUMS

On Windows, in PowerShell:

    Get-FileHash -Algorithm SHA256 index.html

The core itself travels as base64 inside wv-core-wasm.js. Its SHA-256 before encoding is the
"Core sha256" line at the top of this file, and it is the hash wv-core publishes for the same
build in its own VERSION file. A module whose hash is not that one is not this core.

What is different from the website
----------------------------------
One thing. A page opened from a folder may not start a worker in Chrome, so the hashing runs
in the page instead of beside it. A very large file will therefore feel slower here than on
the website. The result is identical: the same core, the same calls, the same report.

What this does not do
---------------------
It does not check whether a time-stamp certificate was withdrawn later, because that would
need a network request. It does not tell you what a picture shows: a verified record proves
that the bytes are unchanged since they were sealed and that the seal is intact, not what was
in front of the camera. A certificate code on its own identifies a record; it cannot be
checked against a file you were not sent.

Contents
--------
    assets/404.Ckqr129S.css
    assets/Button.BApqK-XV.css
    assets/PageIntro.kZRJf4-b.css
    assets/VerdictPlate.327N1qko.css
    assets/_..CUzALhfG.css
    assets/styleguide.BgeY1ayV.css
    de/index.html
    es/index.html
    favicon.svg
    fonts/OFL-IBM-Plex-Mono.txt
    fonts/OFL-Source-Serif-4.txt
    fonts/README.md
    fonts/ibm-plex-mono-400-latin-ext.woff2
    fonts/ibm-plex-mono-400-latin.woff2
    fonts/ibm-plex-mono-500-latin-ext.woff2
    fonts/ibm-plex-mono-500-latin.woff2
    fonts/source-serif-4-latin-ext.woff2
    fonts/source-serif-4-latin.woff2
    fr/index.html
    index.html
    ja/index.html
    material.js
    wv-core-wasm.js
    wv-samples.js
    wv-verifier.js
    zh-Hans/index.html
    README.txt
    SHA256SUMS

Licences for the two typefaces are in fonts/. The verifier itself is published at
https://wiseverify.mrwise.ca , and wv-core's evidence format is documented there under "how it works".
