Hello,

I'd like to add a transparency log to the staging list. Details per https://www.google.com/url?q=https://witness-network.org/participate&source=gmail&ust=1789321125141000&sa=E:

Origin line
https://www.google.com/url?q=http://notbefore.net/log&source=gmail&ust=1789321125141000&sa=E

Public key (vkey, Ed25519, key type 0x01; key name = origin line)
https://www.google.com/url?q=http://notbefore.net/log%2B8b627e7f%2BAfPQekreiy4JUcf8TEcJs4Mj00EHL7JvHUSSLXeyZVLs&source=gmail&ust=1789321125141000&sa=E

Log-list entry, in your log-list-format terms
vkey https://www.google.com/url?q=http://notbefore.net/log%2B8b627e7f%2BAfPQekreiy4JUcf8TEcJs4Mj00EHL7JvHUSSLXeyZVLs&source=gmail&ust=1789321125141000&sa=E
qpd 60
contact docdailey@gmail.com

add-checkpoint rate
Two requests per hour in steady state — one per published record (a commit at :01 and a reveal at :06 past each hour) — plus rare back-fills. Requesting qpd 60 to leave headroom; typical days will use about 48.

List
staging. This is a real, running log with real usage; we're happy to dogfood.

Contact
docdailey@gmail.com · https://www.google.com/url?q=https://notbefore.net/&source=gmail&ust=1789321125141000&sa=E · https://www.google.com/url?q=https://github.com/docdailey/qrng-beacon-log&source=gmail&ust=1789321125141000&sa=E

What the log is
An hourly commit-then-reveal randomness beacon ("NotBefore"): a 32-byte value is committed before a named drand quicknet round exists and revealed after it, so a consumer can check that the value was fixed before the round and not selected after. Each commit carries two RFC 3161 timestamps; every record is additionally anchored in Rekor and OpenTimestamps. The Merkle tree is RFC 6962 over every published record; checkpoints follow https://www.google.com/url?q=http://c2sp.org/tlog-checkpoint&source=gmail&ust=1789321125141000&sa=E and are signed in the same commit as the record they cover. The current checkpoint is served at https://www.google.com/url?q=https://notbefore.net/checkpoint&source=gmail&ust=1789321125141000&sa=E and history at https://www.google.com/url?q=https://notbefore.net/checkpoints/NNNNNN&source=gmail&ust=1789321125141000&sa=E; the same files are in the GitHub repository above. Tree size is ~52 today, growing by ~17,500 entries per year. Origin and key are permanent by policy; a key rotation would be announced in the repository and the origin would not change.

Implementation notes
The log speaks https://www.google.com/url?q=http://c2sp.org/tlog-witness@v1.0.0&source=gmail&ust=1789321125141000&sa=E (add-checkpoint with old size + consistency proof; 409 handling) and appends cosignatures per https://www.google.com/url?q=http://c2sp.org/tlog-cosignature@v1.0.1&source=gmail&ust=1789321125141000&sa=E. We have been exercising the client hourly against a witness we run ourselves, and have implemented the RFC 6962 vectors, signed-note and cosignature key-ID derivations as tests (https://www.google.com/url?q=https://github.com/docdailey/qrng-beacon-log/blob/main/tlog.py&source=gmail&ust=1789321125141000&sa=E, `selftest`). If anything in our checkpoints or requests is non-conformant, I'd be grateful to hear it — this is our first participation in the network.

Once approved, we will configure the staging witnesses' add-checkpoint endpoints and keys from the witness tables and start submitting on the next published record.

Thank you,
Doc
docdailey@gmail.com
https://www.google.com/url?q=https://notbefore.net/&source=gmail&ust=1789321125141000&sa=E