- Participate - Witness-network mailing lists

ct-uptime-alerts.fly.dev is now uptime.geomys.org
by Filippo Valsorda 28 Mar '26

28 Mar '26

Hello folks, We moved the https://ct-uptime-alerts.fly.dev/witness/ service to https://uptime.geomys.org/witness/ and plan to decommission the old one a month from now. It otherwise works exactly the same. Please migrate if you are using it for monitoring! Also, a tip: to avoid false positives, configure uptime monitoring to check from locations in Europe and in the US, and to only alert if both/all are down. This will hit separate instances and will avoid alerting due to downtime of an instance (as opposed to witness downtime). Cheers, Filippo

1 0

Re: Request to add witness witness.stagemole.eu
by Rasmus Dahlberg 27 Feb '26

27 Feb '26

On Wed, Nov 05, 2025 at 08:27:39AM +0100, Grégoire Détrez wrote: > On Tue, 4 Nov 2025 at 15:21, Rasmus Dahlberg <rgdd(a)glasklarteknik.se> wrote: > > > $ echo "witness.stagemole.eu+67f7aea0+BEqSG3yu9YrmcM3BHvQYTxwFj3uSWakQepafafpUqklv" > > | sigsum-key from-vkey -v > > Key name "witness.stagemole.eu", key type: 0x04 (cosignature/v1) > > ssh-ed25519 > > AAAAC3NzaC1lZDI1NTE5AAAAIEqSG3yu9YrmcM3BHvQYTxwFj3uSWakQepafafpUqklv sigsum > > key > > > > Looks well-formed and with the right type! > > > > 🎉 🎉 🎉 > > > > Starting with the testing list sounds good (staging is not open yet). > > > > I was wondering about this: does it mean we'll need to pull both the test > list and the (selected) staging list in the future? Good question -- the test list is intentionally a bit YOLO so I'd say it's ok that you stop configuring it and instead switch to staging later. If anyone has a different take I'd be curious to hear it! > > I'm intending to add > > > > | Mullvad VPN AB | [testing/log-list.1][] | < > > https://witness.stagemole.eu/about> | > > > > to the testing witness table here: > > > > https://witness-network.org/witness-tables/ > > > > Just waiting for the about page to be ready -- so let me know when it is! > > > > Ready now ☑️ Just queued you up in the testing table -- you can see the status here: https://github.com/transparency-dev/witness-network/pull/18 > > > > Yep, correct. And I'd say a likely way this turns out is if we, e.g., > > have a > > 1qps list then the 10qps is probably having the 1qps list as a subset. So > > basically, as a witness operator you'd select the highest profile your > > able to > > accomodate, and we as maintainers will do our best to direct logs to the > > different lists without hogging all the capacity. So for example, we would > > definitely not put a 1qps log on the 1qps list, since then it's full. :-) > > > Thanks, that does make it clearer! (Sounds like a fun allocation > problem 🤓) Fantastic, thanks for asking the questions! -Rasmus > > Grégoire

1 1

New staging witness: witness.navigli.sunlight.geomys.org
by Filippo Valsorda 01 Dec '25

01 Dec '25

Hello folks, I am happy to introduce the witness.navigli.sunlight.geomys.org staging witness. It replaces the experimental navigli.sunlight.geomys.org/dev testing witness. It is operated by Geomys, and it configures all the staging and testing lists. The about page is https://geomys.org/witness/navigli. Cheers, Filippo P.S. In order to have something meaningful to point uptime monitoring at, I built a little service that submits a checkpoint to a witness and returns 200 OK only if the returned signature is fresh and valid. You are welcome to use it to monitor your own witnesses. https://ct-uptime-alerts.fly.dev/witness/

2 1

Request to add witness witness.stagemole.eu
by Gregoire Detrez 04 Nov '25

04 Nov '25

Hello again! We would also like to add our staging witness to the witness network: - operator name: Mullvad VPN AB - vkey: witness.stagemole.eu +ac5cc086+BEqSG3yu9YrmcM3BHvQYTxwFj3uSWakQepafafpUqklv - log list: testing and/or staging (?) - about page: https://witness.stagemole.eu/about I don't really understand the part about a performance profile: is there a list of options I can pick from? Does this determine what logs I get from the witness network? Cheers, Grégoire

2 3

Requests to add log serviceberry.tlog.stagemole.eu
by Gregoire Detrez 03 Nov '25

03 Nov '25

Hello, We'd like to participate to the Witness Network by adding our staging Sigsum log: - origin-line: sigsum.org/v1/tree/1643169b32bef33a3f54f8a353b87c475d19b6223cbb106390d10a29… - vkey: sigsum.org/v1/tree/1643169b32bef33a3f54f8a353b87c475d19b6223cbb106390d10a29… - add-checkpoint rate: every 10s - contact: services(a)mullvad.net, https://serviceberry.tlog.stagemole.eu/about I'm not sure what list is appropriate at this point. Going by the descriptions on the witness-network website, our intention is to run this more as a staging log (long-term but experimental), but I think the test list would work as well. (There doesn't seem to be any witness in the staging table so maybe it's too soon to add logs to the staging list?) Cheers, Grégoire

2 1

Participation request for my test witness called witness1.smartit.nu/witness1
by Elias Rudberg 19 Oct '25

19 Oct '25

Hello! I would like to participate with my test witness called witness1.smartit.nu/witness1 Operator name: Elias Rudberg Log list: I have configured only the "Testing" list, because this is only a test witness. About page URL: https://witness1.smartit.nu/witness1/about.txt Best regards Elias Rudberg

1 0

Witness participation request
by Florian Larysch 17 Oct '25

17 Oct '25

Hi, I'd like to participate in the witness network with my test witness "remora.n621.de". Operator: Florian Larysch About page: https://remora.n621.de Log lists: testing/log-list.1 (imported hourly) Thanks!

2 2

Participation request for test log "barreleye" related to the Sigsum project
by Elias Rudberg 17 Oct '25

17 Oct '25

Hello, We would like to participate by adding our test log "barreleye". Origin line: sigsum.org/v1/tree/4e89cc51651f0d95f3c6127c15e1a42e3ddf7046c5b17b752689c402… Public key in vkey format: sigsum.org/v1/tree/4e89cc51651f0d95f3c6127c15e1a42e3ddf7046c5b17b752689c402… Add-checkpoint rate: Every 10 seconds Log list: This is a test log, so please add it to the "testing" list. Contact information: Email: sigsum-logs (at) glasklarteknik.se Other information: This is a test log related to the Sigsum project, see https://www.sigsum.org/ for more information. Best regards, Elias Rudberg Glasklar Teknik AB

2 1

2026

2025

Participate ----- 2026 ----- May 2026 April 2026 March 2026 February 2026 January 2026 ----- 2025 ----- December 2025 November 2025 October 2025

Participate