One link, checked in your browser.
No account, no signup, nothing to install. The check runs the moment the record opens, and you can run it again on your own computer without PacSpace or the lab.
From the link to a check you can repeat.
The lab sends one link and a code, by separate channels.
The link opens the record the lab chose to share. Nothing about the lab's systems comes with it.
The check runs the moment the record opens.
Your browser checks every entry against the seal it was committed with.
What the lab revealed you see in full.
What it withheld you see counted, never shown.
Change one character of your copy, or drop an entry from it, and the change shows.
Check it again on your own computer.
Our open-source checker runs without PacSpace: npx @pacspace-io/check history.json
Ask for more fields if you need them.
The lab reveals them in a new link, or in a file built from the record, and each field is checked against its entry's seal.
Record that you checked, only if you choose to.
It writes a record of its own, under the name the lab gave your link, saying which entries you checked and whether they matched. The check never needs it.
Keep a copy.
One file of the seals and the fields revealed to you. The open-source checker checks it later on any computer, without the link and without PacSpace.
What you can rely on, and what you can't.
The check shows each seal was committed and that all of them are here, in order, and that each shown field is in its entry's seal. It does not show what a field that is not shown says, or that what was recorded was true.
The lab still chooses what to write, the same limit every log has. What it gives up is changing the record afterward. A gap in the record is as telling as a change: the records on either side put a start and an end on it.
Don't trust us, trust the math. The verification survives the company.
The seals are committed to the proof layer, infrastructure no party controls, PacSpace included.
The checker is open source and checks a record without asking us or anyone else. If PacSpace went away tomorrow, yesterday's records would still check.
We're an evaluator. What do we need to check a record?
The link and its code, and nothing else. No account, no signup, nothing to install. The check runs in your browser the moment the record opens, and you can run it again on your own computer with our open-source checker, which works without PacSpace.
Can an evaluator see what the lab didn't reveal?
No. Fields the lab doesn't reveal can't be seen or guessed from the record. The evaluator sees how many were withheld, and checks every revealed field against the seal its entry was committed with. Withholding a field doesn't change what was committed: every entry's seal still checks, revealed or not.
Can we check a record without going through PacSpace?
Yes. Opening a shared record in a browser is the easy way, and that page is served by us, so a careful reader shouldn't have to stop there. The operator can download a record's history file and hand it to you. A checker we publish on npm, under an open license, runs on your own machine, reads what was committed directly from the source, and compares it with the file. Neither PacSpace nor the operator is involved while that check runs, and you can read the checker's code to see what it computes.
What is under the hood? How does checking actually work?
What the record gives you, we will explain to anyone: entries committed at the time, not changeable after commit, checkable by anyone holding a copy, and seals that outlast us. How it is built is a conversation we have with your engineers when you evaluate it. And you don't have to take the check on faith: the checker we publish is code you can read, and it shows what a check computes and what it compares. You don't need the mechanism to test the claim.
Bring the case you think breaks it.
We would rather be evaluated by use than by description. Talk to us and we'll put you in a live environment: commit a record, do your best to change it, then check it yourself, with us out of the loop. The change shows.
The record must exist.