Skip to content

Add Google's new staging and prod CT logs#36

Merged
rgdd merged 3 commits into
transparency-dev:mainfrom
phbnf:google-stg-prod-init
Mar 31, 2026
Merged

Add Google's new staging and prod CT logs#36
rgdd merged 3 commits into
transparency-dev:mainfrom
phbnf:google-stg-prod-init

Conversation

@phbnf
Copy link
Copy Markdown
Contributor

@phbnf phbnf commented Mar 24, 2026

This PR adds Google's new staging and prod logs to ensure that all holes have been punched through. We'll follow with more recent shards later.

@rgdd
Copy link
Copy Markdown
Collaborator

rgdd commented Mar 25, 2026

Hey @phbnf, thanks for filing this!

Just a short ack that we've seen this, and before we can proceed filippo, al, and I need to sync on if we need a higher qps list to direct these requests towards or not. Sorry in advance for a little bit of delay.

Also a question -- who will be using the cosignatures that these logs collect? I'm in particular curious if it's necessary to collect every second, as opposed to on a lower frequency to not require as many witnessing resources.

@rgdd
Copy link
Copy Markdown
Collaborator

rgdd commented Mar 26, 2026

Update: we're working on getting a higher qps list added, please hold on :-).

#37

@rgdd
Copy link
Copy Markdown
Collaborator

rgdd commented Mar 26, 2026

Now https://staging.witness-network.org/log-list-100qps-40klogs.1 is available, and shortly there should be at least one witness pulling from this list. Can you redirect these CT log participating requests to the higher perf list:

https://github.com/transparency-dev/witness-network/blob/main/lists/staging/log-list-100qps-40klogs.1

Thanks!

@phbnf phbnf force-pushed the google-stg-prod-init branch from 27d3082 to 5f2e792 Compare March 27, 2026 10:30
Copy link
Copy Markdown
Collaborator

@rgdd rgdd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just fix the one minor nit comment and we're good to go!

Comment thread lists/staging/log-list-10qps-4klogs.1 Outdated
@phbnf
Copy link
Copy Markdown
Contributor Author

phbnf commented Mar 27, 2026

Brilliant, thank you very much!

Also a question -- who will be using the cosignatures that these logs collect? I'm in particular curious if it's necessary to collect every second, as opposed to on a lower frequency to not require as many witnessing resources.

I'm hoping that folks monitoring the logs will use these signatures to make sure everybody has the same view of the log.
At the moment, these logs are configured to publish a checkpoint every 1.5s, so 1 qps seems reasonable to leave a bit of margin if anything changes, and should allow to witness all the checkpoints logs publish.

We will send another PR in a few days with other temporal logs. In practice, for every family of logs, only one temporal log should publish one checkpoint every 1.5s. Other shouldn't have too many submission yet or anymore, and I expect them to grow slower. In the absence of growth, they will publish a checkpoint every 30s.

Copy link
Copy Markdown
Collaborator

@rgdd rgdd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM -- thanks @phbnf!

@rgdd rgdd merged commit 841d76d into transparency-dev:main Mar 31, 2026
4 checks passed
@rgdd
Copy link
Copy Markdown
Collaborator

rgdd commented Mar 31, 2026

I'm hoping that folks monitoring the logs will use these signatures to make sure everybody has the same view of the log.

Sweet! (On a personal note I'd be happy to incorporate verification of cosignatures in silentct.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants