Verify · NEAR testnet
Don't trust this page.
Your browser is asking NEAR testnet directly. It reads the contract and the refund transaction of call 2 (the wrong answer), rebuilds what each AI model of the experimental panel was asked, and checks the three signatures itself. From us come only the transaction IDs, the account names, the published contract hash and the panel's system prompt; the page checks that prompt against the hash the contract itself logged. Everything else is read from the chain.
- The refund transaction exists on NEAR testnet: 0.40 USDC back to the buyer
- The contract on chain is the published build
- 3 of 3 AI votes carry valid signatures from the keys stored in the contract
- The votes are about this request and this answer, not another one
Not checked here: that each key belongs to a genuine enclave. That check runs offline (make verify), and the Intel and NVIDIA certificate chains are not verified anywhere yet. The contract owner registers the juror keys. What the check covers