docs: Tapp verification SDK design draft (#9)#15
Open
Wilbert957 wants to merge 1 commit into
Open
Conversation
Design draft for extracting tapp's chain/attestation logic into a reusable SDK so consumers (CLI, verifier, frontend, indexer, agents) don't re-implement the footguns (RTMR-vs-report_data, quote version offset, override/inherit, AS endpoint, hash codec). Notes that the core verify flow already ships in src/verify.rs (tapp-cli verify-app), so the SDK is mostly "extract verify+onchain into a shared (macOS-buildable) crate + bindings" — which also removes the module duplication of the standalone-CLI approach.
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
1 participant
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.
Design draft for the Tapp verification SDK (tracking #9): extract tapp's chain/attestation logic into a reusable, macOS-buildable crate + TS/Python bindings, so every consumer (CLI, verifier, frontend, indexer, agents) shares one tested implementation instead of re-rolling the footguns (RTMR-vs-report_data, quote version offset, override/inherit, AS endpoint :50004, on-chain hash codec).
Key point: the core verify flow already ships in
src/verify.rs(behindtapp-cli verify-app) — chain reads, evidence parsing, CoCo-AS client, reconciliation. So the SDK work is mostly extractverify+onchaininto a shared crate + add bindings, which also resolves the module duplication of the "standalone CLI" approach (#13) by sharing one crate.Docs-only (design draft for review).
🤖 Generated with Claude Code