Provable Inference
- Source
- anthropic.com
- Author
- Anthropic research
- Date

Context
Anthropic's FlashProve lets someone check that a specific AI model produced a response without seeing the model's weights or rerunning it. Today a user cannot tell whether the model they chose actually answered, or whether a routing service substituted a cheaper one or an attacker tampered with the output. FlashProve uses a zkSNARK, a type of cryptographic proof: the provider first publishes a commitment that pins down one exact set of weights while keeping them hidden, then produces, for a given prompt and reply, a proof that those committed weights produce exactly those . Anyone holding the commitment, the prompt and the reply can check the proof, and it reveals nothing about the weights, according to Anthropic's research post.
What the post adds is speed. In Anthropic's measurements on Meta's Llama 4 Maverick, a 400-billion-parameter model run with 4-bit weights, a single H100 GPU proves about 110 tokens per second. Each 1,024-token request gets a proof of about 19 MB that a 24-core CPU checks in about 17 seconds. Proving still takes roughly 70 to 95 times the GPU time of serving the same requests with vLLM, a common open-source engine. The only earlier proof of this model the post knows of, VerInf, reports 14.3 hours for 1,000 tokens on a DGX Spark, a different machine, with a 93.6 GB proof that took almost a day to verify. Anthropic says Claude produced the improvements to the proof system and that the top-level security properties are stated and proved in Lean, a formal verification language.
The uses the post describes all depend on someone needing assurance they cannot get from the output alone. Outside evaluators could confirm they are testing the model being served, customers of routing services could confirm they got the model they paid for, a company could detect a compromised inference server, and a regulator could check that only approved models are served or that hardware is really running inference. The post is careful about that last case: proving that hardware served inference does not show it was not also training on the side.
FlashProve is a research prototype released under the Apache 2.0 license, and its limits are specific. It proves an exact integer version of the model under greedy decoding, so a reply from ordinary floating-point serving or sampled decoding can depart from what was proved. It handles contexts of only 1,024 tokens, depends on the mixture-of-experts structure, hides the weights but not the architecture, and treats timing side channels as out of scope. The fast C++ verifier meant for daily use carries no formal guarantee; only the slower Lean verifier does. Anthropic also says it met its own September 30, 2026 goal for a provable-inference prototype through a separate project that signs inference traffic and recomputes it on a trusted server, so FlashProve is a second route to the same aim.
- FlashProve, from Anthropic and outside collaborators, generates zero-knowledge proofs that a response came from a committed model, at about 110 tokens/second on one H100 for the 400B-parameter Llama 4 Maverick in 4-bit form, with proofs of about 19 MB per 1,024-token request.
- Proving is costly but checking is cheap: the team measured proving at roughly 70 to 95 times the GPU time vLLM needs for the same requests, while a proof verifies in about 17 seconds on a 24-thread CPU with no GPU and no access to the weights.
- Per the post, the earlier VerInf system proved the same Maverick model at about 0.02 tokens/second with a 93.6 GB proof. One FlashProve design choice: prover work scales with the ~17B parameters each token activates, not all 400B, while still hiding which experts ran.
- The guarantees are narrow for now: proofs hide weights but not architecture, cover an integer version of the model under greedy decoding, and handle contexts up to 1,024 tokens, so sampled or floating-point outputs can diverge. The authors call it a research prototype.
- To make the cryptographic code auditable, the team stated completeness, soundness and zero knowledge in Lean and ships a slow, formally checked Lean verifier beside a fast C++ verifier that carries no formal guarantee but agreed with it on every test proof.
- token — The chunk of text a model reads and writes in — roughly three-quarters of a word — and the unit AI usage is billed in.
- mixture-of-experts — A model built from many specialist sub-networks where only a few activate per token, giving big-model capability at small-model running cost.
- inference — Running a trained model to get answers — the phase where AI is actually used, as opposed to trained.
Checking sign-in…
Loading comments…





