Trust & evidence
Evidence that holds up after the fact
Every decision is sealed with exactly what it was based on and anchored in a block. If anyone changes the record later, verification says so.
Recorded with every decision
The full picture, sealed
An audit record is written for every evaluated event, allowed or refused. Its integrity hash is SHA-256 over a canonical JSON encoding, so the same content always produces the same hash, however a database stores it.
- Entity snapshot. The record as it stood at the moment of the decision: a shipment's custodian and seal, a vendor's verified accounts, a policy's insured parties, an order's payment method.
- Event snapshot. The handoff, payment, claim, refund or application payload as received.
- Ruleset snapshot. Name, version, condition and consequence of every rule evaluated.
- Fraud context. Watchlist matches and recent history for every identity in the event, computed by Omnareth, not the client.
- Anchor receipt. The block and transaction holding the hash, decision id and decision status.
Tested against insiders
What verification reports when someone edits the database
We edited stored records directly, the way someone with database access could, and asked Omnareth to verify them. Choose a change to see the result we got.
Fails verification
Trust model
Where the guarantees end
Tamper evidence is only as strong as its weakest assumption. Here are ours, so deployments can be designed around them.
Who takes part matters
The Omnareth chain accepts records through PACT Protocol, Habify Labs' Proof-of-Activity consensus. Anchoring proves the decision database was not edited after the fact. To hold up against the operator itself, include independent parties in the network.
Decisions follow the data
Seal numbers, driver ids and tracker readings come from your systems and devices. Omnareth refuses inconsistencies; it cannot detect a lie that is consistent everywhere.
Your system records transfers
Omnareth does not move custody or money itself. Your system of record updates the entity after an allowed action, and only then.
Fraud memory is per deployment
Repeat fraud is recognized across the shipments, vendors and other entities Omnareth sees, by the identifiers your systems report. Watchlists are not shared with other organizations, and an impostor who changes driver ID each time is refused but not linked.
Pilot program
Prove it on your own operation in 90 days
One lane, facility or process, in shadow mode, with results measured against criteria we agree with you. Qualified companies and organizations can apply.