Research Labs Request access

Interactive Nibiru Engine

Watch a private machine expose only its proof surface.

This viewer opens a real run from the Nibiru pipeline — encrypted custody, private execution, proof-backed settlement, and recovery. What happened stays sealed; only the public check, its receipt, and whether the run is accepted or rejected become visible. Behind it sits an endurance-qualified demo build: a signed, byte-verified release pack that cleared 100 consecutive transactions over a continuous 24-hour run.

  1. custody
  2. execution
  3. proof
  4. settlement
  5. recovery
Lean 4 Proof theory machine-checked — no gaps · reproducible signed builds · 24 h · 100/100 endurance run
receipt state accepted
public check visible proof trail
private material sealed
shared trust co-checked
Viewer source sample-run.json
private program public check ready 0 / 0

Plain English

What is running here?

Urizen is showing a Nibiru Engine run: private work moves through the system, the private parts stay locked, and the public receipt shows whether the run can be trusted.

1 Locked work

The sensitive parts stay private.

2 Sealed run

The system runs the job without opening the underlying material.

3 Public check

The result comes with a receipt others can verify.

4 Shared trust

Two sides can participate without either revealing its private inputs.

Live Instance

Nibiru Engine MDVM Run

0 steps 0 cells 0 trits
step 0 valid

Selected Step

Step 0

valid transition
State Before -
State After -

Control

Write