Skip to content

Add wallet support for shielded voting snapshots#5

Closed
greg0x wants to merge 2 commits into
maint/zcash_client_sqlite-0.19.xfrom
shielded-voting-wallet-support
Closed

Add wallet support for shielded voting snapshots#5
greg0x wants to merge 2 commits into
maint/zcash_client_sqlite-0.19.xfrom
shielded-voting-wallet-support

Conversation

@greg0x
Copy link
Copy Markdown

@greg0x greg0x commented Mar 13, 2026

Adds the minimal librustzcash surface needed for Zcash shielded voting. Targets maint/zcash_client_sqlite-0.19.x (orchard 0.11); same changes apply cleanly to main (orchard 0.12).

Related:

PCZT changes (pczt crate)

  • Spend::spend_auth_sig getter — read back the hardware wallet signature after signing, so it can be threaded into a ZK delegation proof
  • Signer::shielded_sighash() getter — expose the cached sighash (already on upstream main, backported here)

Wallet changes (zcash_client_sqlite crate)

Two new governance-specific methods on WalletDb (inherent, not on wallet traits — these don't belong in the general-purpose API):

  • get_orchard_notes_at_snapshot(account, height) — returns all Orchard notes received at or before snapshot_height and unspent as of that height. Backward-looking query for voting snapshots, unlike select_unspent_notes which is forward-looking (based on tx expiry).

  • generate_orchard_witnesses_at_frontier(positions, frontier, height) — copies wallet shard data to an ephemeral in-memory database, inserts the lightwalletd frontier as a checkpoint, and generates Merkle witnesses at the snapshot anchor. The wallet DB is strictly read-only.

Context

Governance protocols need to construct Orchard-only PCZTs for hardware wallet signing, query wallet notes at a historical snapshot, and generate witnesses anchored at that snapshot's frontier (even if the wallet has synced past it). These changes cleanly separate concerns: librustzcash owns the wallet domain, the voting library owns the voting domain, and the SDK wires them together.

greg0x added 2 commits March 13, 2026 14:23
Shielded voting protocols need to:

- Read back the spend_auth_sig after a hardware wallet signs the PCZT,
  so the signature can be threaded into a ZK delegation proof
- Access the cached shielded sighash from the Signer role

Changes:
- Add Spend::spend_auth_sig getter (via getset)
- Add Signer::shielded_sighash() getter
WalletDb gains two new methods (not on traits — governance-specific):

- get_orchard_notes_at_snapshot(account, height): returns all Orchard
  notes received at or before snapshot_height and unspent as of that
  height. Backward-looking query for voting snapshots, unlike
  select_unspent_notes which is forward-looking.

- generate_orchard_witnesses_at_frontier(positions, frontier, height):
  copies wallet shard data to ephemeral in-memory DB, inserts the
  lightwalletd frontier as a checkpoint, and generates Merkle witnesses.
  Wallet DB is strictly read-only.
@greg0x greg0x closed this Mar 13, 2026
@greg0x
Copy link
Copy Markdown
Author

greg0x commented Mar 13, 2026

zcash#2212 - this is superseded by the main PR

p0mvn pushed a commit that referenced this pull request Apr 3, 2026
…14868de..23f0768ea

23f0768ea Release lightwallet-protocol v0.4.0
41156c767 Merge pull request #11 from zcash/feature/get_mempool_tx_pools
7c130e883 Add `lightwalletProtocolVersion` field to `LightdInfo` struct.
edbb726d7 Apply suggestion from code review
38fddd73b Apply suggestions from code review
0250f2720 Add pool type filtering to `GetMempoolTx` argument.
54ccaadd5 Change semantics of pool-based pruning of compact transactions from "may prune" to "must prune".
b0667ec99 Merge pull request #9 from zcash/2025-11-doc-TransparentAddressBlockFilter
f3fea7bd4 doc: TransparentAddressBlockFilter doesn't include mempool
a67dd323a Merge pull request #8 from zcash/2025-11-lightdinfo-upgrade-info
11da4b7e3 add next upgrade info to LightdInfo structure (GetLightdInfo)
42cd8f720 Transparent data docs update (#7)
c0cf957ac Merge pull request #5 from zcash/2025-11-comments
912fc3609 Minor clarification in GetBlockRange documentation.
6b03f2cce Documentation (comments) only
d978256a2 Merge pull request #1 from zcash/compact_tx_transparent
7eeb82e7c Merge pull request #4 from zcash/add_changelog
a95359dc9 Apply suggestions from code review
592b637a8 Add transparent data to the `CompactBlock` format.
9d1fb2c41 Add a CHANGELOG.md that documents the evolution of the light client protocol.
180717dfa Merge pull request #3 from zcash/merge_librustzcash_history
450bd4181 Merge the history of the .proto files from `librustzcash` for complete history preservation.
a4859d11d Move protobuf files into place for use in `zcash/lightwallet-protocol`
2e66cdd9e Update zcash_client_backend/proto/service.proto
eda012519 fix comment
f838d10ad Add gRPC LightdInfo Donation Address
db12c0415 Merge pull request zcash#1473 from nuttycom/wallet/enrichment_queue
698feba96 Apply suggestions from code review
20ce57ab3 zcash_client_backend: Add `block_height` argument to `decrypt_and_store_transaction`
a6dea1da8 Merge pull request zcash#1482 from zancas/doc_tweak
4d2d45fc9 fix incorrect doc-comment
e826f4740 update CompactBlock doc-comment, to cover non-Sapling shielded notes, and addresses
e9a6c00bf Various documentation improvements
988bc7214 Merge pull request zcash#872 from nuttycom/feature/pre_dag_sync-suggest_scan_ranges
58d07d469 Implement `suggest_scan_ranges` and `update_chain_tip`
a9222b338 Address comments from code review.
e20310857 Rename proto::compact::{BlockMetadata => ChainMetadata}
ac63418c5 Reorganize Sapling and Orchard note commitment tree sizes in CompactBlock.
0fdca14f1 zcash_client_backend: Add note commitment tree sizes to `CompactBlock` serialization.
2a0c2b8b7 zcash_client_backend: Add gRPC bindings behind feature flag
1342f0480 zcash_client_backend: Address compact_formats.proto comments
68aa4e01b zcash_client_backend: Bring in latest `compact_formats.proto`
e712eb1bc Add prevHash field to CompactBlock
440384c3e Build protobufs for compact formats

git-subtree-dir: zcash_client_backend/lightwallet-protocol
git-subtree-split: 23f0768ea4471b63285f3c0e9b6fbb361674aa2b
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