How to read a verification-suite result
Every card in the verification suite runs a published benchmark in your browser and stamps the result. This is what each line means, and how to check it yourself rather than take our word for it.
Every card in the verification suite runs a published benchmark in your browser and stamps the result. This is what each line means, and how to check it yourself rather than take our word for it.
Every card names its source. Go to the standard or manual it cites and find the worked example yourself. If you cannot find the number there, the benchmark is not anchored — that is the first thing to check on any vendor’s claim, ours included.
The suite runs the actual engine in your browser, not a recording. Run the card and watch it produce the number. Then run it again — the SHA-256 stamp should be identical, which is what proves the run reproduces.
A pass inside a wide tolerance is weaker than a pass inside a tight one. Look at how far our value is from the reference and ask whether you would accept that gap on a project you were signing.
The strongest check is independent. Take the same inputs into the software you use today and compare its answer to both numbers. Three answers that agree are worth more than any one of them.
The whole registry, with every benchmark and its source, is on the verification page. The suite that runs them live is at /verification/suite.
Open the suite, run a card, check the hash. Then put the same inputs into the tool you use today.