Sealed Dossier · recorded run
Three questions on an invented tenancy case, answered by Qwen/Qwen3.8-27B in the confidential tier of NEAR AI Cloud on 31 October 2026. Names were replaced before anything left the machine.
Every check below runs in your browser: no server, no key, no network request. The page carries the exact bytes of each receipt from fixtures/run1.
Checking…
For each receipt the page recomputes the SHA-256 of the request and of the response, recovers the signer from the EIP-191 signature, recomputes the receipt hash and follows the hash chain. The same checks as python -m sealed verify.
What this does and does not show
- Shows: the request and the response were not changed after signing, and the signature was made by the key
…. - Attestation: each receipt records
report_lists_signer: that key was listed in NEAR AI's attestation report fetched with a fresh nonce. The full Intel TDX and NVIDIA GPU check was done separately with NEAR AI's official verifier, for the same key: docs/ATTESTATION_CHECK.md. - Does not show: that names not on the user's list were hidden. Replacement is rule-based;
--dry-runshows the exact request before it is sent.