Blog
The Dual-Pillar essays · every claim checkable, offline
Nine pieces on what it means for an AI agent to trust an address and a verdict without asking anyone’s permission — including ours.
Every platform ships identity and authorization; verifiable evidence is missing everywhere — audit logs locked in the operator's own systems. A minimal, open-source form of evidence anyone can re-verify offline.
Assigned addresses bill an online round trip for every verification. Derivation — SHA-256 of an authority string — makes the address a mathematical fact: deterministic, self-evident, offline. With an honest 128-bit margin ledger.
A fixed-layout, zero-parser attestation envelope: four standing states, revocation as a new envelope, constant-time whole-frame HMAC, fail-closed. REJECT is a result, not an error.
Public vector → structured decode → [PASS] → flip one byte → REJECT. Stateless, fail-closed, fully offline. Install from PyPI, npm, or crates.io — any MCP client works.
The address anchors on a hash; the evidence anchors on a key. Two anchors, one draft, two schemes — interlocked byte-for-byte in the subject shard, closing the loop with no callback.
Read the spec only, any language, fully offline, deterministic. Run all 35 vectors and your name enters the record; they fail and it's our bug, credited to you. Either way, you win.
One blade decides everything: to verify this signature, whose house must you visit? Named specimens (did:web, GitHub "Verified"), three tests — and our own 2^64 birthday ledger, disclosed before anyone asks.
Who issues the first piece of evidence? The anchor lives off the evidence axis, and a standard component carries N creation stories that never adjudicate each other. Openness is not the absence of an origin — it is refusing to monopolize one.
The address is a freehold — landlord: mathematics. Standing is a 120-second lease — landlord: time. What must be permanent goes to math, what must be temporary goes to time; the remaining pillars grow in the stack, not the protocol.