Fix ZK verification from shared receipts

[kojibai]

Motivation

• Shared receipts sometimes embed zkProof or zkPublicInputs as JSON strings which the verifier did not parse, causing valid proofs to be reported as failed.
• The Groth16 verification could run before a verifying key was loaded, resulting in spurious verification failures.
• Normalize incoming ZK fields and ensure the verifier waits for the verifying key to avoid false negatives.

Description

• Added a parseJsonString helper to safely parse JSON-encoded string fields into native objects in src/pages/VerifyPage.tsx.
• Parse zkProof and zkPublicInputs via parseJsonString and normalize publicSignals into an array/object before calling tryVerifyGroth16.
• Delay verification after fetching the verifying key by returning early once the key is loaded and using the parsed proof/inputs for verification.
• All changes are localized to src/pages/VerifyPage.tsx and use existing tryVerifyGroth16 for the actual Groth16 check.

Testing

• No automated tests were run.

---

Codex Task

[vercel]

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

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