Every credential is logged
Before a credential takes effect, its entry is in the log. No entry, no credential.
TRANSPARENCY
Every credential Zuger issues, renews or revokes goes into a public, append-only log first. Anyone can check that an entry is there, and that the log was never rewritten.
Built, and not live yet
Nothing on this page is live yet. No credential has been issued, the public verifier is not open and the log is not published. This page describes what is built and how it will work; each part goes live on its own, and this list will say so.
THE LOG TODAY
Before a credential takes effect, its entry is in the log. No entry, no credential.
The log only grows. Once witnesses cosign, a rewrite or a second version shows.
Independent witnesses cosign each checkpoint. None is onboarded yet, and this page will name each one only once it cosigns.
WHAT IS LOGGED
| Entry | What the public sees |
|---|---|
| A credential | A salted hash of it. Its subject is hashed again with a salt that changes every day, so the log cannot count a company’s Runs. |
| A revocation | A salted hash of the credential and the time it was revoked. |
| A step of the Agent Chain | A salted hash of the signed step. |
| Never | A company, an agent, a person, a count per agent, or what a step was about. |
With nothing per company in the log, there is nothing to search by. Whoever holds an entry and its salt can find it and prove it is there.
CHECKPOINTS
Each new entry gets a signed promise straight away: its place in the log, and that it will be in a checkpoint within 5 minutes.
Each checkpoint signs the size of the log and its root. The log never shows two roots for one size.
The log signs with a key of its own, never one that signs credentials.
WITNESSES
A witness is an independent party that cosigns each checkpoint only if it extends the last one it saw. With enough of them, Zuger cannot show one history to you and another to someone else.
| Today | |
|---|---|
| Witnesses needed | 3 independent witnesses, in at least three countries |
| Witnesses cosigning | 0 of 3. None is onboarded yet. |
| Until then | The log is published as unwitnessed, and this page says so. |
| Timestamps | Hourly timestamps from two independent providers are planned. None is contracted yet. |
| Mirrors | Copies of the log kept by others. None is live yet. |
CHECK AN ENTRY YOURSELF
A few calls to a free, public API, and a few lines of hashing. None of it is live yet.
From the entry and its salt: HMAC-SHA-256 under the salt, over “kya-log-leaf/v1”, a new line, then the entry.
Check the log’s signature on it, and each witness’s cosignature.
Ask for the inclusion proof of your leaf at that checkpoint’s size.
Hash your way up the proof as RFC 9162 says. If you reach the checkpoint’s root, the entry is in the log.
Keep the checkpoint. The consistency proof shows any later one extends it.
| Read | Answers |
|---|---|
GET /v1/kya/log/checkpoint | The latest signed checkpoint, with the cosignatures received |
GET /v1/kya/log/proof/inclusion | The inclusion proof of a leaf |
GET /v1/kya/log/proof/consistency | The consistency proof between two sizes |
GET /v1/kya/log/entries | Entries by position: the index and the leaf only |
Coming soon The log, its API, the witness list and the open-source monitor are not published yet.
The Agent Chain stands on this log: each step an agent takes, signed and chained to the person who asked.
Log in to pick up where the agents left off
By continuing you agree to our Terms & Privacy Policy
Don’t have an account? Create account
Free to start · No card
By continuing you agree to our Terms & Privacy Policy
Already have an account? Log in
If has an account, six digits are on their way. They work once, for ten minutes.
New to Zuger? Create account · Use another address
If can be used, a link is on its way.
Open it on the device you want to sign in with — your phone, most likely. It works once, expires in a few hours, and can only create a passkey: it cannot read anything or approve anything.