Nibiru Engine

Private execution with public receipts.

Nibiru runs a committed program over encrypted material and emits a receipt that anyone can verify without learning the private inputs, state, outputs, or program contents.

Open the interactive demo Docs index

The Nibiru shape

1
Data owner encrypts inputs and binds the committed job.
2
Operator runs Nibiru over ciphertext without becoming the trusted party.
3
Receipt proves the committed execution completed correctly.
4
Owner, auditor, app, or chain verifies in the open.

What a receipt binds

Committed program root
Committed initial and final state roots
Semantic transition trace
Public receipt root
Artifact identity used by the FHE-to-ZK bridge

Maturity

A working proof path exists today: encrypted VM smoke execution, semantic receipts, an MPC witness source for bilateral privacy mode, and a redacted public viewer. Larger runtime shapes, release packaging, and production hardening remain underway.