Skip to contentThe claims register is public. 27 verified, 7 struck.

Check the record. Not our word.

If the only way to check evidence is to ask whoever produced it, it proves nothing. Admissible's records verify offline, without access to our systems. Hand one to a third party and it verifies with Admissible absent.

Verifier readoutillustrative
input
one evidence pack, sealed
network
none — the check runs offline
record 07
PASS — matches the seal it was sealed under
record 07*
FAIL — altered copy; the seal does not match
answer
pass or fail — nothing in between
Illustrative. The shipped verifier prints its own. The starred row is the same record with one field changed.

The receipt

What a receipt is. What was proposed, what the kernel answered, and the seal that binds the two.

Sealed at the decision

Every governed action is sealed in a signed, tamper-evident record. That record is the receipt. A refused action is recorded with the reason it was refused. An allowed one carries its seal all the same.

Tamper-evident means exactly that

Alter a sealed record, one field, one character, and it stops verifying. The receipt does not argue with you. It either matches its seal or it does not.

The flow

Three steps. None of them involves us.

A reader counting to three and not finding our name in any of them is the argument. If we disappeared tomorrow, the answer would not change.

Step 1Your file

Load the record

You hold the record you were given: a single receipt, or a period’s evidence pack. It travels as a file. There is no account to open and no portal to log in to.

Step 2Your machine

Run the verifier

The verifier runs on your machine. It needs no access to our systems — pull the network cable first if you like. It checks the record against the published public key and answers.

Step 3Any third party

Read the answer

Pass or fail. The evidence a period produces can be handed to a third party — an auditor, a counterparty, a regulator — and verified with Admissible absent.

If we disappeared tomorrow, the answer would not change.

Scope

What a pass means. And what it does not.

Verified

A pass means

The record in front of you is the record that was sealed, unaltered, signed under the key it claims. The verdict it reports is the verdict that was given.

And because the checks are deterministic, same input, same verdict, every time, the record describes a decision that would come out the same way if you replayed it.

Not a judgement

A pass does not mean

That the rules the kernel enforced were the right rules for your obligations, or that the action was lawful, fair, or wise.

A receipt is evidence of what happened, not a judgement about it.

At launch

The verifier and the demo public key publish here. Until then this page carries no upload form and no verification widget.

A form that pretended to verify would be the opposite of the point. When the tool is here, it will be the real one, and the note on this page will change to say so.

What is demonstrated
At launch

The verifier

A small, self-contained program you download once and run locally. Every receipt the sandbox issues will verify against it, on your machine.

At launch

The demo public key

Sandbox receipts are signed under it. It publishes here beside the verifier, and nowhere else first.

Receipts to verify

The sandbox issues signed receipts against synthetic packs. Bring one back here.

Get them from the sandbox

The wider layer

What a record carries, and whose desk it lands on.

How records are made

Start here

Want a record of your own to check?

The sandbox issues signed receipts against synthetic packs. Bring one back here and verify it yourself.