Digital Signatures on Certificates, in Plain English

You have signed your name on paper to say this is mine and I mean it. A digital signature does the same job for a certificate, except it is impossible to forge by hand and a computer can check it in milliseconds. Here is how that works without the jargon.

Two keys instead of one pen

A digital signature uses a pair of keys that are mathematically linked. One is private and the issuer keeps it secret. The other is public and anyone can have it. The private key creates signatures. The public key checks them. You can verify a signature with the public key, but you can never work backwards to the private key, so you can confirm a certificate without being able to forge one.

What actually gets signed

When a certificate is issued, the system takes its meaningful data, such as the recipient's name, the qualification, the date, and a unique ID, and arranges it in a fixed, canonical form. The private key then produces a short signature over that exact data. The signature is stored with the certificate. Because it is tied to the data, the signature is unique to this certificate and nothing else.

How verification works

Checking is the clever part. A verifier takes the certificate's data, applies the issuer's public key to the signature, and asks one question: does this signature match this data from this issuer? The answer is a clean yes or no.

• Yes: the data is exactly as the issuer signed it, and it really came from them.
• No: the data was changed, or the signature did not come from that issuer.

Change a single character, a grade, a date, a letter of the name, and the maths no longer lines up. There is no partial pass. That all-or-nothing property is what makes signatures so useful for credentials.

Why Ed25519

Ed25519 is a modern signature scheme, and there are good reasons it is popular. It is fast, so signing thousands of certificates in a batch is quick. It is compact, so the signature does not bloat the certificate. And it is robust, designed to avoid several footguns that tripped up older schemes. In short, it gives strong security with small, fast signatures, which is exactly what high-volume certificate issuance needs.

Signing data beats signing a PDF

A subtle but important point: it matters whether you sign the document or the data. Signing a PDF only protects that one file, and the same information can be poured into a fresh file that carries no signature. Signing the canonical data fields protects the credential itself, however it is displayed. The certificate becomes a view of signed data, not a loose file that happens to look official.

Do it with QRCertificates

QRCertificates puts this to work in a way your recipients never have to think about. Every certificate is signed with Ed25519 over its canonical data fields, so we sign the data and not the PDF, and one changed character fails verification. Each certificate carries a QR code and a short human-readable code for one-click public verification on any device, with no login, no app, and no blockchain. The result also confirms a verified issuer identity, and verification is always free. The cryptography is serious; the experience is just a scan.