Compliance, proven not promised

A cryptographic record of every trade decision, that nobody can quietly rewrite.

Probatum is a hybrid private/public blockchain system that turns trading-desk compliance checks into an append-only, independently verifiable record — so payout disputes end at the proof, not in a meeting.

See how it works Request a walkthrough In active development
root: 4f9a21e0c3...b7e2 · anchored block #19234871 · private chain integrity verified
The problem

Compliance is only as good as the paper trail.

When a payout dispute comes down to "the trader says, the desk says," there's usually no independent way to settle it. Logs can be edited. Spreadsheets get "corrected." Trust runs out exactly when it matters most.

01

Disputed payouts

Traders and desks disagree on whether a rule was followed, with no tamper-evident record to settle it.

02

Editable history

Most compliance logs live in systems where a record can be quietly changed after the fact.

03

Trust, not proof

"We checked" isn't the same as "here's the cryptographic proof we checked." Probatum closes that gap.

Architecture

Private chain, public proof.

Compliance events stay private and on-premise. Only a periodic fingerprint of that history goes public — enough to prove nothing was altered, without exposing trade detail.

Step 1

Private append-only log

Each compliance event is written once to a JSONL chain, sequentially hashed to the previous entry. No edit or delete path exists.

Step 2

Merkle root generation

Batches of records are periodically rolled up into a single Merkle root — a compact fingerprint of everything in that batch.

Step 3

Public L2 anchor

The root is committed to a public chain (e.g. Base or Arbitrum), giving the batch a timestamp no one controls.

Step 4

Independent verification

Anyone holding a record can recompute the hash path and check it against the public root — no need to trust the firm's word.

Security & isolation

Air-gapped by design.

The private chain runs on an isolated machine, reachable only through a controlled interface. Nothing about the compliance log is exposed to the open internet — only the anchored root ever leaves.

Isolated deployment

Runs on a dedicated, network-isolated host behind nginx, with no inbound path to the raw compliance data.

Tamper-evidence, not just access control

Even someone with access to the machine can't edit history without breaking the hash chain — the system would visibly fail verification.

Status

Where things stand.

StageIn active development
Deployment targetIsolated host, managed by us
Anchor chainPublic L2 (Base / Arbitrum — under evaluation)
IP approachTrade secret — architecture isn't published or open-sourced
Get in touch

Want to see a real anchored record?

Probatum is in active development. If you run a prop desk and want to see how this would slot into your compliance process, get in touch.