Independent Proof Demonstration

Don't Trust Us.
Verify Us.

SecLog is a trade ledger that emits cryptographic proofs any third party can check offline. No account, no API key, no access to our infrastructure. Pick a hardware profile below, run the verifier in your own browser, then flip one bit and watch the proof collapse.

Run the verifier Download bundle

What This Page Proves, Precisely

Four Cryptographic Facts

A SecLog proof bundle is a small JSON artefact — about 1 KB — plus one Ed25519 public key. Together they demonstrate four facts no amount of operator tampering can fake.

01 · Existence

The Record Existed

Hashing the record with BLAKE3 and walking the Merkle path reconstructs the block root byte-for-byte. Any change to the record breaks this.

02 · Sealing

The Block Was Sealed

The reconstructed root is signed with Ed25519 by the operator's published key. The signature cannot be forged without that key.

03 · Anchoring

The Tip Was Witnessed

A chain of block roots leads from this block to a payload that was published to independent witnesses at a point in time and itself signed.

04 · Interlock

All Of It, Or None Of It

The four checks are interlocked. Flipping a single bit anywhere — record, proof, signature, chain — causes at least one check to fail. Partial tampering is not possible.

Boundary

What This Does Not Prove

That the record is true. That's the job of the exchange feed this record was normalised from. SecLog proves durability, not correctness.

Requirements

What You Need To Verify

BLAKE3, Ed25519, and the public key. Nothing else. No SecLog code is touched during verification, in this browser or in the Python script.

Live Verifier

Run It In Your Browser

Each bundle below was produced by a real SecLog run on the indicated hardware. Pick a profile — the verifier fetches that bundle and checks it live in your browser using two audited libraries: @noble/hashes (BLAKE3) and @noble/ed25519.

Status
Loading bundle…
Public Key (Ed25519)
Block Root (BLAKE3)
Record (Hex)
Block Signature (Ed25519)
Witness-Anchored Root
Merkle Depth
levels
Chain Length
links
Press Verify to run the four checks in your browser.

Throughput Artefact

Same Engine, Different Silicon

Every bundle ships a timing.json from a 10-million-record run on the hardware in its title. It pins the CPU, core count, kernel, partition layout, and durability mode — a TPS number without that metadata is meaningless, so we don't emit one. Swap profiles above to see the same engine on different silicon.

Records
Appended, sealed, signed, and included in inclusion proofs.
Wall-Clock Elapsed
Single process, all partitions. See durability_mode below.
Sustained Rate
Scales with per-core clock and core count.
Per-Record Cost
Hash + chain update + buffer append, amortised over the block.
Hardware loading…

Reproduce Without This Page

If You Don't Trust The Browser, Don't.

Download the bundle and run the reference Python verifier on your own machine. It's 200 lines, pure standard crypto, and makes no network calls.

01 · Get the bundle

  1. For the profile currently selected above: (~5 KB)
  2. Or the individual files:
  3. Shared across all profiles: verify_proof.py, index.json

02 · Install deps

  1. pip install blake3 pynacl
  2. Or use the Debian/Ubuntu packages if available.
  3. Zero SecLog code is required — only the two crypto primitives.

03 · Run it

  1. unzip seclog-proof-bundle-<profile>.zip -d bundle/
  2. python3 verify_proof.py bundle/
  3. Tamper mode: add --tamper.
  4. The verifier prints the hardware identity from each bundle's timing.json.
$ python3 verify_proof.py bundle/

SecLog Proof Verifier
==================================================
Libraries: blake3, pynacl (libsodium)

1. Record hash + inclusion proof (12 levels):   PASS
2. Signature (Ed25519):                          PASS
3. Anchor signature (Ed25519):                   PASS
4. Chain integrity (5 links):                    PASS

==================================================
VERDICT: VALID

Throughput: 10,000,000 records in 2122ms = 4,711,515 records/sec
  measured on: AWS Graviton4 (Neoverse V2) — EC2 c8g.8xlarge (ca-central-1) (aarch64, 32 cores, linux 6.12)
  config:      partitions=8, trades_per_block=4096, durability=none

Content Boundaries

What This Site Deliberately Leaves Out

Everything on this page is shareable with anyone — regulators, prospects, the public. The following is discussed only under NDA, because it reveals either a non-obvious engineering lever, a non-public commercial choice, or information about a specific customer.

Next Step

Have A Harder Proof In Mind?

We can produce bundles against your own data, under NDA, on short notice — a specific symbol, date range, counterparty-identifier redaction profile, or a benchmark on your reference hardware.

Request a custom bundle