Settlement infrastructure · CAGE 17ZE9

I don't ask you to trust the number. I hand you the harness.

Security researcher and settlement-infrastructure engineer. I build ledgers that prove their own integrity — and I publish the benchmarks, including the ones that don't flatter me.

See the measurements Work with me
acre — integrity check · live output
The proof
Real numbers, measured on real hardware.

Every figure here came off a benchmark you can run yourself. Nothing is asserted; everything is timed. That includes the result that argued against my own instinct.

SQLite in-process, single node
21,485 tps
PostgreSQL decoupled, concurrent
4,739 tps
// I expected to need the heavier database. I benchmarked it anyway. SQLite won — so I shipped the simpler engine, and I'll move to Postgres the day I actually outgrow one machine. Not before.
THROUGHPUT
21,485 /s

Settlements per second on a single node, measured — not modeled. Batching pushes it higher.

CONSERVATION
0 cents lost

Double-entry, verified. Opening and closing balances reconcile exactly, every run, or the run is rejected.

TAMPER-EVIDENCE
SHA-256

Hash-chained history. Any edit to a past transaction or balance breaks the chain and is caught on verify.

Integrity
A ledger that checks its own work.

The engine records transfers in a double-entry ledger, chains each committed batch to the last with SHA-256, and can replay its entire history from the opening state to confirm every balance. Tampering doesn't hide — it surfaces the moment anyone re-runs the check. For counterparties, the chain head can be anchored outside the operator's own reach, so integrity holds even against the operator.

Honest scope
What it is. What it isn't.

Precision is the product. Here's exactly what's built and demonstrable today, and what I won't claim until it's true.

// BUILT & DEMONSTRABLE

  • Measured settlement throughput on real hardware, reproducible
  • Tamper-evident ledger — edits to history or balances are detected
  • Self-verifying integrity — replay confirms conservation to the cent
  • Grey Liquidity Orchestrator — autonomous reserve-ratio and rail-spread management

// NOT CLAIMED (YET)

  • Not fully autonomous arbitrage — requires manual liquidity-threshold monitoring
  • Not distributed consensus — single-node integrity, stated plainly
  • Not a license — built for licensed operators, who stay accountable
  • Not custodial — the design does not hold your keys or your funds

Building settlement rails for licensed operators.

Bug-bounty and vulnerability research, ledger and payment-rail architecture, and integrity engineering — under CryptoFreight LLC, federally registered, CAGE 17ZE9.

[email protected] josephvasapolli.com