Price a European option book and verify the run.

Public demonstration boundary

Who it is for

Quantitative, trading, risk, and financial-infrastructure teams that need a defined book priced the same way, with a receipt they can keep. Also useful to regulated-computing groups that want a small, inspectable binary rather than a service stack.

Downloads

Binaries and the example book live in the public LuxiDemo repository. These are the current published files.

There is no macOS GPU binary. The CUDA build needs a live NVIDIA driver. Binaries are unsigned: on macOS, right-click the file and choose Open the first time.

How to try it

# Mac CPU
chmod +x luxi-book-macos-arm64
./luxi-book-macos-arm64 price --book example_book.csv --out report.csv --receipt receipt.json

# Linux CPU
./luxi-book-linux-x86_64 price --book example_book.csv --out report.csv --receipt receipt.json

# Linux CUDA
./luxi-book-linux-x86_64-cuda price --book example_book.csv --out report.csv --receipt receipt.json --mode gpu

Full download notes and checksums: demo page.

Public example-book receipt check across five machines

Running the published example_book.csv through the published v0.2.1 binaries on August 16, 2026 produced the same output hash on every machine tested, on the LuxiBook CPU and CUDA pricing paths. This is an internal LuxiBook measurement, not Risk State Engine evidence.

Every row is one physical machine with its own install key. The published folder preserves all 20 signed receipts from the original two-book matrix. Each machine's compute capability is recorded in its receipt. Apple Silicon has a published binary and was covered by an earlier check, but it is not part of this matrix; there is no macOS GPU binary.

# pip install cryptography
import base64, json
from cryptography.hazmat.primitives.asymmetric.ed25519 import Ed25519PublicKey
from cryptography.exceptions import InvalidSignature

with open("receipt.json") as f:
    data = json.load(f)

# Receipt blob layout: 5-byte header + 32-byte pubkey + 64-byte Ed25519 sig
s      = data["receipt"][len("lxq2_"):]
pad    = (-len(s)) % 4
raw    = base64.urlsafe_b64decode(s + "=" * pad)
pubkey = Ed25519PublicKey.from_public_bytes(raw[5:37])
try:
    pubkey.verify(raw[37:], data["payload"].encode())
    print("PASS: signature valid")
except InvalidSignature:
    print("FAIL: signature invalid")

The check that fails

A check that has never been shown to fail cannot be told apart from a check that cannot fail. So here it is failing. We rebuilt a book of 11,317 real executed BTC option trades from one past trading day, priced and sealed it, then changed a single implied volatility in the fifteenth significant digit in one row and verified the altered book against the original receipt.

[OK  ] signature: Ed25519 ok
[FAIL] input_sha256: MISMATCH - book file differs from what was signed
[FAIL] output_vector_sha256: MISMATCH - re-price produced a different vector
[OK  ] book_price_bits: bits match re-price
[OK  ] mode: payload=cpu verify_mode=cpu

RESULT: FAIL - do not trust this receipt for the given book.

Quoted output, with the binary's own long dash rendered as a hyphen. Nothing else is altered.

Reproduce a past trading day yourself

Both books below were rebuilt from a free public venue history API. No account, no key, no data purchase. Executed trades do not change after the fact, so the input can be regenerated on demand rather than accepted on trust: the rebuilt book came back byte-identical to the one sealed earlier.

Both books were also re-run from an empty directory with a fresh key directory. That produced a different install fingerprint, as it must, and the same output hash. Different install, same number, and the receipt records which install asserted it.

# 1. get the published binary and prove it is the published one
curl -fsSLO https://raw.githubusercontent.com/RegularJoe-CEO/LuxiDemo/main/downloads/luxibook/luxi-book-linux-x86_64
sha256sum luxi-book-linux-x86_64
# expect b4c14b9e0ceddf86e7a518d36d9ea48e5d6b07c72c331294a90af2100cc53c29

# 2. rebuild the book from the venue's free public history
python3 build_historical_book.py 2025-02-18 > book.csv
sha256sum book.csv
# expect 7ffb96d4668d7ca795d87888bf99884d0e23653a0bb7ddf6e466d02c2170b39e

# 3. price, then verify
chmod +x luxi-book-linux-x86_64
./luxi-book-linux-x86_64 price --book book.csv --out priced.csv --receipt r.json
./luxi-book-linux-x86_64 verify --book book.csv --receipt r.json

Scripts: build_historical_book.py rebuilds either book from the public history. reproduce.sh runs the whole sequence for both dates, checks every value against the figures above, and then breaks one volatility on purpose so you see the seal react.

Request a paid evaluation

Bring your own book, your comparator, and the hardware you care about. A paid, fixed-scope evaluation measures correctness, determinism, speed, energy, and receipts, then documents the head-to-head.