Reclaim ProtocolReclaim ProtocolTrust Center

Whitepaper Adherence

Our guarantee

Every claim in the Reclaim Protocol whitepaper is re-verified monthly against the open-source code that runs in production. The verdict and the source files are published per claim.

The threat model

A whitepaper is only useful if the code actually implements it. Implementations drift from their specifications silently, through refactors, optimizations, or shortcuts. Even when no one means to break the protocol, things slip. Without continuous re-verification, security claims based on the whitepaper become stale fiction.

How it’s enforced

Every claim from the whitepaper is encoded as a verifiable statement. An AI reviewer maps each claim to the specific files and functions in the open-source code that implement it, then confirms (or flags) whether the implementation matches. The check runs monthly against the latest commit on each verification repo.

How you verify

The full per-claim table is published on this page below: each verdict, the AI's reasoning, and the exact source files inspected, all linked directly to GitHub. Disagree with a verdict? You have the same source files we do.

What you still trust

The whitepaper itself, which has been peer-reviewed at IACR ePrint 2024/733 and independently audited by multiple cryptography researchers. And the AI reviewer's faithfulness in mapping claims to code, which you can spot-check against the per-claim table below.
Reclaim Protocol Whitepaper

Reclaim Protocol Whitepaper

View on Google Drive

Last checked: 7d ago
reclaim-teeattestor-corereclaim-inapp-sdkreclaim-js-sdkreclaim-sdk-backend
AugSepOct
Monitoring started · Jul 15Oct 12

Today · Oct 12

For any incidents, please report at support@reclaimprotocol.org. Response time: 4 hours for critical, 48 hours for other issues.

© 2026 Reclaim Protocol · trust.reclaimprotocol.org

DocumentationContact

0/24 claims passed, 0 partial · 0 cached from previous run

✓ 0 passed⚠ 24 didn’t match

Every statement we make in our whitepaper is re-verified monthly against the open-source code. For each claim below you can see the AI's reasoning and open the exact files it inspected on GitHub.

⚠ Needs attentioncryptographySection 3.2.3, page 14
claim-009

For AES-GCM, TagSecrets passed from TEEK to TEEA consists of EK(0^128) and EK(IV||0^31||1)

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWWEL9csvFQAHmV3eda"}

⚠ Needs attentiondata-handlingSection 3.2.5 Algorithm 5 step 8, page 16
claim-017

The proof output Pi consists of the two signatures (sigma_K, sigma_A) and the session-related data that was signed

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWX3nRKumurzLcJj44X"}

⚠ Needs attentionprivacySection 3.2.3 Algorithm 3 step 9, page 14
claim-008

All sensitive data masked by the user is correctly reapplied when TEEA reconstructs the full request ciphertext, ensuring no sensitive bytes are exposed to either TEE

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWXmzvZRmWFhG3VQVXN"}

⚠ Needs attentionsecurityAppendix C.7.3, page 43
claim-024

The protocol monitors BGP announcements via RIPE RIS to detect traffic rerouting between the attestor and the website during proof creation

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWXvHkqm7vW4XK7BkmH"}

⚠ Needs attentiondata-handlingSection 3.2.2 Algorithm 2, page 13
claim-003

User sends connection parameters (hostname, port, SNI, ALPN) to TEEK at the start of the TLS handshake phase

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWYmq2hyMnnoFbXKDQt"}

⚠ Needs attentionprivacySection 3.2.3 Algorithm 3, page 13-14
claim-006

All sensitive portions of the request are masked by the user before being sent to TEEK, ensuring TEEK never sees any raw sensitive data

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWZveeKfcgqEPp5iPa1"}

⚠ Needs attentioncryptographySection 3.2.3, page 14
claim-010

For ChaCha20-Poly1305, TagSecrets consists of the first 32 bytes of the encryption stream derived at counter value 0

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWabyWjM7sPsqeBU2DX"}

⚠ Needs attentioncryptographySection 3.2.3 Algorithm 3 steps 10-12, page 14
claim-011

TEEA computes authentication tag T = AuthTag(Renc, TagSecrets) and sends it to the user for forwarding to the website

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWbPpJZBEVYPXbWxZJc"}

⚠ Needs attentionprivacyAppendix C.1, page 37
claim-023

The user does not learn the TLS session encryption keys at any point before both TEEs switch to FINISHED phase

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWcAtwR8nf2NjYXe2Sc"}

⚠ Needs attentionarchitectureSection 3, page 11; Section 3.1, page 12
claim-001

The protocol uses exactly two separate TEEs: TEEK (holds TLS keys) and TEEA (computes auth tags without key access)

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWd3xm7TRoXTnrgJSPd"}

⚠ Needs attentioncryptographySection 3.2.2 Algorithm 2, page 13
claim-004

TEEK derives three session keys (kenc, kdec, IV) during the TLS handshake and does not share them with the user

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWdnGiMwKJTTR3qzkMB"}

⚠ Needs attentioncryptographySection 3.2.4 Algorithm 4 step 8, page 15
claim-013

TEEK generates the decryption stream as StrDec = Stream(kdec, nonceresp, |Respenc|) only after receiving a success signal from TEEA

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWeTvSCfx7PNC5vfr5B"}

⚠ Needs attentionsecuritySection 3.2.5, page 16 (note after Algorithm 5)
claim-018

TEEK signs the SSL Certificate of the website received during the TLS handshake as part of its attestation commitment

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWfDKd4Rp43wfSgXmqt"}

⚠ Needs attentionsecuritySection 3.2.2 Algorithm 2, page 13; Appendix C.3, page 38
claim-005

TEEK verifies the website's SSL certificate

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWfuhkbj8XeiAzkVYf2"}

⚠ Needs attentioncryptographySection 3.2.5 Algorithm 5 step 5, page 16
claim-016

TEEA produces signature sigma_A over the concatenation of Respenc, Tresp, and StrSP

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWgeDcjyVon4ecw4aH1"}

⚠ Needs attentionsecuritySection 3.2.4 Algorithm 4 steps 5-11, page 15
claim-012

TEEA verifies the website response authentication tag before any decryption material is released; the session aborts if verification fails

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWhKJcCTzBWMSwRbVv7"}

⚠ Needs attentionsecurityAppendix C.7.3, page 43
claim-025

If a potentially malicious BGP announcement is detected, the current connection and proof creation are dropped

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWhW4VzYxwPShqAxuAG"}

⚠ Needs attentionarchitectureSection 3.2.6 Algorithm 6 step 4, page 16
claim-021

Verifier reconstructs the revealed request by copying Rred and replacing bytes in non-proof redaction ranges (requestRedactionRanges without 'proof' type) with redaction characters for display

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWhg9jR8eYkX3K9dtz4"}

⚠ Needs attentionsecuritySection 3.2.6 Algorithm 6 step 3, page 16
claim-020

Attestor validates the website's SSL Certificate as a distinct step during proof verification

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWhzr8JwVHsLCjckJs7"}

⚠ Needs attentionarchitectureSection 3.2.6 Algorithm 6 step 5, page 16
claim-022

Attestor reconstructs the revealed response as reconstructedResponse = consolidated_response_ciphertext (Respenc) XOR consolidated_response_keystream (StrDec,Red from TEEK) directly using redacted keystream (no full decryption keys)

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWiBRsDMxbhkJjN8A4t"}

⚠ Needs attentioncryptographySection 3.2.3 Algorithm 3 step 5, page 14
claim-007

TEEK encrypts the redacted request as Rred,enc = Rred XOR Stream(kenc, nonce)

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWitiJKRynG88oWUDR1"}

⚠ Needs attentioncryptographySection 3.2.5 Algorithm 5 step 4, page 16
claim-015

TEEK produces signature sigma_K over the concatenation of Rred, StrDec,Red, and the website's SSL Certificate

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWjairye1ugKqcATU3j"}

⚠ Needs attentionprivacySection 3.2.5 Algorithm 5 step 2, page 15-16
claim-014

TEEK replaces bytes at user-specified SecretRanges in StrDec with '*' to produce StrDec,Red before signing

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWkFq5MTNoSELHbHdGx"}

⚠ Needs attentionsecuritySection 3.2.6 Algorithm 6 step 2, page 16
claim-019

Proof verification checks both ECDSA signatures against the public keys of TEEK (pkK) and TEEA (pkT)

AI reasoning

Verification error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CfiWkeph4xzX4og6UCooF"}

0% Pass
Last checked: 7d ago

Repositories scanned (6)

  • attestor-core
  • reclaim-devtool-backend
  • reclaim-inapp-sdk
  • reclaim-js-sdk
  • reclaim-sdk-backend
  • reclaim-tee

Methodology

Monthly AI re-verification of every whitepaper claim against the open-source code that runs in production.