A deep dive into the protocol mechanisms behind URUZ — from DAG structure and work-weighted finality to post-quantum checkpoints, adaptive parameters, and Structural Graph Identity.
Traditional blockchains serialize transactions into a linear chain. URUZ uses a Directed Acyclic Graph where each vertex references multiple parent tips simultaneously, allowing concurrent emission by all participants without coordination.
The DAG naturally handles forks: competing vertices are not discarded but accumulated. Finality emerges from work accumulation in descendants, not from a committee choosing a winner.
The protocol is implemented in Rust with a modular architecture focused on deterministic behavior, throughput, and operational resilience.
Finality parameters adapt to network conditions in real time while remaining bounded by strict safety constraints.
Adaptive parameters are estimated from robust network telemetry with outlier resistance and bounded-rate updates.
Startup warm-up logic keeps thresholds stable during node restart and early sampling.
Every checkpoint in URUZ is certified using ML-DSA (Module-Lattice Digital Signature Algorithm), standardised as FIPS 204 — the same algorithm NIST selected as its primary post-quantum signature standard in 2024.
Checkpoint verification is rooted in immutable trust anchors. Snapshot import requires strict integrity checks to prevent poisoned state acceptance.
Bootstrap acceptance requires independent peer corroboration plus anti-abuse rate limiting.
Deployed in current, the bootstrap protection operates in three layers:
Layer 1 — immutable trust anchor verification.
Layer 2 — multi-source consistency checks before accepting state.
Layer 3 — controlled recovery cadence to prevent abuse.
Reputation is derived from verifiable patterns in the DAG itself — not from external capital, hardware, or identity.
Consensus reputation is intentionally slow-moving, so short-term bursts cannot capture meaningful influence.
Diversity filters reduce coordinated behavior inflation and keep influence tied to independent participation quality.
Finality influence transitions are smoothed across windows to prevent one-cycle manipulation.
The security specification defines a structured threat model with phased defenses, telemetry, and response policies.