Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding

FlashProve: proofs of which model answered you

Written November 9, 2026

You cannot tell from the words alone which model wrote a reply. A routing service could swap in a cheaper model, or an attacker could tamper with the token stream, and the output would still read fine. Anthropic's FlashProve attaches a cryptographic proof to the answer — at 70 to 95 times the cost of serving it.

The problem

When you send a request to an AI model today, you have no way of knowing for certain that the model you selected is the one that generated the response. That matters in three cases Anthropic names in its research post: independent evaluators who test models before and after release need to know the model they are evaluating is the model being served; clients using a model through a third-party routing service want assurance the tokens came from the model they paid for; and if an attacker modifies the token stream while pretending to be a given model, the output alone gives no way to detect it. Even publishing chat logs proves nothing — a developer could fake them with a cheaper model.

FlashProve, from Anthropic's Frontier Red Team, is an open-source prototype for provable inference: a system that lets a provider prove a response came from a specific, committed set of model weights, without revealing those weights. The post is dated November 2, 2026; some coverage of the release is dated November 4. The repository itself was created October 30.

What it proves — and what it does not

FlashProve is built on a zkSNARK, a zero-knowledge succinct argument of knowledge. It works in two phases. In the offline phase, the provider publishes a commitment to the model weights — a short fingerprint that pins down one exact choice of weights while the weights themselves stay hidden. In the online phase, the provider produces a proof file with each reply, proving the statement: the committed model produces these output tokens when evaluated. Anyone holding the commitment, the prompt, and the reply can check it, without the weights and with limited compute. A proof file is accepted if it is honest, cannot be forged without breaking widely believed cryptographic assumptions, reveals nothing about the weights beyond what the response itself implies, and is small and cheap to check.

What it proves is origin, not correctness. A proof says the committed model produced these tokens. It says nothing about whether the tokens are true, good, or safe — a correct proof of a wrong answer is still a proof. The model architecture is not hidden either: hiding the weights is the goal; hiding the architecture is not. And a proof does not show the provider's hardware was used only for inference — Anthropic notes that it verifies the hardware is serving inference, not that it is not training on the side.

What it costs

Anthropic measured FlashProve on Meta's Llama 4 Maverick, a 400-billion-parameter mixture-of-experts model in public 4-bit weights, on a single H100 GPU. All figures are Anthropic's measurements:

MeasureFigure
Proving speedAbout 110 tokens per second on one H100
Proof sizeAbout 19 MB per 1,024-token request
Checking a proof17 seconds on 24 CPU threads (21 seconds on one thread), no GPU needed
Overhead vs plain inferenceAbout 70–95 times the GPU time vLLM takes for the same requests
Commitment downloadAbout 6.5 MB, once
Offline phaseAbout 39 minutes, once per model; the commitment is good for about 16 million requests

For scale, the only earlier proof of the same model that Anthropic knows of, VerInf, took 14.3 hours for 1,000 tokens with a 93.6 GB proof that took almost a day to check. FlashProve is orders of magnitude faster than that — and still 70 to 95 times slower than serving the model plain. Anthropic frames the release as intermediate progress, not a completed research agenda, and says it has no plans to deploy FlashProve at Anthropic or any other lab.

The limits that keep it a prototype

Who would use it, then? Evaluators and auditors who need to know the model they tested is the model that was served, and regulators who need to check that only approved models are served, without rerunning the model themselves. For everyone else, the honest summary is the one Anthropic gives: a fast prototype that shows provable inference is practical, at a cost no production service would pay today.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Astra did 40% less work on safety tasks · OpenAI: agents tried to escape their sandboxes