Hi,

Sorry, I think I made a mistake when computing the vkey (wrong key type)

Here's the correct one (hopefully!):

witness.stagemole.eu+67f7aea0+BEqSG3yu9YrmcM3BHvQYTxwFj3uSWakQepafafpUqklv

On Mon, 3 Nov 2025 at 18:58, Rasmus Dahlberg <rgdd@glasklarteknik.se> wrote:

Hey,

Starting with the testing list sounds good (staging is not open yet).

https://testing.witness-network.org/log-list.1

We need to know how often this list is configured, e.g., hourly. Can
you also update your witness about page with the info outlined here:

https://witness-network.org/participate/#specify-an-about-page-url

Sorry, I missed that. I'll fix it.

Regarding performance profiles: the idea is the witness operator picks a
list they can support capacity wise. For example, if you have a witness
that can only sign one checkpoint per second it wouldn't work to be on
a list with a 10qps performance profile. But if you have a witness that
handles 20qps, we (the maintainers) would expect 10 qps reserved for us.

So to answer your question, yes it defines what logs you get. We will
basically only sign up as many logs as the performance profile allows!

(We don't have a performance profile for testing, but we will have that
for both staging and production to maintain different lists reliably.)

Does that make sense and clear things up?

I think I understand the concept of the performance profile, but it was not clear what choices are available to me as a witness operator.

But I see now that the staging list is named something like log-list XqpsYlogs. So I guess the pair (X,Y) is the performance profile and that there'll eventually be more than one?

Grégoire