ZIP-321 URI Support

[Jon-edge]

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

• Yes
• No

Dependencies

none

Description

none

---

Note

Adds Zcash ZIP-321 Payment URI handling by routing makeSpend to proposeFulfillingPaymentURI and wiring the method through the Zcash IO bridge.

• Zcash:
  • ZIP-321 URI flow: ZcashEngine.makeSpend now detects edgeSpendInfo.otherParams.zip321Uri and calls synchronizer.proposeFulfillingPaymentURI(...); otherwise falls back to proposeTransfer.
  • IO bridge: Extend ZcashSynchronizer with proposeFulfillingPaymentURI(paymentUri) and proxy to native react-native-zcash synchronizer.
  • Add debugging logs for proposal inputs/results.
• Docs:
  • Update CHANGELOG.md: add "(Zcash) ZIP-321 URI support" under Unreleased.

^{Written by Cursor Bugbot for commit 22a8e08. This will update automatically on new commits. Configure here.}

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1212244743805125

[chatgpt-codex-connector]

💡 Codex Review

edge-currency-accountbased/src/zcash/ZcashEngine.ts

Lines 462 to 466 in 995f06a

	this.log(
	'[ZEC propose] proposal result ' + JSON.stringify(proposal, null, 2)
	)
	const totalTxAmount = add(nativeAmount, networkFee)

Use proposal amount when fulfilling ZIP-321 URIs

When zip321Uri is provided the proposal is built via proposeFulfillingPaymentURI, but the spend amount used for fee checks and EdgeTransaction.nativeAmount is still nativeAmount from the spend target (totalTxAmount = add(nativeAmount, networkFee)). If the URI encodes a different amount (e.g., multiple recipients or a UI that leaves nativeAmount empty), the engine will undercount the outgoing value, potentially passing insufficient-funds checks and recording an incorrect debit while broadcasting the larger proposal returned by the synchronizer.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[peachbits]

The synchronizer?.proposeFulfillingPaymentURI != null is unnecessary as it's required in the type