Skip to content
P‑AIProject‑AI
Trust Spine · /keys

Declared audit verification key

This page renders the complete public-key record used by the receipt verifier and by the signer's fail-closed key-pair check. Deployment-private-key pairing remains a separate runtime fact.

PAI-006 · Unverified / Implemented
Current build declaration
Key id
pai-30f1e1db82b2
Algorithm
Ed25519
Raw public point
BPFt7TXnsEPv4ClkPrGwyplPC89_733ZVCcr7_PUq2M
SPKI SHA-256 fingerprint
sha256:438aced9df88bb70d920a503c823c19b33be7fd8c7a52efbabd04295bf5c34a1
Evidence status
The verifier derives this complete fingerprint again before accepting the key, and the signer rejects a configured private key whose public half differs. This page does not prove which secret is deployed.
Ed25519 public key · SPKI PEM
-----BEGIN PUBLIC KEY-----
MCowBQYDK2VwAyEABPFt7TXnsEPv4ClkPrGwyplPC89/733ZVCcr7/PUq2M=
-----END PUBLIC KEY-----

The complete PEM, raw point, key id, and fingerprint come from one trust-registry module. Receipt-v1 signatures cover the UTF-8 lowercase receipt_hash text.

Executable receipt vectors
npm exec -- vitest run tests/receipt-verifier.test.ts tests/signing.test.ts

Run from a dependency-installed clone. The fixtures cover valid, tampered core/hash/ signature, unknown-key, malformed-timestamp, and broken-chain cases.

Verification boundary

The local verifier checks strict receipt-v1 structure, canonical-core SHA-256, the declared key fingerprint, Ed25519 signature, UTC timestamp syntax, and an optional previous-hash link. It does not prove ledger membership, timestamp freshness or authority, deployment-private-key pairing, or semantic correctness.

  • • No RFC 3161 timestamp token or timestamp-authority root is declared.
  • • No warrant-signing key or PGP disclosure key is established here.
  • • No validity window, revocation feed, or verified rotation history is declared.