Transparency log · witnesses
Who has checked this log?
A witness is a separate party that re-checks the log and cosigns its tree head. Today the registry signs its own checkpoints, so the log is verifiable but not independently witnessed. Witnesses below were added by the operator; this page cannot tell you whether they are independent of it.
Allow-listed witnesses 0
None yet
Current tree head 27 leaves
Not cosigned
Run a witness
A witness is a small program with its own key. Each round it fetches the checkpoint, verifies the registry's signature, proves the log only grew since the last tree head it stored (RFC 9162 consistency proof), refuses on any rollback or fork, and only then signs and posts a cosignature.
git clone <repo> && cd agentpass/packages/witness
node cli.mjs keygen --name my-witness # writes my-witness.key.json (private) and prints your public entry
# send the public entry {name, kid, jwk} to the registry operator for WITNESS_KEYS, then:
node cli.mjs run --log https://superintelligencepassport.com --key my-witness.key.json --interval 300
Signed message: agentpass-witness-cosignature-v1
witness: <name>
<checkpoint note>, ECDSA P-256 / SHA-256. Machine-readable list: /log/witnesses.json. Full guide: packages/witness/README.md and WITNESSES.md in the repository.
What a cosignature means
- It says: this witness saw this tree head, and it extended the one it saw before. That is all.
- It does not say the entries are true, that the operator is trustworthy, or that the witness is independent.
- Stage 2 of the maturity ladder needs at least two unrelated witnesses, a public monitor, an external audit and an oversight board. None of that exists yet.