real Ed25519 + BLAKE3, run client-side via WebAssembly
the checking happens on your device, with real cryptography
One answer. Evidence from independent systems. Verified 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 tiny extra cost of proving the answer is genuine. Real measurements, re-runnable from the code.
loading measured numbers…
Each node is checked three ways, its content-id matches its bytes (integrity), its signature is valid (authenticity), and its signer is certified to a trusted anchor whose namespace covers its name (authorization). Each venture has its own anchor and signs its own evidence. The verifier trusts none of them, and there is no central authority.
“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.