/alpha
/beta
/gamma
/delta
real Ed25519 + BLAKE3, run client-side via WebAssembly
the checking happens on your device, with real cryptography
One answer. Evidence across named domains. Declared provenance checked in your browser.
Measured off vs JIT latency per store (localhost floor) and the marginal dollar cost the provenance layer adds, re-runnable with cargo run --release -p prov-bench. Prices are list-price assumptions; this measures verifiable provenance, not correctness.
How fast each system answers, and the measured extra cost of checking its declared provenance. The measurements are re-runnable from the code.
loading measured numbers…
Each node's canonical bytes are checked against its content-id, its Ed25519 signature is checked over that content-id, and its signer is authorized under a consumer-chosen anchor whose namespace covers the name. The demo runs its heterogeneous stacks under one operator, and its configured anchor set represents those local choices rather than separate operators; there is zero global authority. A pass authenticates the bytes and signer-declared lineage, not factual truth or the declaration's faithfulness to an actual computation.
“A waist that only works in one language is just a library; one that spans React/JS and full-stack Rust is a real interoperability layer, the way IP works identically across any OS or hardware.”
The WebAssembly verifying this page is compiled from prov-core, the exact Rust crate the backends sign with. Heterogeneity in (Pinecone/JS, pgvector/JS, Qdrant/Rust, and a deliberately unlike intel feed); one verifiable object out.