Verifier admissions log
Every decision taken on a third-party verifier of the single-node production chain under the published admission policy, in an append-only public record with no personal data. No entry yet.
Every decision the admissions authority takes on a third-party verifier of the single-node production chain is recorded here, under the published admission policy: admissions, refusals, origin renewals, renewals and hand-overs of the identity check, suspensions, monitoring, reinstatements, revocations and appeal answers. The registry itself is on chain and readable with proofs; this log adds what the chain does not hold: the funding of each account, the reason for each decision, and the identity-check renewals the chain cannot record.
What it never carries. No personal data: no person’s name or contact, no company name beyond the registry’s public_display_name, no business register number, no KYC session, grade or signed acceptance. A refusal names no account, origin or business: only the SHA-256 of the request file as the authority received it, which the applicant can recompute and nobody else can attach a name to.
How it changes. Append-only. An entry is committed the day of the event and published with the next public release of the source tree; the chain shows the record itself at once. An error is corrected by a new entry that names the entry it corrects; no entry is edited or removed.
Columns
| Column | Value |
|---|---|
date | the day of the event, UTC, YYYY-MM-DD |
event | one of the events below |
tier | permissionless or admitted |
operator_account | the record’s operator account (bech32); — on a refusal |
origin | the exact origin of the binding; — on a refusal |
public_display_name | as the registry holds it; — on a refusal |
operated_by | — when the business runs its own verifier service; otherwise the name of the operator of the service, as its published deployment record states it |
release | the release the verifier service of the single-node production chain reports in GET /v1/build-info on that day |
reason | a reason code below; — where none applies |
tx | the transaction hashes (funding, then registration or renewal) on the permissionless tier, the proposal ids on the admitted tier and for every state edge |
commitment | for identity_renewed and responsible_person_replaced: the new commitment hex and its issuer id, <commitment_hex>@<issuer_id_hex>; — otherwise |
request_sha256 | on a refusal or an appeal against one: the SHA-256 of the request file; — otherwise |
Events and reason codes
| Event | Meaning |
|---|---|
admitted | the record is ACTIVE: self-registered after the funding (permissionless), or registered and activated by two proposals (admitted) |
refused | the request did not meet the policy |
origin_renewed | an origin’s revalidation window was renewed |
identity_renewed | the responsible person’s identity check was renewed from that person’s renewal session; the chain record keeps the commitment of the first admission |
responsible_person_replaced | a new responsible person, identified in a fresh session; the record, the origin and the verifier id do not change |
monitoring, suspended, reinstated, revoked | the registry edge of that name |
appeal | the written answer to an appeal: upheld or reversed in reason, after a slash, with the code it concerns |
correction | corrects the entry named in reason (its date and event) |
Reason codes: not_registered_business, identity_check_missing, evidence_not_ok, obligations_not_accepted, request_invalid (refusals); revalidation_lapsed, key_compromise_reported, evidence_not_served, court_order, r18_breach, verifier_request (state edges); cause_remedied, appeal_reversed (reinstatements).
Entries
The records written at the chain’s genesis (the operator’s own issuer and verifier) were not admitted under this policy and are not listed; they are readable on chain.
| date | event | tier | operator_account | origin | public_display_name | operated_by | release | reason | tx | commitment | request_sha256 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| No entry yet. | |||||||||||
How a verifier is admitted, and what it accepts in doing so, is on becoming a verifier.