Read witness cosignatures
Read each configured witness’s latest stored cosignature.
GET
/{log}/witnesses- Access
- Public access
- Client
- Browser fetch supported
Parameters#
| Name | Location | Meaning |
|---|---|---|
logRequired | Path | The log name identified by /v1/log, such as staging-1. |
Request examples#
cURL
curl -fsS 'https://log.veil.rip/staging-1/witnesses'Response#
JSON with origin, quorum and witnesses. Different witnesses may have signed different tree sizes.
| Field | Type | Meaning |
|---|---|---|
origin | string | Log origin. |
quorum | integer | Required witness count. |
witnesses | array<LogWitness> | Per-witness signed checkpoint information. Validate against the policy and signed notes. |
Expand a nested object for its fields. Types ending in null allow a null value; optional fields may be absent. Other fields are present in that object.
Log witness LogWitness
| Field | Type | Meaning |
|---|---|---|
name | string | Witness key name. |
vkey | string | Signed-note verifier key. |
url | string | Witness service URL. |
size | integer | Most recently cosigned tree size; witnesses can lag behind each other. |
checkpoint | string | Signed checkpoint associated with this witness. |
cosignature | string | Witness cosignature. Check it against the policy. |
seen | string | Time the log last observed this witness response. |
Response headers#
| Header | Value | Meaning |
|---|---|---|
Content-Type | application/json | Use the declared media type before choosing a parser. |
What to verify#
Verify each cosignature against the expected witness key and the checkpoint it signed.
Errors#
The log host serves its own text or binary protocol. Missing resources can return HTTP 404; do not assume a directory JSON error envelope. Response and error guide