key_id) with the one we publish here.
The current key
Current since 13 Nov 2026. Ed25519 algorithm. The fingerprint (
key_id) is the sha256 of the public key’s 32 raw bytes.key_id
blockgence-evidencia.pub.pem. It can also be downloaded from the Verify page on the website.
Why you need to compare it
Every signed document carries its own copy of the public key, inmanifest.integrity.attestations.signature. That copy lets you verify the signature without asking for anything, but on its own it proves nothing: anyone can strip Blockgence’s signature and sign with another key.
What proves the document was issued by Blockgence is that its key_id is the one on this page. That is why, when you verify a signature, you use the key downloaded from here and not the one the document carries.
Where it is published
The same fingerprint is published through three channels, which must say the same thing:The website
www.blockgence.com/en/verify.html (and /verificar.html). The key is written into the HTML: it is not requested from the signing server.The API
GET /v1/evidence/signing-key, open: no API key, no session and no credits.This documentation
This page, with the same registry.
The website does not ask the server for the key, on purpose: if the signing server were compromised, it could also serve a different key. When in doubt, the reference is the one published on the website.
The key from the API
configured: the key that server signs with today, derived from its private key (never the private key itself). If the server has no key, it isnullandconfigured_notesays why.published: Blockgence’s versioned key registry, with the current, retired and revoked keys and their periods. This is the fingerprint worth comparing.
matches_published says whether the configured key is the current published one. If it is false, that is a warning: the server signs with a key that is not published yet, or with a retired or revoked one.
Key states
If the key changes
- Rotation: the new key shows up as current and the previous one moves to the retired list, with its period. Documents signed with the previous key during its period remain valid.
- Compromise: the key moves to revoked, with the date and the reason, and a new one is generated.
Retired and revoked keys: none so far.