Seal Once. Verify Forever.
Tamper-evident sealing that runs anywhere — online, offline, or air-gapped. 48,640 seals per second. Zero trust required.
Core Guarantees
01 Deterministic Hashing
Canonical JSON normalization ensures byte-for-byte reproducibility across any platform, any time.
02 Collision Resistant Binding
Proprietary field binding construction prevents extension attacks and ensures unique cryptographic commitment.
03 Offline Verification
Pure function verification flow requires zero network access. Verify on an air-gapped laptop.
04 Client-Owned Keys
You generate and custody the signing keys. Full data sovereignty. No key escrow.
Advanced Capabilities v2.1
Beyond the seal — the surfaces that make 0REI an evidence system, not just a signer.
01 Merkle Attestation
Binary Merkle tree over seal binding roots. Batch, anchor one root publicly, prove inclusion without credentials.
- SHA-256 tree over binding roots
- Batch size to 10,000 seals
verify_prooffrom (leaf, proof, root)
02 ST3GG Steganography
LSB embedding of seal proofs inside PNG pixels. Verify a seal straight from an image, fully offline.
/seals/embed— write proof to PNG/seals/extract— pull seal from PNG/seals/extract-verify— confirm, no DB
03 Delta Entities
Append-only delta log with advisory-lock sequencing. High-frequency settlement, zero read-modify-write.
- Increment · Decrement · Append · Set
- State materialized on read by replay
- Full delta audit trail per entity
04 Optimistic Concurrency
Per-entity advisory locking with retry policy and structured 409 conflicts. Built-in observability on every transaction.
pg_advisory_xact_lockper entity- Exponential backoff, configurable retries
- attempt / conflict / duration stats returned
05 Pluggable HSM
The HsmSigner trait abstracts hardware signing. Software signing is the default; hardware is a config swap.
- AWS CloudHSM reference path
- Azure · Thales Luna · YubiHSM · PKCS#11
- FIPS 140-2 L3 pathway (integration, not validated)
06 Genesis Anchor
A signed, version-controlled origin seal committed at bootstrap. Every seal traces lineage to a verifiable day zero.
- Signed with the deployment's Ed25519 key
- Committed to source control
- Tamper surfaces as a signature mismatch
How It Works
Four steps from event to courtroom-grade evidence.
Capture
Your application emits an event — API call, transaction, file change, or sensor reading.
Canonicalize
RFC 8785 deterministic JSON serialization eliminates ambiguity. Same input always produces same output.
Seal
SHA-256 content hash bound to Ed25519 digital signature. Cryptographically tamper-evident in 0.022ms.
Deliver
Evidence Packet with standalone verification proof. Verifiable offline, forever, by anyone.
The Evidence Packet
The Evidence Packet is the product. Everything else is the factory that produces it.
Contents
core/ canonicalized payload
core/ cryptographic manifest
proof/ standalone verification tooling
proof/ pre-computed verification proof
docs/ technical specification
If an auditor cannot verify it on a laptop with no internet, it is not evidence.
Integration Surfaces
Kafka
Ingest events from existing streams and seal them as they flow. Zero-copy integration with your message bus.
HTTP API
POST payloads directly for sealing with deterministic hashing and binding. Simple REST interface.
Rust Crate & CLI
Embed the orei crate directly in your services, or ship the standalone 0rei-verify binary. Seal and verify in-process — no HTTP, no server, no network.
Supabase Bridge
Four Deno edge functions seal Supabase events at the source — table writes, storage objects, scan results — with a scheduled retry handler for transient failures.