Hello, We would like to participate in the Witness Network as a witness operator, starting with the testing list. Operator name: GBLIN Protocol Lists: testing/log-list.1 About page: https://gblin-mcp.gblin-mcp-worker.workers.dev/witness Witness name: gblin.digital/witness Verifier key: gblin.digital/witness+c335a002+BF54nC8Q1wHAlKirQexRC5phxjLtbEhcq8udv8TXPwXx add-checkpoint: POST https://gblin-mcp.gblin-mcp-worker.workers.dev/witness/add-checkpoint Contact: info@gblin.digital Discovery works as your guidelines ask: the list is downloaded once a day and used only to discover logs we do not know yet. A log we have already configured is never removed or modified because the list changed - the list is not our configuration file. As of today the witness has configured all nine logs currently in testing/log-list.1 and accepts pushed checkpoints from each of them; the about page enumerates them with the date each was added. To be precise about what is actually exercised: we accept pushes from all nine, but we actively poll only one log today, markovianprotocol.com/log, which we have been co-signing every ten minutes since 18 August. That is where the implementation was first tested against a real tree. On the protocol side we implement c2sp.org/tlog-witness: a checkpoint is accepted only if it verifies against that log's key, and, when we already hold a smaller tree for that origin, against a consistency proof; on success we return a c2sp.org/tlog-cosignature line. Sizes we hold are returned as 409 with the held size, a shrinking or forked tree gets 422. We keep one persistent record per log plus the history of cosigned notes. Two things you should weigh honestly. First, we are a small operator running this on Cloudflare Workers, so please read it as a testing-grade witness, not a production guarantee. Second, we also operate our own application transparency log (gblin.digital/receipts-log) and would eventually like it witnessed - but we are asking to give before we ask to receive, and the two requests are separate. Happy to answer questions or fix anything that does not match your expectations. Best regards, GBLIN Protocol https://gblin.digital Inviato con la posta elettronica sicura [Proton Mail](https://proton.me/mail/home).