---
title: "Transparency log | KYE Protocol™"
description: "KYE Protocol™ publishes its own signed self-governance runs and verifies them against one published Ed25519 key: what is logged, how to verify it offline, and where operators read the full feed."
url: https://kyeprotocol.com/transparency/
lang: en
source: "KYE Protocol"
---

> KYE Protocol™ publishes its own signed self-governance runs and verifies them against one published Ed25519 key: what is logged, how to verify it offline, and where operators read the full feed.

Transparency

# The protocol governs itself.

Every privileged action against the KYE™ codebase emits the same signed evidence-pack family KYE™ asks every customer to emit, and anyone can verify it offline from the published key.

2 · The receipts

## IP-safe, signed, publicly verifiable.

Three live transparency surfaces. None disclose a KYE™ mechanism — only the canonical envelopes the protocol's clients consume. The proprietary track stays intact; the audit story stays auditable.

### Self-governance run log

Every signed self-governance run published with its decision-map id, evidence-pack id, replay-proof id, signing key id, git SHA, and drift / replay-equivalence flags. `/self-audit-runs/index.json`

### Reference envelope fixture

Three signed JSON artefacts — a self-audit run record, an engine-health snapshot, an audit-chain integrity check — signed with EdDSA over a canonical payload. Drop-in verifier; 30-line Python / Go equivalent. No mechanism content. [trust-self-audit.html](https://kyeprotocol.com/trust-self-audit/) · `trust/self-audit/self-audit-run.json`

### Public verification key

Single Ed25519 public key — everything in this transparency log verifies against it. Per-run public keys also published in each run directory under `public-key.jwk` so rotation is observable. `trust/self-audit-jwks.json`

3 · Verify it yourself

## Two commands. No further dependency on us.

The fixture is small enough that a Python or Go verifier fits in 30 lines. The drop-in JavaScript verifier is in the public mirror.

```
# 1) Fetch the canonical verifier from the public mirror.
curl -fsSL https://raw.githubusercontent.com/KYE-Protocol/app/main/scripts/verify-self-audit.mjs -o /tmp/verify-self-audit.mjs

# 2) Run it against the live transparency log.
node /tmp/verify-self-audit.mjs

# Output (abridged):
#   Loaded JWKS — 1 key(s): kye:key:self-audit-fixture-2026-05
#   ✓ self-audit-run.json       alg=EdDSA kid=kye:key:self-audit-fixture-2026-05
#   ✓ engine-health.json        alg=EdDSA kid=kye:key:self-audit-fixture-2026-05
#   ✓ audit-integrity-check.json alg=EdDSA kid=kye:key:self-audit-fixture-2026-05
```

For each artefact: parse JSON, extract `payload` and `signature`, canonicalise `payload` (sorted keys, no whitespace), base64url-decode `signature.sig`, look up `signature.kid` in the JWKS, and verify EdDSA. No KYE-specific cryptography — vendor-documented primitives only.

## Where to read it

[Public The protocol governs itself Self-governance runs, the reference envelope fixture, the commands to verify.](https://kyeprotocol.com/self-governance/) [Public Self-audit fixture Publicly verifiable proof of mechanism.](https://kyeprotocol.com/trust-self-audit/) [Public Trust center Live receipts, signed evidence, open verifier.](https://kyeprotocol.com/trust-center/) [Admin (owner) Transparency log The operator view of the log, behind sign-in.](https://kyeprotocol.com/admin/transparency/) [Admin (owner) Full feed Every entry, behind sign-in.](https://kyeprotocol.com/admin/transparency-log/) [API GET /api/v1/transparency The admin contract the views call.](https://kyeprotocol.com/developers/api/admin/)