Check a Sentinel answer
Every answer from Sentinel carries a proof signed by the Intel chip it ran on. Paste one here to check it. The check runs in your browser: nothing you paste is sent anywhere, and you do not have to trust Sentinel for any of it.
What this checks, and against what
- Intel's signature. The quote is checked with Phala's dcap-qvl, the same verifier the subnet's validators use, against Intel's root certificate built into it. Intel's signed documents for the machine are fetched from pccs.phala.network, a relay: everything it serves is signed by Intel and checked here, so it cannot vouch for a machine that Intel does not.
- The approved list. Approved releases, firmware and Secure Boot key come from measurements.json in the public repository. Its digest is …, which is what the subnet's owner commits on chain and every validator checks before using it.
- The release. The chip signs registers, not file names. The answer's boot log is replayed until it lands on exactly those registers, and only then is it read: which release loaded, and that Secure Boot checked it with Sentinel's key.
- This answer. The chip signed a value that commits to the result, the key server and the TLS key, so none of them can be changed after the fact.
What it does not show: that your agent's connection met the TLS key named here (your client's certificate check does that), or anything about answers you did not paste. Source: web/verify.