Company
0REI Immutable Evidence Systems
We build the tools to seal a record once and let anyone verify it later, on their own machine, with the network unplugged.
Who we are
0REI Immutable Evidence Systems builds cryptographic evidence tools.
A record is sealed once, and anyone, a regulator, an auditor, a court, can verify that seal later, with no network, no database, and no 0REI service running.
The problem
In the generative AI era, digital documents, database writes, execution telemetry, and autonomous agent messages have become trivially forgeable.
Logs, PDFs and database writes are trivially fakeable.
Every incumbent regime relies on an obsolete primitive: trusting the entity that holds the records.
If the vendor suffers a breach or shuts down, the audit trail dies with them.
A check that only runs online is still a check you have to take on trust. The proof has to run on the checker's own machine, with the network unplugged.
A seal proves integrity after sealing. It does not stop a false record being sealed.
What we do
Seal, find, move, prove.
Seal. Evidence Rail turns a record into canonical JSON, hashes it with SHA-256 and signs it with Ed25519. The signing time, signed_at, sits inside the signature, so it can't be changed without breaking the seal. Any later change to the record shows.
Find. Reisuka with Zero Search finds the sealed record on your own machine. Every sealed-record hit carries its proof handle.
Move. TremorFrost Tier 3 is the Rust signed-message bus. It carries live traffic between nodes. The Console reads the bus live.
Prove. The Offline Verifier answers valid or invalid on the checker's machine, with the network unplugged.
The products
Tier 1 is a TypeScript MCP bridge, a separate product from TremorFrost Tier 3. It is not showcased here. It has its own section on the TremorFrost page.
Who it's for
Regulated industries where "the system says so" is not an acceptable answer.
- Financial forensics and settlement reconciliation, and high-volume payments.
- Healthcare provenance and chain of custody.
- Legal evidence chains.
- Regulatory compliance work, including SOX, HIPAA, and GDPR data-lineage.
- Air-gapped environments.
- Autonomous agent communication across financial execution, defense logistics, and enterprise operations.
- Auditors, insurers and regulators who need to confirm sums and ranges over sealed records while the records stay sealed.
- Energy and industrial control, aerospace, telecom, logistics and supply chain, fintech, and defense contractors.
0REI does not name customers, pilots or deployments on this page.
How we work
- Proof, not promises.
- A proof badge is a claim, and it only appears where the record can back it.
- Fail loud. When a dependency is missing, the software says so and fails rather than returning an empty success.
- Every number carries its method and its date.
- Not a blockchain: there's no consensus and no gas.
- We don't escrow or store customer keys.
- It is not a cloud service. It runs on customer hardware.
- Refuse-before-write: uncanonical, unauthenticated or malformed data is rejected before it touches disk.
- A seal proves integrity after sealing; it doesn't stop a false record being sealed.
- Verification does not prove that the data was true when it was sealed, that the key holder is who they claim to be, or that a set of records is complete.
Milestones
| Date | What |
|---|---|
| 2026-08-07 | Signing step: 46,696 signatures/sec, median of 8 runs at commit f002cf2. This is the signing step only, in a loop with no API, no database and no timestamp. |
| 2026-09-01 | TremorFrost change-control chain: 27 records verified as CHAIN INTACT, and 6 of the 27 were countersigned by a second key. That verification was self-rooted, not an independent attestation. |
| 2026-09-11 | Offline Verifier: verdicts on a machine with the network cable pulled, with zero non-loopback connections while each verdict was on screen. Nothing broader than that is claimed. |
| 2026-09-28 | Zero Search load: 1,000 generated test records sealed through the live API and closed into three anchored batches. One bundle from each batch verified VALID offline. A copy with one flipped signature byte came back INVALID. (Test data, labelled generated=true, not customer data.) |
| 2026-10-26 | Full engine: ~547 seals/sec, API + Postgres 16 with fsync on. 1,000 seals in 1.829 s. All 1,005 roots and signatures were rechecked as valid. |
| 2026-11-03 | Research preprint published: Quadratic Residues and the Failure of Zero Knowledge Positivity Proofs over BN254, CC BY 4.0, affiliation 0REI Immutable Evidence Systems. Concept DOI 10.5281/zenodo.23842727. Latest version DOI 10.5281/zenodo.23901653. |
Dated facts only. Method and limits for the two speed measurements are on the Proof page.
Research
The company publishes its research openly.
The latest is the BN254 preprint: Quadratic Residues and the Failure of Zero Knowledge Positivity Proofs over BN254. Preprint, 2026-11-03, CC BY 4.0. Author affiliation: 0REI Immutable Evidence Systems.
The paper shows that a published zero-knowledge positivity circuit is neither complete nor sound over the BN254 scalar field, gives two counterexamples and releases code that reproduces every number.
DOI: 10.5281/zenodo.23842727 (concept DOI; it always resolves to the latest version). Latest version: 10.5281/zenodo.23901653.