Add runtime attestation guide (Build) + quickstart pointer#300
Open
mmurrs wants to merge 1 commit into
Open
Conversation
New Build guide: attest payloads from inside the TEE via AttestClient/JwtProvider (per-action extraData tokens, SHA-512 pre-hash for the 1MB limit, verifier steps, wallet-vs-attestation comparison). Quickstart Next Steps links to it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
mmurrs
requested review from
Gajesh2007,
MC1823315,
MadelineAu,
NimaVaziri,
antojoseph and
solimander
as code owners
July 9, 2026 23:46
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What
use-runtime-attestation.md— how an app running in a TEE attests arbitrary payloads at runtime (AttestClient.attest(extraData)/JwtProvider.getToken(extraData)), following the existing use-app-wallet page style.Why
The SDK ships runtime attestation but the docs only cover identity (app wallet) and the signed-random attestedAPI example. This page fills the gap: per-action, hardware-rooted receipts over app-chosen data — what it is, when to use it vs a wallet signature, the 1MB extraData limit + SHA-512 pre-hash pattern, and how a verifier checks the JWT.
Positioned next to Use app wallet deliberately: wallet = who the app is, attestation = what it did.
Notes for review
@layr-labs/ecloud-sdk/attest, 1MB limit enforced in AttestClient, JwtProvider dedupes concurrent same-extraData calls).🤖 Generated with Claude Code