Skip to content

Reject existing Zcash batch signatures#34

Closed
czarcas7ic wants to merge 1 commit into
zcash-upstreamfrom
adam/reject-preexisting-zcash-shielded-signatures
Closed

Reject existing Zcash batch signatures#34
czarcas7ic wants to merge 1 commit into
zcash-upstreamfrom
adam/reject-preexisting-zcash-shielded-signatures

Conversation

@czarcas7ic

Copy link
Copy Markdown

Summary

Reject Zcash batch requests that already contain Orchard or Ironwood spend authorization signatures. Batch responses are defined as compact signatures generated by the device, so accepting incoming signature fields could let a mixed-action request report success while returning bytes that the device did not produce.

The check is limited to batch review and signing. Generic PCZT signing keeps its collaborative and finalized dummy behavior, and the cached signability decision remains bound to the complete normalized PCZT digest.

Test plan

  • cargo +nightly-2025-07-01 test -p app_zcash --locked
  • cargo +nightly-2025-07-01 test -p app_zcash --no-default-features --features multi_coins --locked
  • cargo +nightly-2025-07-01 test -p rust_c --no-default-features --features simulator-cypherpunk --lib -- zcash common::ur
  • cargo +nightly-2025-07-01 fmt --all -- --check
  • cargo +nightly-2025-07-01 metadata --locked --no-deps --format-version 1
  • python3 build.py -t cypherpunk -o simulator

@czarcas7ic czarcas7ic closed this Jul 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant