Skip to content

View proof: open the TEE Explorer report already verified, no pasting #277

Closed

Description

@Lexirieru

Axel's request (12 Nov): in "The proof behind this reply", the Paste the quote in TEE Explorer link should open https://proof.t16z.com with the quote already checked, so the user doesn't have to paste anything.

What we found (checked 12 Nov)

  • Why pasting failed: pasting the whole proof (the JSON from "Copy the proof") into the Explorer answers "The quote is invalid". The Explorer takes only the Intel quote as hex.
  • No prefill URL: proof.t16z.com has no URL parameter that fills in a quote.
  • The upload API: its own Verify button calls POST https://proof.t16z.com/api/upload, multipart file = the quote's bytes, application/octet-stream. It answers { success, checksum, url, quote: { verified, … } }, and the report lives at https://proof.t16z.com/reports/<checksum>.
  • Live check: an Intel quote from a local run's run.verified proof returned verified: true and a report page reading VERIFIED, "The attestation is verified and safe to use".
  • No browser calls: the API sends no CORS headers, so the FE can't call it. The upload must go through the backend.

Plan

  1. Backend: POST /v1/runs/{runId}/proof/tee-explorer, for the run's owner only.
    • Takes the Intel quote(s) from the stored proof (GET /v1/runs/{runId}/proof already has them) and uploads the bytes.
    • Answers { reports: [{ attestation, url, verified }] }.
    • Keeps the checksum so a second click doesn't upload again.
    • Uses a timeout and no redirects. Only the quote is sent: NEAR AI's hardware report and nonce, never conversation text.
  2. FE (@AncungAulia): the link calls that route and opens url in a new tab.
    • Open the tab on the click, then set its location when the answer arrives, so popup blockers don't stop it.
    • Keep "Copy the Intel quote" for people who want to paste it themselves.

Note

An uploaded report appears in the Explorer's public "Recent attestations" list, the same as if the user pasted it. It holds the attestation only.

🤖 Generated with Claude Code

Activity

  1. Lin1er commented on Nov 12, 2026

    @Lin1er
    Contributor

    @Lexirieru the backend part is ready on branch feat/be-tee-explorer (58de954). OK to open a PR to main?

    Route: POST /v1/runs/{runId}/proof/tee-explorer, body {}, owner only.

    • Answers { reports: [{ attestation, url, verified }] }.
    • Errors: 404 run_not_found / no_proof / no_quote, and 503 tee_explorer_unreachable / tee_explorer_error when the Explorer fails.

    What it does

    • Uploads each attestation's Intel quote (hex → bytes) to proof.t16z.com/api/upload as multipart file = quote.bin, application/octet-stream. That's the same request the Explorer's own Verify button sends.
    • Only the quote is sent: no steps, no signed text, no conversation.
    • 20 s timeout and no redirects. The report URL is built from the checksum (it must be 64 hex), never taken from the answer.
    • tee_explorer_reports (migration 016) keeps the checksum per quote hash, so a second click doesn't upload again.
    • Docs updated: docs/api-contract.md (§5 + §7) and apps/be notes.

    Tests (ct-dev-env)

    • apps/be typecheck clean.
    • bun run test: 133 pass, 0 fail, 1 skipped. A new case against a fake Explorer covers refused and bad-checksum answers, reuse, owner only, and no proof.
    • bun run load: 0 errors, 0 runs missing events.
    • Not checked against the live Explorer from this branch. Your live check on this issue used the same request shape.

    @AncungAulia once this is merged: call it on the link click, opening the tab first and then setting its location to reports[0].url.

  2. added 3 commits that reference this issue on Nov 12, 2026
  3. Lexirieru commented on Nov 12, 2026

    @Lexirieru
    ContributorAuthor

    Done: backend route #279 and the "Check it in TEE Explorer" button #280 are merged and live; checked in Chrome (one click, one tab, a VERIFIED report).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions