Document TEE trust model and signature verification scope#289
Open
adambalogh wants to merge 1 commit intomainfrom
Open
Document TEE trust model and signature verification scope#289adambalogh wants to merge 1 commit intomainfrom
adambalogh wants to merge 1 commit intomainfrom
Conversation
Distinguish the three layers that make SDK responses trustworthy (network-side attestation at registration, SDK-side TLS pinning at request time, on-chain signature verification at settlement) so users don't read tee_signature on a returned response as a client-side verification gate. - README: add "Trust Model" section; soften the TEE-Secured LLM Chat blurb to point at it. - types.py: rewrite the TextGenerationOutput class docstring's verification paragraph, and tighten the tee_signature field docs on both TextGenerationOutput and StreamChunk. - tee_connection.py: mark StaticTEEConnection as dev-only and call out that it is not a production trust path (verify=False, no pinning).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR clarifies the trust model and signature verification scope for OpenGradient's verifiable inference system. It documents that live trust comes from TLS certificate pinning to the on-chain registry, while
tee_signatureverification happens at on-chain settlement rather than in the SDK at return time.