Skip to content

Include KAS and ZK fields from shared receipt into embedded proof#215

Merged
kojibai merged 1 commit intocodex/fix-zk-proof-verification-issuefrom
codex/fix-verification-not-indicating-status
Jan 11, 2026
Merged

Include KAS and ZK fields from shared receipt into embedded proof#215
kojibai merged 1 commit intocodex/fix-zk-proof-verification-issuefrom
codex/fix-verification-not-indicating-status

Conversation

@kojibai
Copy link
Copy Markdown
Owner

@kojibai kojibai commented Jan 11, 2026

Motivation

  • Shared receipts loaded via the ?r receipt parameter were not exposing author signature and ZK metadata to the embedded proof state, preventing KAS/G16 seals from being displayed/verified.
  • The goal is to preserve the full seal data from a shared receipt so subsequent verification UI and logic (KAS/Groth16) can operate on that data.

Description

  • When a sharedReceipt is used to populate proof state, the code now copies authorSig into the constructed embeddedProof object in src/pages/VerifyPage.tsx.
  • The change also preserves ZK-related fields zkProof, proofHints, and zkPublicInputs from the sharedReceipt into embeddedProof so sealZK logic can run.
  • Other existing fields (proofCapsule, svgHash, capsuleHash, bundleHash, shareUrl, verifierUrl) continue to be set as before.

Testing

  • No automated tests were run as part of this change.
  • Manual inspection and static code checks were used to confirm the added fields are assigned in buildProof when sharedReceipt is present.

Codex Task

@vercel
Copy link
Copy Markdown

vercel bot commented Jan 11, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
phi-network-5aii Ready Ready Preview, Comment Jan 11, 2026 5:17pm

@kojibai kojibai merged commit 3835b8d into codex/fix-zk-proof-verification-issue Jan 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant