Read live from NEAR testnet Nothing here is taken on our word
Ask NEAR yourself.
Each line below is a claim this project makes about its contract on NEAR. Your browser asks NEAR's public RPC and compares the answer. No wallet, no key, nothing signed; the only requests leave for the RPC.
1. The contract's account has no access keys
With no key on , no key holder, us included, can replace its code or its fee. Together with check 2 (the code is the repository's, and that code has no way to replace itself) this is what "nobody can change it" rests on.
2. The code on NEAR is the code in the repository
The hash NEAR reports for the account, against the hash of the contract built from the repository (scripts/check-deployed rebuilds it and compares).
3. The sample review is signed by the model that wrote it
The capsule on this site is verified in this tab; every answer in it carries the model's own signature.
4. NEAR's verifier contract vouched for that model key
Our contract handed the key's Intel TDX quote to the verifier contract that near/mpc's design documents name as live on testnet, and recorded what it answered. This asks for that record, and checks that the verifier's own account has no access keys and still runs the code we pinned.
5. The contract paid for a review when its capsule was registered
This order required a hardware record. In the transaction that released the money, the contract verified the capsule's model signatures and that the model key had an up-to-date record made after the order opened.
6. What the registry holds right now
Counts read from the contract, and the fee written into its code.
What this shows, and what it does not
- Everything is NEAR testnet. The amounts are test tokens. The numbers are small because the product is a prototype: they are the real counts, not rounded up.
- Check 4 shows what the verifier contract accepted and that its account is keyless; that the account is NEAR's rests on near/mpc's documents naming it, which this page cannot check for you.
- Check 2 compares with a hash this site states. To take nobody's word, run scripts/check-deployed in the repository: it builds the contract and compares it with NEAR itself.
- A hardware record shows the model ran on a machine Intel's collateral accepts at that patch level. It does not show that an answer is right.
- The same claims for a program to read: proof.json (each claim with the exact RPC request and the expected answer) and llms.txt.