RUNTIME VALIDATION STACK
URUZ

VM

Bridge and runtime stack for validating DAG execution flows. Operational observability while the chain and VM mature.

APT
Execution
KAS
Settlement
OPS
Visible
SCROLL
WHAT IT IS

A bridge runtime that validates execution before the chain does.

URUZ VM is a validation runtime that bridges Aptos execution with Kaspa settlement. It provides real-time observability into DAG execution flows, ensuring every state transition is traceable, verifiable, and reconcilable.

While the URUZ chain and native VM mature in parallel, this runtime stack establishes the operational foundation: execution confirmation, progression tracking, mismatch detection, and full audit visibility.

EXECUTION
Aptos

Smart contract execution boundary

SETTLEMENT
Kaspa

DAG-based final settlement layer

VALIDATION
URUZ VM

Runtime observability and reconciliation

ARCHITECTURE PRINCIPLES

Built on clear separation of concerns.

01

Coordinator Owns Orchestration

The coordinator is the single source of truth for flow progression. All state transitions flow through explicit orchestration.

02

Contracts Stay Execution-Boundary Focused

Smart contracts handle execution logic only. No coordination complexity bleeds into on-chain code.

03

Canonical Mapping First

Every flow has a canonical identifier. Cross-chain state is mapped deterministically before execution.

04

Observability First

Every state transition is logged, timestamped, and queryable. No silent failures, no hidden state.

05

Reconciliation is Observational

Mismatch detection reads state. It never mutates. Reconciliation surfaces truth without forcing it.

06

Health, Loop Health, Flow Truth Are Separate

System health, loop lifecycle, and individual flow state are distinct concerns with distinct surfaces.

CURRENT CAPABILITIES

Operational runtime surfaces, already exercised.

These capabilities are live in local and devnet environments. Each represents validated, operational functionality rather than roadmap speculation.

LOCAL/DEVNET VALIDATED

EXECUTION LAYER

  • Aptos execution integration
  • Event-driven execution confirmation
  • Transaction lifecycle tracking
  • Smart contract state observation

SETTLEMENT LAYER

  • Kaspa settlement integration
  • DAG finality detection
  • Cross-chain state mapping
  • Settlement confirmation tracking

RUNTIME OPERATIONS

  • Polling and runner lifecycle
  • Loop health monitoring
  • Graceful shutdown handling
  • Recovery state persistence

OBSERVABILITY

  • Progression metrics dashboard
  • Reconciliation visibility
  • Mismatch detection and alerting
  • Full audit trail inspection
RUNTIME FLOW

Eight states. Complete visibility.

Every flow progresses through deterministic states. Each transition is observable, auditable, and recoverable.

01
DEPOSIT DETECTED
initiation
02
DEPOSIT FINALIZED
initiation
03
ATTESTATION READY
validation
04
MINT SUBMITTED
execution
05
MINT CONFIRMED
execution
06
BURN OBSERVED
settlement
07
RELEASE SUBMITTED
settlement
08
RELEASE CONFIRMED
settlement

RUNTIME OBSERVABILITY

Health
System-wide operational status
Loop Health
Individual runner lifecycle state
Progression Metrics
Flow completion statistics
Flow Inspection
Deep state examination tools
Mismatch Visibility
Reconciliation anomaly detection
ROADMAP

Building toward production.

Disciplined milestones based on architecture, runtime behavior, and integration readiness.

Local/Devnet Bring-up

Runtime, health, and inspection surfaces established in local/devnet operation.

Real Execution Path

Aptos integration with event-driven confirmation

Real Settlement Read Path

IN PROGRESS

Kaspa DAG state observation and finality detection

Recovery Hardening

Crash recovery and state persistence guarantees

Release Primitive

Complete settlement flow with release execution

URUZ Devnet Integration

Native chain integration milestone