LLPROBeta

Home / Signing keys

Signing keys

Machine copy, signed: /.well-known/llpro-keys.json (version 3, 2026-11-15). Active keys as JWKs: /.well-known/jwks.json. Offline check: /verify.

What this covers

Every key LLPRO signs with: the key of each Trust and Lane B product, the agent card key, Countersign, Agent Record, certificates, stamp outcomes, registry proofs and the Trust Log. Each is an Ed25519 key (RFC 8032). Its public half is listed below with the date it started and, once closed, the date it stopped.

How keys are kept

Each private key is a file on LLPRO's own server that only the service account can read (mode 600, folder 700). Keys are never printed, sent in messages or put in code repositories.

A nightly backup copies the key files to a second LLPRO machine. An encrypted copy kept off LLPRO's premises waits on the owner (not in place yet). Until it is, losing both machines means losing the keys: we would then rotate and say so here.

Rotation

Every product key is replaced at least once a year, and at once when we suspect it was seen by anyone else. Rotation makes a new key, closes the old one (its 'valid to' date is set) and keeps the old private key in a closed folder, read-only, never used again. It is not deleted, so the record stays complete.

Answers signed before a rotation keep verifying with the old key, because the history shows the old key was valid at that time. Answers that claim a time after the close date are refused.

Revocation

If a key is lost or may be known to someone else, we revoke it: the history gets a revocation with the reason and the time from which answers signed by that key are no longer trusted. That time may be earlier than the day we found out.

Revocations are published in the same signed file and on LLPRO's public failure record. They are never removed.

The key that signs the history itself is pinned inside the offline verifier. If it were ever exposed, we would make a new one, ship it in a new release of the verifier, publish the change here and on the failure record, and history files signed by the old one would no longer be trusted.

If a key is lost or stolen (our steps)

1. Stop using it: rotate the key (a new key takes over at once).

2. Revoke it here with the earliest time it could have been exposed.

3. Write the event on the public failure record: what happened, from when, what to stop trusting, what we changed.

4. Tell the agents we know depend on it, through the channels they gave us, without delay.

5. Check the Trust Log: answers logged before the exposure time stay proven; others signed by that key are not trusted.

What a signed time proves

The time inside a signed answer is the signer's own statement. Someone holding a stolen key could write an earlier time. A time is proven only once the answer is in LLPRO's public Trust Log, which fixes the order of entries. After a compromise, trust only answers logged before the revocation time.

How to check offline

Download /.well-known/llpro-keys.json and the offline verifier at /verify (llpro_verify.py, standard library only). Run: python3 llpro_verify.py transaction-audit KEY answer.json --keys llpro-keys.json. It checks the file is signed by LLPRO's key-history key (pinned inside the verifier), that the key is listed, that the answer's time is inside the key's valid dates and that the key is not revoked.

Keep the newest history file you have seen and pass it with --prev old.json: each file names the hash of every earlier one, so an older or altered file is refused.

Revocations

No key has been revoked.

Key history

Keys with the date each started and stopped (id shortened; every key with its full id and public key is in the signed file).

Signs forKey idFromToStatus
countersignpuugvf7mhsl22026-11-07nowactive
ground-truthanqbbpp6widr2026-11-07nowactive
agent-record33vniz6a33ql2026-11-07nowactive
agent-recorduibkpay4wzck2026-11-07nowactive
countersignj4oxdqbsevjw2026-11-07nowactive
agent-carddtyphb246o5a2026-11-07nowactive
llpro-certificate3nhd6mqp5qqt2026-11-10nowactive
transaction-audit5xqitz7n2oxj2026-11-11nowactive
spend-limits6p2vtbtuibau2026-11-11nowactive
run-records3ig6lb7654ps2026-11-12nowactive
agent-identity-check4nkux5vixiuq2026-11-12nowactive
certified-registera5fyinggks4g2026-11-12nowactive
witnessofmqnj43wtlw2026-11-12nowactive
signed-handoffswzmf5wbdlgtj2026-11-12nowactive
stamp-outcomes2z2o6vt4koaq2026-11-12nowactive
attribution, verified-attributionwmjdezlpxkcj2026-11-12nowactive
dispute-recordmgyewcyqyko52026-11-13nowactive
campusc6ywywsozw7j2026-11-13nowactive
key-historyktsb3tu55wfn2026-11-15nowactive
trust-logfvxbo2bbadli2026-11-15nowactive
45 other product keys, all active: listed with full dates in the signed file

Backed by LLPRO LLC. Policy text is plain language, not reviewed by an attorney.