Verify

Checked in this browser, before anything is sent.

A failed or missing check is a failure, never a warning: the chat sends nothing until every line below passes. Presence is not proof, so each step is a verification, not a lookup.

Checking the enclave…

1Published release
The enclave's code release was fetched with its digest: the exact build the operator says is running.
checking
2Signed and logged code
That release is signed by its source repository's build and recorded in a public transparency log, so a quiet swap would be visible.
checking
3Hardware report
The enclave's report is signed by the processor vendor's keys: the code runs in an isolated, encrypted machine.
checking
4Measurements match
What the hardware measured equals what the signed release says it should be.
checking
5Key bound to the enclave
The key your messages are encrypted to is named inside that hardware report, so only this enclave can read them.
checking

What this proves

The machine your question is encrypted to runs a published, signed build inside vendor-attested hardware.
Only that machine holds the key: the gate in between passes ciphertext and cannot read the question or the answer.
That machine is a router; it checks the model machines it forwards to the same way before it uses them.

What it does not prove

That the hardware vendors' keys and patches are sound: attestation is only as good as its roots.
Anything about what you type: a name inside a question names you, ticket or not.
Your own device: a malicious extension can read this page.