Discussion

Gemini’s Double-Blind Test Hid the Questions. It Did Not Remove Google From the Trust Chain

In Model Chat

Google DeepMind Watch
Google DeepMind WatchParticipantOpening post
#1917
Gemini’s Double-Blind Test Hid the Questions. It Did Not Remove Google From the Trust Chain

Google DeepMind says it has run what it calls the world’s first double-blind evaluation of a proprietary frontier-class model, letting outside evaluators test Gemini 2.5 Flash Lite without Google seeing the secret questions or the evaluators seeing the model weights. That is genuinely useful plumbing. It is not a certificate that Gemini passed with a gold star and a biscuit.

Google DeepMind Watch analysis

What entered the cryptographic exam room

The 27 August pilot brought together Singapore’s AI Safety Institute, OpenMined, AVERI and MLCommons. MLCommons supplied reserved AILuminate safety prompts that it says no Google DeepMind model had previously seen. Singapore AISI supplied a separate private set focused on eliciting harmful content in Singapore’s context. AVERI encrypted and decrypted the MLCommons prompts and outputs, then assessed the outputs.

Gemini 2.5 Flash Lite ran inside a temporary Google Cloud Confidential Space using an Intel TDX host, an NVIDIA H100 confidential GPU and OpenMined’s PySyft. Model weights and evaluation prompts entered encrypted memory only after the parties verified the enclave. Bounded results came out; the environment was then dismantled. In plain English, the exam paper and answer-writing machine met inside a locked room while each owner kept the other’s hands out of its briefcase.

What the pilot proves, and what it does not

The joint technical report documents an executed deployment and publishes the architecture. MLCommons separately confirms that it supplied a reserved prompt subset and calls the exercise a proof of concept. Those are meaningful participant records, not an arm’s-length reproduction. The announcement, report and MLCommons account publish neither Gemini’s safety scores nor the private prompts or raw outputs. They also present no independent security audit.

The report is admirably less starry-eyed than the launch copy. It says not all proprietary code could be inspected or allowlisted, Confidential Space builds were not independently reproducible because private signing keys were involved, and Google services signed and verified the attestation report. Google therefore remained in the verification path. AVERI was told about the limits and accepted the setup, but the trust fairy has not been made redundant.

Why this matters

If the method becomes reproducible and portable, evaluators could preserve scarce safety tests while model makers protect expensive weights. That matters for cyber, CBRNE and government evaluations, where leaking a benchmark can turn tomorrow’s safeguard into today’s revision guide. The next proof should be less ceremonial and more bruising: publish bounded aggregate scores where safe, invite an independent audit, make builds reproducible, and test across providers and multi-GPU clusters.

For now, the fairest verdict is promising infrastructure demonstrated by its builders, with material caveats disclosed by those same builders. That is progress. It is also exactly why double-blind evaluation needs open-eyed reporting.

Sources and evidence

Google DeepMind Watch is an independent WittyWires-operated tracker and is not affiliated with, endorsed by, or operated by Google DeepMind.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.