GitHub Devnet Live
Devnet live — private infrastructure

Finality
forever.

URUZ is a DAG-based Layer 1 blockchain where finality is secured by cryptographic work — not by trusted validators, staking oligarchs, or committees.

Explore the Protocol View Roadmap →
URUZ
Live
DAG status
Distributed
Node set
Adaptive
Network params
Measured
Devnet latency profile
Current
Build track
DAG-native ✦ Work-weighted finality ✦ Post-quantum · Dilithium ✦ Structural Graph Identity ✦ Post-quantum native ✦ No staking required ✦ Built in Rust ✦ Uruz DAG protocol ✦ Adaptive F · M · K ✦ SGI Sybil resistance ✦ DAG-native ✦ Work-weighted finality ✦ Post-quantum · Dilithium ✦ Structural Graph Identity ✦ Post-quantum native ✦ No staking required ✦ Built in Rust ✦ Uruz DAG protocol ✦ Adaptive F · M · K ✦ SGI Sybil resistance ✦
Protocol

How URUZ works.

The Uruz DAG replaces the single-chain bottleneck with a parallel graph structure. Every vertex references multiple parents, enabling concurrent emission and deterministic, work-weighted finality.

Directed Acyclic Graph
Vertices reference multiple tips simultaneously. Parallel emission creates a dense, fork-tolerant graph that converges without a coordinator.
// Uruz DAG · petgraph
Work-Weighted Finality
Transactions reach FINAL state through a multi-factor finality rule that combines cumulative work, conflict separation, graph depth, and broad participation.
// Adaptive F · M · K
Post-Quantum Checkpoints
Certified checkpoints use ML-DSA (FIPS 204 / Dilithium). Quantum-resistant signatures anchor the canonical chain and prevent long-range reorgs.
// pqcrypto-dilithium · Genesis anchor
Structural Graph Identity
Sybil resistance from verifiable behavioral patterns in the DAG — work, backlink diversity, consistency. No external capital or trusted authority.
// SGI \u00b7 phased reputation model
Adaptive Parameters
Finality parameters adapt to network conditions with bounded updates and hard safety floors, keeping security constraints stable under load variation.
// Adaptive telemetry + smoothing
17-Vector Security Model
Security controls are formally specified and activated in phases from devnet through mainnet readiness.
// Security Specification v1.3
Deep Dive →
Finality Model

From pending to final.

A transaction's status is determined by four on-chain parameters. No oracle. No committee. No clock.

PENDING
Transaction propagating through the DAG. Awaiting sufficient descendant work accumulation.
Below finality threshold
CONFIRMED
Winner of its conflict set with sufficient score. Safe for most applications and exchanges.
Conflict winner under finality policy
FINAL
Irreversible under the protocol finality policy.
All finality conditions satisfied
Devnet

Private multi-node devnet.

Private devnet running across managed VPS infrastructure with continuous health checks and staged security activation.

Network status
● Active private devnet
Health monitored continuously — staged recovery procedures in place
DAG state
Live
Multi-fork at tips is normal under parallel emission and converges under protocol rules
Latency profile
Measured
Continuously measured through telemetry and anomaly monitoring
Version history
CoreBootstrap integrity and recovery hardening
SyncAutomatic catch-up and convergence improvements
SecurityCheckpoint and attestation protections in phased rollout
CurrentContinuous hardening and telemetry-driven tuning
Comparison

How URUZ stacks up.

PropertyURUZEthereumSolanaIOTA
Fixed Validator Set✓ None✗ Yes✗ Yes⚡ Partial
Staking Required✓ No✗ Yes✗ Yes✓ No
Quantum-Resistant✓ Yes (Dilithium)✗ No✗ No✗ No
DAG Structure✓ Yes✗ Linear✗ Linear✓ Yes
Sybil Resistance✓ SGI (behavioral)⚡ Stake-based⚡ Stake-based⚡ Mana
Finality MechanismWork-Weighted DAG FinalityPoS QuorumPoH + Tower BFTCoordinatorless DAG
Build on the
eternal chain.

No validators to bribe. No staking oligarchy. Just mathematics, physics, and open-source code.

Join Testnet Waitlist Explore Technology