beat-key
A key server for time-sealed envelopes, operated by beatkey-konveria.
This machine holds one share of a split key. It publishes a signature once a given moment has passed, and nothing else. On its own that share opens nothing — an envelope needs several, held by parties that do not answer to each other.
Endpoints
/info— this operator's public key and scheme/share/<beat_index>— the released share for that moment. 404 before it arrives, never a hint about how long is left/healthz— liveness
A share fetched from here is verified against the public key recorded in the envelope, not against this server. Once published it is ordinary public data: copy it, mirror it, archive it. This host is in neither the trust path nor the availability path.
What this server does not do
- It cannot open an envelope, and neither can anyone else holding a single share.
- It stores no user data. No ciphertext passes through it — it publishes signatures of numbers.
- It keeps no record of who asked for what.
Found this address in an envelope?
Then you are in the right place, and you probably want
the protocol
— it describes exactly what a share is and how to check one. The envelope format
itself is documented at
sigelith.org/seal (Sigelith, formerly
BeatTime — hence the beattime- prefix in the format names).