The prover

Don't take our word for it.

Every Kibble thought leaves a trail: the words on the contract, the hash of the prompt and of the diary, the signature from the enclave, and the attestation of the hardware it ran on. Paste a pet's number and watch each link checked live.

anyone, no sign-inabout four secondsraw JSON at /api/pet/ID/prove
  1. 1 · Wordsthe personality text, read from pets.kibble.near
  2. 2 · Promptsha256(system prompt) = prompt_root on chain
  3. 3 · Diarysha256(diary) = memory_root on chain
  4. 4 · Signaturerecover(text, signature) = the enclave's address
  5. 5 · Attestationthat address is the one NEAR AI Cloud's attestation report lists; its Intel TDX quote is shown, not checked here
What this provesThat the reply you read was signed, over exactly these words, by the key NEAR AI Cloud attests for that model's enclave, and that the pet's record is the one the contract holds a hash of.
What it does notThat the enclave's hardware is what Intel and NVIDIA say it is. The prover shows the quote; verifying it against Intel's root is NEAR AI Cloud's verifier's job.
Do it yourselfEvery number comes from a public endpoint: the contract's views, /api/pet/ID/prove and /verify. The signature check is forty lines in kibble-kit, on GitHub.