URUZ VM

Current
Capabilities

URUZ VM already has meaningful runtime and operational capabilities in local and devnet environments. This is not a roadmap. These are working systems.

OPERATIONAL IN LOCAL / DEVNET
01

Core Runtime Capabilities

Runtime surfaces that are already exercised in local and devnet operation.

01

Aptos Execution Integration

Execution-side reads, event observation, and mint/burn flow handling.

  • Real-time event stream observation
  • Mint transaction submission and confirmation
  • Burn event detection and processing
  • Execution state reads from on-chain data
02

Kaspa Settlement Integration

Settlement-side reads, deposit observation, finality evaluation, and release path planning.

  • UTXO-based deposit detection
  • DAG finality evaluation with confirmation depth
  • Release transaction construction
  • Settlement state reconciliation
03

Event-Driven Execution Confirmation

Real execution progression driven by canonical execution events, not just submit acknowledgements.

  • Canonical event sequence validation
  • State machine driven by actual chain events
  • No false-positive confirmations
  • Audit-ready event trail
04

Polling and Runner Lifecycle

Looped execution, release, and settlement observation with health tracking and backoff discipline.

  • Configurable polling intervals
  • Automatic backoff on failures
  • Health status reporting
  • Graceful shutdown handling
05

Progression Metrics and Flow Inspection

Flows, phases, metrics, and inspection surfaces are already available.

  • Per-flow phase tracking
  • Progression rate metrics
  • Latency measurements
  • Full flow inspection API
06

Reconciliation and Drift Detection

System compares registry, execution evidence, settlement evidence, and phase derivation.

  • Cross-boundary state comparison
  • Drift detection and alerting
  • Mismatch categorization
  • Reconciliation audit logs
02

Operational Readiness

What "operationally usable" means in practice. These are not planned features. This is the current operational surface.

active

API Health

All read endpoints operational with latency tracking and availability monitoring.

active

Loop Health

Continuous monitoring of execution, release, and settlement loops with failure detection.

monitored

Progression Metrics

Real-time tracking of flow throughput, phase transitions, and completion rates.

active

Bridge Flow Inspection

Full visibility into individual flow states, phases, and audit trails.

monitored

Mismatch Visibility

Reconciliation findings surfaced with severity classification and context.

active

Runtime Discipline

Controlled bring-up and shutdown with state preservation and clean handoffs.

URUZ VM is not just a specification. It is a running system with operational monitoring.

03

Real Flow Coverage

The complete flow that is already being exercised in local and devnet environments.

SETTLEMENT
EXECUTION
BRIDGE
01

DEPOSIT_DETECTED

UTXO observed on Kaspa

SETTLEMENT
02

DEPOSIT_FINALIZED

DAG finality confirmed

SETTLEMENT
03

ATTESTATION_READY

Evidence prepared for execution

BRIDGE
04

MINT_SUBMITTED

Mint transaction sent to Aptos

EXECUTION
05

MINT_CONFIRMED

Mint event observed on-chain

EXECUTION
06

BURN_OBSERVED

Burn event detected on Aptos

EXECUTION
07

RELEASE_SUBMITTED

Release transaction sent to Kaspa

SETTLEMENT
08

RELEASE_CONFIRMED

Release finality achieved

SETTLEMENT
8
STATES
3
PHASES
OPS
VISIBLE
04

Boundary Maturity

Clean separation of concerns with well-defined boundaries. Each boundary owns its domain.

ESTABLISHED

Coordinator

Central orchestration of flow lifecycle and state transitions.

  • Flow state machine management
  • Phase transition coordination
  • Cross-boundary event routing
ESTABLISHED

Execution Adapter

Aptos-specific integration for execution-side operations.

  • Mint/burn transaction handling
  • Event stream observation
  • Execution state reads
ESTABLISHED

Settlement Adapter

Kaspa-specific integration for settlement-side operations.

  • Deposit/release detection
  • DAG finality evaluation
  • UTXO management
ESTABLISHED

Reconciliation Worker

Continuous state comparison across all boundaries.

  • Registry vs evidence comparison
  • Drift detection and reporting
  • Mismatch categorization
ESTABLISHED

API / Read-Only Inspection

External visibility into system state without mutation.

  • Flow inspection endpoints
  • Metrics exposure
  • Health status APIs
MATURING

Release Service

Dedicated boundary for outbound settlement operations.

  • Release transaction construction
  • Confirmation tracking
  • Settlement finality monitoring
05

Practical Value

Why these current capabilities matter for building and validating URUZ infrastructure.

Faster Iteration

Real runtime with real observability means faster development cycles. See exactly what happens at each step without guessing.

Safer Operational Validation

Test operational scenarios in local/devnet before touching mainnet. Validate edge cases and failure modes safely.

Better Debugging

Full flow inspection, audit trails, and reconciliation visibility make debugging tractable instead of speculative.

Cleaner Environment Bring-Up

Structured runtime bring-up and shutdown with health checks. No manual coordination or fragile startup scripts.

Confidence Before Integration

Build confidence in the runtime behavior before deeper URUZ integration. Reduce risk incrementally.

URUZ VM is already operationally meaningful, even while the broader URUZ stack is still maturing.

This is not a promise of future capability. This is working infrastructure that enables real development, testing, and operational validation today.