Add Google's new staging and prod CT logs#36
Conversation
|
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. |
|
Update: we're working on getting a higher qps list added, please hold on :-). |
|
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: Thanks! |
27d3082 to
5f2e792
Compare
rgdd
left a comment
There was a problem hiding this comment.
LGTM, just fix the one minor nit comment and we're good to go!
|
Brilliant, thank you very much!
I'm hoping that folks monitoring the logs will use these signatures to make sure everybody has the same view of the log. 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. |
Sweet! (On a personal note I'd be happy to incorporate verification of cosignatures in silentct.) |
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.