Hello,

We'd like to enroll our transparency log with the Witness Network. It's a self-hosted C2SP tlog-tiles / RFC-6962 log for per-operator agent network identities. It emits conformant C2SP signed-note checkpoints (Ed25519, log-signed) and serves RFC-6962 consistency proofs, so a stock tlog-witness can cosign it with no bespoke integration.

  origin line   : whisper.online/ledger
  vkey          : whisper.online/ledger+8a3a5df0+AackwSi920iTu5AW3cOBaibI0RFtt4zT9Ox8mygciGm4
  checkpoint    : https://whisper.online/checkpoint          (verbatim C2SP signed note)
  key           : https://whisper.online/checkpoint/key
  consistency   : https://whisper.online/consistency?from=<a>&to=<b>   (RFC-6962)
  tiles         : https://whisper.online/tile/<level>/<index>          (tlog-tiles)
  add-cp rate   : bursty; we will throttle add-checkpoint submissions to at most a few per minute
                  and respect each witness's stated rate limit
  tier          : testing  (to shake out conformance first; then move to staging)
  contact       : kaveh@whisper.security

The checkpoint is a proper signed note: line 1 = origin, line 2 = tree size, line 3 = base64 RFC-6962 root, followed by a 68-byte Ed25519 note signature whose key-hash 8a3a5df0 matches the vkey above. We keep the origin and key immutable and never rewind the tree.

Thank you,
Kaveh Ranjbar, Whisper Security (viaGraph B.V.)