Research Labs Request accessAccess

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

Try it — three taps Anansi harness demo

receipt state accepted
public check visible proof trail
private material sealed
shared trust co-checked

Try it · three taps

Seal it. Run it. Check it.

Pick something private, hand it to a provider who can't read it, and let anyone check the answer. Then try to break the receipt.

guided simulation · nothing is decrypted in your browser · the real run record is below
Youplaintext

The data owner. The key never leaves this card.

Providercomputes blind

Runs the job on ciphertext. Never holds the key, never sees the data.

what the provider holds—
  • enc.load
  • fhe.add
  • fhe.mul
  • fhe.rotate
  • repack
  • fold
  • verify.prep

peeks: 0 · bytes learned: 0

Anyoneverifies

Checks the receipt without the data, the key, or the provider's cooperation.

execution receipt · root—

Confidentiality from FHE · integrity from the ZK receipt · the theory behind both is machine-checked in Lean 4.

Below is the real thing: a retained run from a signed Nibiru build, step by step, with its public surface and receipt.

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 run

0 steps 0 cells 0 width
step 0 valid

Selected Step

Step 0

valid transition
State Before -
State After -

Control

Write