UVRN

Portable proof for the open web.

UVRN is the lightweight verification protocol that powers verifiable receipts—receipts that flow freely until you decide to block (canonize) them.

Core Idea

“Proof that flows. Block it when it matters.”

UVRN replaces heavy ledgers with tiny receipts: signed JSON records that prove who did what, when, and with what result.

Each receipt can stay loose (mutable, portable) or become blocked (canonical, permanent).

Tag Examples

Tags act like open-graph hashtags for proof context. They help index receipts across apps, agents, and people.

Each tag can appear in the receipt metadata:

"tags": ["#uvrn", "#drvc3", "#canonized"]

UVRN Protocol Outline

1. Receipt Structure — DRVC3 Schema

{
  "receipt_id": "abc123",
  "issuer": "app.example.com",
  "event": "content.publish",
  "timestamp": "2025-10-06T21:00Z",
  "integrity": {
    "hash_algorithm": "sha256",
    "hash": "sha256:…",
    "signature_method": "eip191",
    "signature": "0x…",
    "signer_address": "0xA9F1…"
  },
  "validation": { "v_score": 92, "checks": {} },
  "block_state": "loose",
  "certificate": "DRVC3 v1.0",
  "replay_instructions": {"service": "app.launcher", "params": {"id": "42"}},
  "tags": ["#uvrn", "#drvc3", "#replayable"]
}

2. Lifecycle (TVC Loop)

TEST → VALIDATE → CANONIZE

• Test System or user emits a loose receipt.
• Validate Cross-checks parity, completeness, freshness → V-Score.
• Canonize (“Block”) – Optionally lock the proof; write to the Canon Log; issue DRVC3 certificate.

3. Endpoints

Delta Engine API (@uvrn/api)

4. Integration Pattern

5. Principles

• Open by default – No proprietary ledger.
• Minimal and verifiable – Store hashes, not content.
• Human + Machine friendly – Readable + executable.
• Selective immutability – Block only what must endure.
• Ethical proof design – Privacy-preserving verification.

6. License

MIT / Open Proof Standard v1.0