Skip to content
LEXUNCreate your KeyRun a decision free
Independent verification

Check a LEXUN result without trusting LEXUN.

Every forecast the platform produces can be exported as a sealed receipt, or as a full .lexun package containing the frozen inputs, the random seed, the model version and the audit record. Paste one below and this page will check it — in your browser, using the same engine code the platform runs, with nothing sent to us or to anyone else.

Verify a receipt

A receipt is the sealed summary of one result: probability, band, input hash, seed, model version, frozen criterion and due date. Paste it and this page checks the seal and re-runs the named model at the named seed.

Verify a .lexun package

A package is the receipt plus the input figures and the decision’s audit record. Paste the whole file and all four checks below run: the seal, the inputs, the audit record and the re-run.

A matching hash shows that a file is unchanged since it was sealed. It is not a digital signature and not a trusted timestamp: it does not show who sealed the file or when, because LEXUN has no accounts and no timestamping authority. The table below says what each check proves and what it does not.

Four separate questions, answered separately. A single green tick would hide the fact that these can disagree. This page tells you which of the four passed: whether the seal matches the receipt, whether the inputs in the file are the figures the receipt was sealed over, whether the audit record is unaltered, and whether an independent re-run of the model reproduces the same number.

Paste a receipt or a package

Read locally by your browser. Not uploaded.

The sample is not a stored file — pressing “Load a live sample” runs the real runway engine in your browser right now and packages the result, so what you verify is produced by the shipping code. “Tamper with it” rewrites the sealed probability; “Change a figure” rewrites the recorded cash balance to £5 without touching the seal, which is the edit the seal alone cannot see.

What each check actually proves

CheckProvesDoes not prove
SealThe receipt body matches the hash that was sealed with it. One changed digit in that body — the probability, the band, the input hash, the seed, the model version, the frozen criterion, the due date — changes the SHA-256 hash.Anything outside the receipt body. The input values travel in the package, not in the receipt, and the seal covers only their hash — which is why the next check exists. Nor when it was written, or who wrote it: there is no timestamping authority and no signature, because there are no accounts.
InputsThe input values in the package hash to the input hash sealed in the receipt, so they are the figures the forecast was actually made from. The hash is computed over the canonical form of each figure, so a value that merely passed through a system which quotes numbers ("120000" for 120000) still matches; a value that was changed does not.That the figures were true. A fact is what a statement shows; the package records which fields the person classified as facts and which as assumptions, and this page cannot check either against the world.
Audit recordEach event in the record still carries its original contents, and in the full record on the device each event is chained to the one before it by hash, so no entry can be quietly altered in the middle.That nothing was ever deleted. A hash chain cannot prove the absence of something that was removed from the end, and the owner of the device can always start a fresh record.
Independent re-runThe recorded calculation reproduces exactly. Your browser runs the named model at the named seed over the frozen inputs and reaches the same probability, digit for digit.That the inputs were true. The model is reproducible; the assumptions fed into it are the user's, and the package labels which fields were facts and which were assumptions.

Why this page exists

An accuracy figure that cannot be checked gives its reader nothing to verify; a method that can be checked does. LEXUN publishes the method and, until ten outcomes have resolved in a domain, no accuracy figure at all. So the verification is not a diagram of a process we run internally — it is this page, running on your machine, on a file you hold.

The honest limits are stated above and repeated in the receipt itself. It is a content hash and an audit chain: tamper-evident, not tamper-proof. That distinction matters, so we print it rather than hiding behind the word "cryptographic". More on the whole approach on the defensibility page, the Trust Centre and the reproduction guide.