They rely on Trusted Execution Environments and the fact that hash functions are one-way functions. Verifier -> requests a Prover to attest its software state

They rely on Trusted Execution Environments and the fact that hash functions are one-way functions. Verifier -> requests a Prover to attest its software state Prover -> goes into RoT, verifies authenticity of Verifier (and request), computes hash of attested memory region, sends hash digest Verifier -> receives digest and compares to known hash > What’s stopping remote endpoint always responding “yes” The attestation code is inside of a RoT, so a bad actor shouldn't be able to call this code, only callable by receiving a request from a Verifier