Hello maintainers of the Witness Network,
The Android Binary Transparency team at Google would like to submit our two new Tessera-backed transparency logs to the Public Witness Network for synchronous checkpoint co-signing. Below are the registration details for both logs:
Public Key (PEM Format):
-----BEGIN PUBLIC KEY-----
MCowBQYDK2VwAyEAOv01ATSC861V+PlwJK1TN2V+USnehmg0cPykibM+Pk4=
-----END PUBLIC KEY-----
Log List: staging (with intent to transition to production when available)
Add-checkpoint rate: At most once every 30 seconds (~2 requests/min, < 0.1 QPS)
Public Key (PEM Format):
-----BEGIN PUBLIC KEY-----
MCowBQYDK2VwAyEA/Ccebn2s1BMkgJyEx3trZbk9BrucLmHaBMR+rd+EIQg=
-----END PUBLIC KEY-----
Log List: staging (with intent to transition to production when available)
Add-checkpoint rate: At most once every 30 seconds (~2 requests/min, < 0.1 QPS)
Contact Information
Operational & Architecture Details
Implementation: Both logs are built on Tessera and adhere to the C2SP tlog-tiles specification (with height of 8).
Witness Interaction Policy:
- requests to witness /add-checkpoint endpoints are dispatched on a fixed 30-second interval by our backend publisher loop (internal rate-limiting prevents burst or traffic amplification).
- outbound HTTP requests are identified by User-Agent: Google-Android-Binary-Transparency/1.0 (<log_origin_string>)
- we operate in greedy collection mode with a 10second timeout, but with fail-open semantics. Temporary witness unresponsiveness or network delays will not block log ingestion or publication.
Please let me know if any additional information or adjustments are needed, and what are the next steps required.
Thank you,
Billy Lau
Android Binary Transparency Team