Proof

Re-check KEYHOLE on mainnet.

No wallet. Each row below hits a public RPC or attestation API and shows PASS or FAIL.

Check one TEE call

Reads the key's owner, lien state, loan terms and refusal rules from the final chain. Nothing is signed.

Live evidence pack

Running

Each row is a claim, the exact public read used to check it, and the live result. No wallet. No signing.

ClaimHow checkedResult

……

Claims checker: run the claims checker script from the repository root (667 claims; last recorded offline run 0 FAIL). This page re-checks the subset that a browser can read without cloning. The count is the current docs/claims.json length and changes when claims are regenerated.

Verify · runs in your browser

Don't trust us. Check the seal.

Six attestation checks, 19 Intel DCAP checks and 12 Intel revocation and TCB checks, done locally against the enclave's attestation, Intel's signed data and NEAR mainnet. Nothing here asks you to trust this site.

·/37

37 checks run in this browser6 against NEAR mainnet, 19 Intel DCAP, 12 revocation and TCB. No server of ours is trusted.

Result

Not verified yet.

·Quote validityTDX quote + 19 Intel DCAP checks
·Output bindingreport_data binds request hash / account / token
·Economic semanticsEvidence / pasted output vs attestation
·Current-build identityWasm vs the live registry

A sealed enamel reliquary with a wax seal

Attestation report

Where each check comes from: computed in your browserread from NEAR mainnetfetched from OutLayeragainst Intel's root / PCSdata we publish (repo) Only the last one is our word; everything else you can re-run without us.

Enclave attestation 6 checks

Intel TDX quote present fetched from OutLayercomputed in your browserOutLayer attestation · quote parsed in your browser

—

Worker code hash matches computed in your browserRegistered hash equals the hash that executed, then your browser re-hashes the wasm.

—

Published on NEAR read from NEAR mainnetcomputed in your browserThe wasm bytes come from on-chain FastFS.

—

Published build data we publish (repo)executed_wasm_sha256 equals the published worker unknown (registry unreadable)

—

Quote binds this exact call computed in your browserreport_data in the TDX quote is recomputed from the attested fields

—

Output matches the attested hash data we publish (repo)computed in your browserOptional: paste the worker output below to check it against output_hash

—

Intel quote check 19 checks

·Intel DCAP, checked in your browser computed in your browseragainst Intel's root / PCS…

Parses the TDX quote, verifies the quote signature, the Quoting Enclave report and the PCK chain up to the pinned Intel SGX Root CA, and checks report_data against the attested fields. Revocation and TCB status are checked in the next section.

Intel revocation and TCB 12 checks

·Intel revocation and TCB status against Intel's root / PCScomputed in your browser…

Fetches Intel's PCK and Root CA revocation lists, the TDX TCB Info for this machine's FMSPC and the TD Quoting Enclave identity from Intel PCS, through a pass-through on this site because Intel sends no CORS headers. Every signature is checked here against the pinned Intel SGX Root CA, then the TCB level is matched as Intel's verifier does. The status is shown as Intel reports it.

Recent real calls

H=$(curl -s https://api.outlayer.ai/attestations/by-call/<call_id> | jq -r .executed_wasm_sha256)
curl -s https://main.fastfs.io/keyhole-devmo.near/outlayer.near/$H.wasm | sha256sum
# tx GXZtL6hgscWUAh7SpZLA5SBLyrVe4w9bCxz2Kmb4q1K5