Whitepaper v0.2  ·  2026-03-29

URUZ
Protocol

Structural Graph Identity and Post-Quantum Security
for Permissionless DAG Finality.

Network URUZ Layer 1 Architecture Permissionless DAG Security Post-Quantum Forward

URUZ is a permissionless DAG-based Layer 1 protocol combining work-weighted finality, staged reputation-based Sybil resistance via Structural Graph Identity (SGI), checkpoint-anchored history integrity, and post-quantum trust anchors. The central design choice treats SGI as a phased control system — not an all-at-once consensus switch — allowing the network to advance by verified gates rather than narrative milestones.

Core Design

Four Security Layers

Each layer evolves on its own timeline — execution, finality, checkpointing and identity controls are independently upgradeable.

Layer 01
DAG Execution

Parallel transaction propagation and conflict handling in a directed acyclic graph, enabling high-throughput permissionless processing without sequential bottlenecks.

Execution
Layer 02
Work-Weighted Finality

Policy-bounded deterministic finality. Transactions move through states — PENDING, CONFIRMED, FINAL — only when objective on-chain conditions are satisfied.

Finality
Layer 03
Checkpoint Integrity

Canonical history anchoring and controlled recovery. Reputation influence is constrained by anchored history, protecting against long-range manipulation attacks.

Security
Layer 04
SGI — Identity & Influence

Behavior-derived reputation with staged consensus influence. SGI derives identity signals from durable, verifiable behavior in the DAG — no central authority required.

Identity

Layered Stack

Separation is intentional: execution, finality, checkpointing, and identity controls evolve on different timelines.

Layer 01
DAG Execution
Parallel propagation · Conflict resolution
Live · Devnet
Layer 02
Work-Weighted Finality
Policy-bounded deterministic finality
Live · Devnet
Layer 03
Checkpoint Integrity
Anchored history · Controlled recovery
Live · Devnet
Layer 04
SGI — Structural Graph Identity
Staged influence activation · Telemetry-driven gates
In Progress

SGI

Structural Graph Identity

Sybil resistance derived from durable, verifiable behavior in the DAG — no capital requirement, no central registry.

What SGI Measures
  • Contribution and work signals from verifiable DAG activity
  • Diversity-aware referencing patterns across the graph
  • Consistency signals anchored to canonical checkpoint history
  • Longitudinal behavior across epochs — not single snapshots
Why It Works
  • No capital requirement — Sybil cost derives from graph behavior over time
  • Protocol-native: no centralized identity list or oracle dependency
  • Bounded influence prevents manipulation even during early phases
  • Checkpoint anchoring protects against replay of historical reputation

Phased, Not Binary

URUZ treats early network life as a distinct security regime. SGI activation depends on measurable network health, not calendar deadlines.

Phase 01
Observation

SGI signals are collected and scored passively. Influence is bounded. Network health baselines are established over multiple epochs with continuous telemetry.

Phase 02
Bounded Influence

SGI begins contributing to consensus weighting within defined ceilings. Concentration and quality signals are tracked. Maturity gates require multi-epoch evidence.

Phase 03
Full Activation

Full SGI consensus weighting enabled after measurable stability and governance gates are met. URUZ does not claim this phase complete before gates are satisfied.

Transparency

Implementation Status

A truthful snapshot of what is live, in progress, and not yet claimed as complete in this release.

Component Implemented In Progress Not Yet Claimed
DAG Execution & Finality Core flow live on devnet
Checkpoint Integrity Anchored recovery active
SGI Observability Telemetry-driven paths
Multi-Node Devnet Private, automated monitoring
SGI Influence Activation Progressive by policy gates
Post-Quantum Coverage Expanding beyond trust anchors
Key Rotation & Revocation Hardening in progress
Full SGI Consensus Weighting All phases
Full-Stack PQ Enforcement All surfaces
Mainnet Parameter Set Final values TBD

Crypto-Agility by Design

No permanent lock-in to a single primitive. PQ domains are separated to reduce migration risk and avoid partial-PQ blind spots.

Domain 01
Transaction Authentication

Post-quantum signature schemes for transaction-level authentication, aligned with NIST FIPS 204 (ML-DSA).

Domain 02
Consensus Authority

Checkpoint authority paths secured under PQ assumptions, keeping finality integrity robust against quantum-capable adversaries.

Domain 03
Network & Node Identity

Session and node identity paths migrating to PQ-safe primitives, with rotation and revocation hardening on the active roadmap.