The auditor does not have to take our word for it
Proof comes from systems, Excel files, PDFs and emails. But when did it exist, and has it changed since? With Vidimus, the auditor opens the verification and recomputes the proof themselves.
For the court-appointed expert, the auditor and the counterparty's IT department. Everything below works without an account and without our software, and offline except for one step: for Bitcoin, you look up one block in a public block explorer. You only need the evidence bundle, and you get it from the customer, not from us. Prefer DSS, the European Commission's software?
Only a mathematical anchor is public; with it, anyone can check whether your logbook was rewritten afterwards. Who you are, what you record and with whom stays within your organisation and with the people you give a link to yourself.
Proof comes from systems, Excel files, PDFs and emails. But when did it exist, and has it changed since? With Vidimus, the auditor opens the verification and recomputes the proof themselves.
For a court or a counterparty that prefers not to use Vidimus software. DSS is software from the European Commission; the online version is a demo environment, not an official verification. GLOBALTRUST's granted status on the EU trusted list is set by the Austrian supervisory body, not by the Commission and not by Vidimus. Every evidence bundle contains an Evidence Record (bewijs.ers, RFC 4998): the international standard for "this existed at time T and has not changed since". You check that file with the European Commission's tool or with the one from the German BSI.
bewijs.ers and vingerafdruk-invoer.json (Dutch for "fingerprint input": the exact content that was hashed, with the SHA-256 of every attachment in it).bewijs.ers. Under Original file(s): choose vingerafdruk-invoer.json. If the content is sensitive, choose to send only the digest (SHA-256): then only the fingerprint leaves your computer.organisatie.mandaat_eid.pdf_sha256) and is itself anchored. The PDF is not in the bundle, because the eID certificate contains the administrator's national register number (the Belgian personal identification number).sha256sum attachments/<name> gives a value that appears in vingerafdruk-invoer.json. That way, the photos and PDFs are tied to the same recomputed proof.Tested on 27 September 2026 with DSS 6.5 from the European Commission, on a record of Vidimus itself: Evidence Record PASSED, timestamp QTSA (GLOBALTRUST, Austria), the first hash list contains only the submitted document. Want to try it without a record of your own? The two files of a public demo record (29/09/2026, same outcome) are on the Technology page.
Offline: download the Commission's standalone application, start it on your own computer and follow the same steps; your files stay with you. Online too, the SHA-256 option sends only the fingerprint: the browser calculates it, the file itself does not leave your computer. BSI: the ER Verify Tool (TR-ESOR) is intended for experts; it requires Java 11 and a configured timestamp check, and then runs with checktool -conf config.xml -data vingerafdruk-invoer.json -er bewijs.ers. What this does not cover: who signed, and the Bitcoin anchoring; those are in step 3 below. For logbooks with personal data, the record's salt is already in vingerafdruk-invoer.json: the route works there too. Only records with personal data from before 28 September 2026 (HMAC) are checked with the steps below.
pip install cryptography rfc3161ng opentimestamps-client and then python3 verify_bundle.py bundel.zip. Without the last two packages, timestamp and Bitcoin stay at null; the Bitcoin proof follows the open standard of OpenTimestamps. For each check you get true, false or null (cannot be checked in this environment, with the reason).sha256sum. Build {"canon":"vidimus-json-2","org":"<organisation identifier>","payload":…,"attachments":{name:sha256,…}} canonically (keys sorted, no whitespace) and take its SHA-256. That is the fingerprint in the manifest. The organisation identifier is in the manifest (registration.org_kenmerk) and as serialNumber in signer-cert.pem: each fingerprint is thus bound to one identified company. Records from before 26 September 2026 carry canon vidimus-json-1, without an org field; the script knows both. Attachments count by name; the upload order does not matter. Shorter: sha256sum vingerafdruk-invoer.json gives the same fingerprint, because that file is exactly this object.salt: the secret salt of this one record (disclosure.salt in the manifest), so that nobody can guess names or numbers by hashing them themselves. Over that object you take plain SHA-256, and here too sha256sum vingerafdruk-invoer.json is the fingerprint. The salt says nothing about other records. Older records from such logbooks (hash_type hmac-sha256) use HMAC-SHA256 with the salt as the key, over the object without the salt field; the script knows both.openssl ts -reply -token_in -in tijdstempel.tsr -text shows the root under 'Message data' and the time under 'Time stamp'. Then openssl cms -verify -inform DER -in tijdstempel.tsr -purpose timestampsign -out /dev/null -CAfile <your system's root certificates>: that checks the timestamping service's signature up to a root certificate already on your computer (outcome: Verification successful). In OpenSSL 3, openssl ts -verify can wrongly give the error 'ess cert id not found' for some timestamp files.gekwalificeerd.tsr. Check that qualified.batch_root in the manifest is your batch root, walk qualified.path up to qualified.root, and check with openssl ts -reply -token_in -in gekwalificeerd.tsr -text whether 'Message data' is that root; 'Time stamp' is the qualified time. Look up the issuer of that timestamp file in the EU trusted list (eIDAS Trusted List): the service is listed there as QTST with status 'granted'. The root certificate is usually not on your computer, but it is in that list. The legal presumption (eIDAS Art. 41(2)) applies to that time of the root; whether it also applies to your record is for the court to assess. The precise moment of the record comes from witness 1.ots --no-bitcoin verify -d <root> bitcoin.ots (opentimestamps-client) names the Bitcoin block and the Merkle root that block must have. Compare it on blockstream.info or mempool.space; with your own Bitcoin node, ots verify does this in one step. Bitcoin proves that the root existed before that block; the precise time comes from witness 1. No block height in the manifest means: submitted, no block yet; download the bundle again later.Claude, ChatGPT or your own agent runs the same checks and explains them. Two routes: through our server (facts, no content), or entirely without Vidimus, with the bundle.
{"mcpServers": {"vidimus": {"type": "http", "url": "https://app.vidimus.be/mcp"}}}
# tools: verify_registration, get_dossier, tamper_check, explain · with a key (a read key is enough): header x-api-keyYou have the evidence bundle (zip). Unzip it and run: python3 verify_bundle.py bundel.zip Report true/false/null for each check, with the note. Do not trust any fact from manifest.json that you did not recompute yourself. Bitcoin: compare the merkle root from bitcoin.ots with blockstream.info or mempool.space for that block.
Practise with a real bundle: voorbeeldbundel.zip (one temperature record from a demo logbook, 55 kB). Python 3 with the cryptography package is enough; for the timestamp and Bitcoin the script installs nothing, it tells you which step needs an extra tool. Or recompute files and a complete record in your browser with the hash lab: fingerprints, Merkle path and public root, without uploading anything.
GET /sources/{id}/reeks), each measurement with its fingerprint, in ascending time order.We answer questions from experts directly: oskar@vo-initiatives.com. See also Security and trust.