Representative frontier receipt

6D Vlasov-Maxwell two-stream instability

Dense-equivalent represented scale in compressed QTT form

← Back to Proof

Represented scale

131,072⁶

5.07 × 10³⁰ phase-space points

Declared hardware

1× H100

single local NVIDIA H100 80GB HBM3

Execution horizon

100 steps

35 m 22 s wall time

Receipt surface

Cryptographic anchoring chain

Run IDVLASOV-6D-NONILLION-20260312-190428

Manifestreceipt_manifest.json

Manifest hash961d61e98d01dfbe6cea8523ab0a101cc3dc0e2af1b3ad49ae87990c45903906

Signature standardML-DSA-44, FIPS 204

Receipt key IDVLASOV-6D-20260312-001

Key commitment SHA-256af19d99c7a36ad35871a644029c00d3906b41eda2132c870acbd9963216e979a

Public key SHA-2565282300c22a525232e53a97728e68617d2dcdc38505ef748a6eff4fff7747dc2

Artifact hashes

Execution artifacts

run_start.json

SHA-256

1894d4b6af278e9d8244e5b5997301365f1ad62c664845154d958aff1f9454a4

vlasov_6d_steps.jsonl

SHA-256

6c741fdf1094186a237e5b936e61a79be3ec0e434e75b61ec3baae0553fad3dd

vlasov_6d_summary.json

SHA-256

70572688a6652300aef35a8d7bfd8b36bc8047abfea30a4d4d1f9a2e4c98db68

Receipt structure

Bundle layout

This public receipt is split into two directories. The public/ directory contains everything needed to verify the trust chain around the receipt itself: public-key fingerprint, key commitment integrity, and the signed manifest. The artifacts/ directory contains the run outputs needed for artifact-hash verification. The included verifier expects exactly that relationship and defaults to proofs/receipt_vlasov/public.

proofs/
└── receipt_vlasov/
    ├── public/
    │   ├── receipt_manifest.json
    │   ├── receipt_manifest.sig
    │   ├── receipt_public_key.bin
    │   ├── receipt_public_key.sha256
    │   ├── receipt_key_commitment.json
    │   ├── key_anchor.json
    │   ├── manifest_timestamp_rfc3161.json
    │   ├── verify.txt
    │   └── verify_receipt.py
    └── artifacts/
        ├── run_start.json
        ├── vlasov_6d_steps.jsonl
        └── vlasov_6d_summary.json

What each file does

public/

receipt_manifest.jsonThe signed record of the run. Carries the run ID, algorithm, key commitment hash, timestamps, hardware declaration, scenario label, represented scale, step count, wall time, conservation metrics, artifact hashes, rank-policy summary, and the explicit claim boundary.

receipt_manifest.sigThe ML-DSA-44 signature over the canonicalized manifest hash. The verification instructions define the canonicalization and expected manifest hash.

receipt_public_key.binThe public verification key.

receipt_public_key.sha256Convenience fingerprint file for manual checking.

receipt_key_commitment.jsonBinds the key ID to the public-key SHA-256 and declares the signing standard as ML-DSA-44, FIPS 204.

key_anchor.jsonAnchors the receipt key to both an RFC3161 timestamp and a git commit. In this run, the anchor records git commit c6d756ff3e7d4c9e4e6a2a07c32c818ab146794b.

manifest_timestamp_rfc3161.jsonThe timestamp artifact associated with the manifest-side trust chain.

verify.txtThe manual offline verification procedure.

verify_receipt.pyAutomates the same checks and looks for artifacts/ beside public/.

artifacts/

run_start.jsonMinimal run declaration: run ID, start time, receipt key ID, key commitment hash, scenario label, and hardware class.

vlasov_6d_steps.jsonlStepwise execution log referenced by the artifact hashes.

vlasov_6d_summary.jsonFinal run summary, including completed steps, wall time, rank, memory, scale, and conservation outputs.

Verification flow

How to verify this receipt

Hash receipt_public_key.bin and compare it to receipt_key_commitment.json.

Hash receipt_key_commitment.json and compare it to the commitment hash in receipt_manifest.json.

Verify receipt_manifest.sig against the canonicalized manifest hash using the public key and ML-DSA-44.

Recompute hashes for the artifact files and compare them to the artifact hashes in the manifest.

Claim boundary

What this receipt proves

This receipt proves cryptographically anchored execution provenance for a bounded frontier run in compressed QTT form. It is not a claim of dense explicit cell materialization. That scope statement is embedded directly in the manifest and repeated in the verification instructions.

Receipts

Every run ships with this structure

The receipt surface is not optional and not configurable. It is the delivery structure around execution. Request Access to receive a live receipt bundle.

← Back to Proof