Verification

Verify a certificate,
fully independently.

Lawyer, judge, insurer, opposing party or simply a third party: anyone who has a Scealia certificate can check its authenticity. No account or authorization is needed.

Verify a Scealia proof

Drop the certificate (PDF) or the technical proof file (.asice): they contain the original file, unless it was too large to be attached; in that case, drop it as well. The computation happens in your browser: your files never leave your device. Only the public identifier of the transaction is sent, to read the blockchain.

Drag the files here
or click to select them

Do you only have the file, and the fingerprint shown on a certificate or a link? Drop the file: the page will let you paste the fingerprint to compare them.

What is verified, and how to do it again without Scealia
  1. The SHA-256 of the original file is the fingerprint held in the proof record, preuve.json.
  2. The SHA-256 of the proof record is the proof fingerprint.
  3. The transaction succeeded, comes from a Scealia anchoring address and contains the proof fingerprint. Its first word is the batch fingerprint: the SHA-256 of “scealia-dossier-v2:” followed by the fingerprints of the proofs recorded together.
  4. Each file in the technical proof file matches its manifest. Its signature file is not verified here; an eIDAS validator, such as the European Commission’s DSS tool, can do so.

Without Scealia: sha256sum for both fingerprints (this page shows them too), then a block explorer such as polygonscan.com for the transaction.

The former format, that of technical proof files containing metadata.json and of their certificates, was only used during testing: Scealia no longer supports it.

Scealia anchoring address: 0xd7FB2F693Fb01A969c62B014bB23B5be085624eC on Polygon.

What happens when you verify

Whatever the method (QR code, technical proof file or number), verification rests on a single idea: comparing two fingerprints of the same content, taken at two different moments.

The content, today

Its fingerprint is recomputed at the moment of verification, from the file presented to you.

a3f9 2c81 07d4 …
The certificate

It carries the fingerprint sealed at the moment of capture, on the blockchain and under seal: no one can change it anymore, not even Scealia.

a3f9 2c81 07d4 …
The comparison

The two fingerprints are placed side by side. They can only be one of two things: identical, or completely unrelated.

Fingerprints match The content is exactly the one that was captured, and its date is established.
Fingerprints do not match The content has been modified since the capture, even by a single byte: the alteration is detected.

Demonstration: the three methods of the full service

Each method has a simulation button that runs through a successful verification, all the way to the certificate and its content. The full service will open very soon, when the public testing phase of the app launches.

By QR code

Every Scealia certificate carries a QR code. Scan it with your phone: you land directly on this page, the certificate is authenticated and its content is displayed. The QR code encodes a unique verification token that cannot be guessed.

By technical proof file

Drop the technical proof file you received: it brings together the content, its capture details and its seal in a single file. Everything is read locally in your browser. The file never leaves your device.

Drag a technical proof file here
or click to select it

By certificate number

If you cannot scan the QR code, enter the number and the verification code, both shown on the certificate. The secret code prevents any random searching.

Verifying without Scealia. Every certificate remains verifiable independently of our services: the folder’s fingerprint is recorded on the public Polygon blockchain (viewable through any public explorer; the transaction reference appears on the certificate) and the qualified electronic seal can be checked in any compliant signature validator, as the provider is listed on the European Union trusted list. Detailed instructions are on the last page of every certificate. See a sample certificate.