Check the AI summary's receipt
What this is: This page checks that the summary came back signed as provider_tee.
What you can do: You can read the receipt, and you can try a tampered copy to see it refused.
- Model
- z-ai/glm-5.3-flash
- Signature
- loading
- Signer
- not run
- Request hash
- not run
- Response hash
- not run
- Server attestation
These fields come back with the sealed summary. A filled value was verified by our server via the NEAR AI SDK at call time. This browser did not verify the quote. Where a field is missing, it was not checked.
Gateway TCB. Not checked
Gateway signer. Not checked
Gateway TLS. Not checked
Model TCB. Not checked
Model GPU. Not checked
Model signer. Not checked
- Approve transaction
- No approve transaction is saved in this session. This page does not read the contract to confirm it.
- 01Signature kind is provider_teeNot run
The summary call must report provider_tee. That is the only signature check this page computes.
- 02Fresh client nonceNot checked here
This page does not generate or compare a 32-byte nonce.
- 03Gateway quoteNot checked here
This page does not read a gateway quote or a TCB status.
- 04Nonce bound to the reportNot checked here
This page does not check that report data binds a nonce.
- 05Event log and RTMR3Not checked here
This page does not replay an event log or compare RTMR3.
- 06Compose measurementNot checked here
This page does not compare a compose hash with a measurement.
- 07Model measurementsNot checked here
This page does not check model measurements or GPU evidence.
- 08Encrypted to the model key in the browserNot checked here
In this demo the chart is sent to the app server for the sealed summary. The server turns on NEAR AI SDK encryption for that call. This page does not check browser-side encryption.
- 09Request and response hashesNot checked here
No receipt hashes are on this page yet. This page does not recompute them.
- 10Receipt hash stored on NEARNot checked here
No approve transaction is saved in this session. This page does not read the contract.
These lines are copied from the attack-demo table in this repo (testnet, 2026-11-14, 11 of 11 passed, attack share 14). This page does not run the attacks. A recorded result is not a fresh check.
Clinic create_record was accepted and returned record 8.
On the testnet contract.
Clinic request_referral to the hospital was accepted and returned share 14.
On the testnet contract.
A clinic that is not the recipient called request_open. The contract refused with ERR_UNAUTHORIZED.
On the testnet contract.
Patient approve_share with 1 yoctoNEAR was accepted.
On the testnet contract.
Hospital request_open on the active share was accepted.
On the testnet contract.
The first local open was HTTP 200. The same nonce was HTTP 403 replay.
Inside the script, not a new transaction.
No transaction. This check is local.
The script offered an encryption key that does not match the on-chain directory. The code kept the on-chain key.
Inside the script, not a new transaction.
No transaction. This check is local.
A ciphertext with one flipped byte was rejected.
Inside the script, not a new transaction.
No transaction. This check is local.
Hospital submit_reply was accepted and returned reply 16. The reply text was not stored, only a hash.
On the testnet contract.
Patient revoke_share with 1 yoctoNEAR was accepted. Revoke cannot erase a copy already downloaded.
On the testnet contract.
A later hospital request_open panicked ERR_REVOKED.
On the testnet contract.
Testnet only, with fictional data. This list is not a stamp of approval, and it does not say every possible attack was tried. Revoke cannot erase a copy already downloaded.