The verification frontend allows anyone to verify proofs that specific checks or verifications were performed inside a Trusted Execution Environment (TEE). When someone makes a claim like “I verified my Reddit karma is over 1000” and provides a TEE attestation as proof, this frontend lets others cryptographically verify that claim was actually checked within a secure hardware environment.

​

Purpose

Many systems need to verify user claims or credentials while preserving privacy. The TLS attestation system allows these checks to happen inside a TEE, which then produces cryptographic proof that the verification occurred and passed. The verification frontend makes it easy for anyone to validate these proofs.

​

What Gets Verified

When you paste a TLS attestation into the frontend, it verifies three critical properties:

1. The exact code that ran in the TEE matches a known, trusted hash. This confirms what verification logic executed.

2. The specific claim or check being attested to was satisfied according to the TEE’s verification.

3. The hardware executing the check was a legitimate TEE, verified against the hardware manufacturer’s root of trust public key.

​

Components

​

Verification Interface

The frontend provides a simple interface for verifying attestations:

1. Shows the expected code hash representing the verification logic that should have run

2. Displays information about what claim was being verified

3. Provides an input field for the attestation proof

4. Includes a “Verify” button to trigger validation

​

Verification Results

Upon successful verification, the frontend confirms:

1. Code hash matches the open-source implementation, proving exactly what verification logic ran

2. The specific check or claim being verified was satisfied inside the TEE

3. Hardware authenticity is confirmed through the attestation chain back to the manufacturer

​

More Details

​

Attestation Structure

The attestation object contains:

• Measurements of the code executed in the TEE

• Details of what was verified in the TLS session

• Hardware-signed proof of secure execution

• Chain of signatures linking to the hardware manufacturer’s root of trust

​

Verification Process

The frontend performs these checks:

1. Validates the signature chain back to the hardware manufacturer

2. Verifies the code measurements match the expected verification logic

3. Confirms the specific claim or check was satisfied

4. Validates the hardware instance identifiers

​

Usage Instructions

1. Navigate to the verification frontend

2. Note the expected code hash that should have performed the verification

3. Review what claim or check was being verified

4. Paste the attestation proof

5. Click “Verify” to validate the attestation

6. Review the results confirming all security properties

This system allows anyone to verify that specific checks or claims were legitimately verified within a TEE without having to trust the entity making the claim. The cryptographic attestations prove that the verification occurred in secure hardware running the expected code. This enables trustless verification of user claims while maintaining privacy, since only the fact that a check passed (not the underlying data) is revealed.