The data owner. The key never leaves this card.
Field notes · 01 / Private computation
Keep a secret.
Show the work.
Explore a guided simulation, then inspect the public commitments and receipt of a recorded Nibiru run. The viewer keeps private program and input material hidden. It displays a retained export; it does not execute a new encrypted workload or freshly verify a proof.
A small experiment in keeping a secret.
- custody
- execution
- proof
- settlement
- recovery
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 belowRuns the job on ciphertext. Never holds the key, never sees the data.
- enc.load
- fhe.add
- fhe.mul
- fhe.rotate
- repack
- fold
- verify.prep
peeks: 0 · bytes learned: 0
Checks the receipt without the data, the key, or the provider's cooperation.
Below is the real thing: a retained run from a signed Nibiru build, step by step, with its public surface and receipt.
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.
The sensitive parts stay private.
The system runs the job without opening the underlying material.
The result comes with a receipt others can verify.
Two sides can participate without either revealing its private inputs.
Live Instance
Nibiru Engine run
Selected Step
Step 0
-
-