Hello,
We would like our log added to the testing list.
Origin line: gblin.digital/receipts-log
Public key: gblin.digital/receipts-log+00c6e18c+AY8/YnCHXTnsECT2EGv0M5RTqlVvFobctLv3WSihYkoG
add-checkpoint rate: at most 24 times per day, in practice far less - the log only grows when an agent seals something, which today is a handful of records per day
Log list: testing
We implement the log side of c2sp.org/tlog-witness as of 21 August: on every size change we POST "old <n>", an RFC 6962 consistency proof and the signed note to each configured witness, retry from the size a witness reports in a 409, and store the returned cosignature bound to the exact (origin, size, root) it was issued for. A stored cosignature is served in /log/checkpoint only while it still matches the current size, never re-attached to a later tree. Who cosigns, and at which size, is public at /log/witnesses.
Useful for your decision: the log is tiny - 18 leaves today, most of them our own tests - so the load is negligible and so, honestly, is the current utility to anyone but us. It is operator-signed only, which is exactly why we are asking. Anyone can check it without trusting us: /log/checkpoint, /log/consistency, /log/leaves (raw records, rebuild the tree yourself) and a zero-dependency offline verifier in the repository. If you would rather we come back when the log carries real third-party usage, that is a fair answer.
We are separately asking to participate as a witness operator for testing/log-list.1.
Best regards,
GBLIN Protocol
https://gblin.digital