Every package SIVACOR verifies comes with a TRO declaration and a detached
signature over it (the .jsonld and .sig files in the package’s tro
folder). The signature is made with the key on this page.
The TRO also carries a copy of the public key (trov:publicKey), but that copy
cannot vouch for itself: anyone can sign a declaration with a key of their own
and embed that key. To know that a TRO was signed by SIVACOR, check its
signature against the key published here, outside the TRO.
Fingerprint¶
The current signing key has this fingerprint:
F7DB 4853 9F20 7AD4 612D C408 D8BB 2071 862A FF4AIt is what to compare: a key is identified by its fingerprint, not by its name or e-mail address, which anyone can put in a key of their own.
| Algorithm | ed25519 (signing), cv25519 (encryption subkey) |
| Created | 2025-11-13 |
| Expires | never |
| User IDs | SIVACOR TRS <editors@sivacor.org>, Admin SIVACOR <admin@sivacor.org> |
| Status | current |
The key¶
The canonical copy of the key is the file at
https://
That address is stable, and is the one to use from scripts. The block below is the same file, included into this page when the site is built, so the two cannot differ.
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEaRZowxYJKwYBBAHaRw8BAQdAZE3O+GSW5cJRjptdb8N7UW6jI7l6URVid7Qy
sO4TTMO0IVNJVkFDT1IgVFJTIDxlZGl0b3JzQHNpdmFjb3Iub3JnPoiTBBMWCgA7
FiEE99tIU58getRhLcQI2LsgcYYq/0oFAmkWaMMCGwMFCwkIBwICIgIGFQoJCAsC
BBYCAwECHgcCF4AACgkQ2LsgcYYq/0roKAEAzcHiTUWZPf7IrTct0Zc9wV6C6pIi
Jz5s6EvopXMbiA4A/06xb/as9R479KXUtS7GmuIe5A1cKn6IHnu0gt1v9CUJtCFB
ZG1pbiBTSVZBQ09SIDxhZG1pbkBzaXZhY29yLm9yZz6IkwQTFgoAOxYhBPfbSFOf
IHrUYS3ECNi7IHGGKv9KBQJpfQJHAhsDBQsJCAcCAiICBhUKCQgLAgQWAgMBAh4H
AheAAAoJENi7IHGGKv9KnDcBAMAw+4jrpQGsbaJrgs/2MO/Q2TYTH2Rlsh9WVT1l
LlYYAP0W+WkIs+J0VnuEXCrLcc6rc9iQUiBKb7lWqTaaECk1Bbg4BGkWaMMSCisG
AQQBl1UBBQEBB0BoHfFiGW3Stl+JnlWswb3vpXuiEVAmWUst/dTIbk9NEgMBCAeI
eAQYFgoAIBYhBPfbSFOfIHrUYS3ECNi7IHGGKv9KBQJpFmjDAhsMAAoJENi7IHGG
Kv9Kmu0BAOcqj2DerJgZH7126goV0tXBqncbG5MPuzufGmdjYJ07AQCJAX/uj9X/
v+YHdwl32ozy/kKWYaqlbrODQUbgSu0xBA==
=iFZz
-----END PGP PUBLIC KEY BLOCK-----
The key is also published from the sivacor.org domain itself, through a Web Key Directory, so GnuPG can fetch it by e-mail address:
gpg --auto-key-locate clear,wkd,nodefault --locate-external-keys editors@sivacor.orgIt is on keys.openpgp.org too, with both addresses confirmed. That server publishes an e-mail address on a key only after the owner of the mailbox has confirmed it, so a lookup there by address is also a check that the key belongs to SIVACOR:
gpg --keyserver hkps://keys.openpgp.org --recv-keys F7DB48539F207AD4612DC408D8BB2071862AFF4AA copy is also on the Ubuntu key server. That server accepts uploads from anyone, so it is a convenience, not a source of trust: confirm the fingerprint against this page.
Key list¶
The keys SIVACOR has signed with, and when, are also published as a machine-readable list at
https://
It follows the TRS key list format
that tro-utils verify-signature --trs-keys reads, and like the key file it is
included into this page from the file served at that address:
{
"format": "https://w3id.org/trace/trs-keys/v1",
"updated": "2026-11-17T00:00:00Z",
"systems": [
{
"ids": ["https://sivacor.org/", "trs"],
"name": "SIVACOR",
"keys": [
{
"fingerprint": "F7DB48539F207AD4612DC408D8BB2071862AFF4A",
"valid_from": "2025-11-13T23:24:51Z",
"valid_until": null,
"status": "current"
}
]
}
]
}
fingerprintnames the key; the key itself is the filesivacor-trs.ascabove.valid_fromandvalid_untilbound when SIVACOR signed with the key.valid_untilisnullwhile the key is in use.statusiscurrent,retiredorcompromised; a compromised key also carriescompromised_since. See Key life cycle.idslists every identifier SIVACOR has given itself in a TRO (trov:wasAssembledBy). TROs signed before October 2026 use the generictrs, which older versions oftro-utilswrote for every TRS; see History. Matchingtrsdoes not let another system’s TRO pass, since its signature must still come from a key listed here.
A key is never removed from the list, so TROs it signed stay verifiable.
Checking a TRO’s signature¶
With tro-utils 0.5.3
or later, check the signature against the key list:
curl -fsSO https://docs.sivacor.org/keys/sivacor-trs-keys.json
tro-utils verify-signature tro/tro-<id>.jsonld --trs-keys sivacor-trs-keys.jsonA valid signature looks like this:
Signature: OK
Signed by: Admin SIVACOR <admin@sivacor.org>
Key fingerprint: F7DB48539F207AD4612DC408D8BB2071862AFF4A
Key listed in: sivacor-trs-keys.json (current)
Timestamp: 2026-09-20T09:06:42+00:00The list vouches for the key’s fingerprint, so tro-utils can take the key
itself from the TRO. It also checks the TRO’s trusted timestamp (the .tsr
file) and judges the key as it stood at that time, so a TRO stays verifiable
after its key is retired. To take the key from the canonical file instead of
the TRO, add --keyring sivacor-trs.asc after downloading it.
With GnuPG alone¶
Without tro-utils, use gpgv with a keyring holding only the SIVACOR key, so
that nothing is imported into your own keyring and no other key can satisfy the
check:
curl -fsSO https://docs.sivacor.org/keys/sivacor-trs.asc
gpg --dearmor < sivacor-trs.asc > sivacor-trs.gpg
gpgv --keyring ./sivacor-trs.gpg tro/tro-<id>.sig tro/tro-<id>.jsonldThe ./ matters: without it, gpgv looks for the keyring in its own home
directory instead. A valid signature looks like this:
gpgv: Signature made ...
gpgv: using EDDSA key F7DB48539F207AD4612DC408D8BB2071862AFF4A
gpgv: Good signature from "Admin SIVACOR <admin@sivacor.org>"
gpgv: aka "SIVACOR TRS <editors@sivacor.org>"Compare the fingerprint gpgv prints with the one above.
Good signature means the declaration is exactly as SIVACOR signed it; any
change to it, down to a single byte, makes the check fail.
gpgv does not look at the trusted timestamp (the .tsr file). Check it
separately, with tro-utils verify-timestamp; see the FAQ.
It proves when the declaration and signature existed, which is what keeps a
TRO verifiable after the key that signed it is retired.
Key life cycle¶
Expiry. The current key has no expiry date.
Replacement. If SIVACOR changes keys, the new key is added to this page and to the key list, and the old one is marked
retiredwith the date it went out of use, so that TROs it signed remain verifiable. A retired key is never removed from either.Revocation. If a key is ever compromised, its revocation is published here and on the key servers, and the key list marks it
compromisedfrom the earliest date it may have been in other hands.gpgwill then warn about every signature made with that key, including older ones, and some tools reject the signature outright. For a TRO signed before that date, the evidence that it is genuine is its trusted timestamp, which proves the signature already existed while the key was still trustworthy.tro-utils verify-signature --trs-keysmakes that comparison itself: it accepts such a TRO, with a warning, and rejects one timestamped later.
History¶
What SIVACOR has written into its TROs over time. Signed TROs cannot be changed, so an older TRO keeps whatever was current when it was made.
| Date | Change |
|---|---|
| 2025-11-13 | Key F7DB 4853 … 862A FF4A created, with user ID SIVACOR TRS <editors@sivacor.org>. |
| 2025-12-13 | TRS contact (trov:contact) changed from the placeholder email@goes.here to admin@sivacor.org. |
| 2026-01-30 | User ID Admin SIVACOR <admin@sivacor.org> added to the same key. TROs signed after this date embed a copy of the key with both user IDs; the fingerprint is unchanged. |
| 2026-10 | TRS identifier (trov:wasAssembledBy / @id) changed from the generic trs to https://sivacor.org/, with the move to tro-utils 0.5. The key list gives both. |
| 2026-11-17 | Key list published. |
The contact address that a TRO gives for SIVACOR (trov:wasAssembledBy /
trov:contact) was the placeholder email@goes.here in TROs signed before 2025-12-13, such as
one signed on 2025-12-10, and has been admin@sivacor.org since. Either way, the TRO was signed by the key
above, and support@sivacor.org is the address to write to.