Add draft ZIP: Deterministic Orchard Wallet Scanning Standard #1158
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,47 @@ | ||
| ZIP: unassigned | ||
| Title: Deterministic Orchard Wallet Scanning Standard | ||
| Owners: Lowo88 <lowo88@leoninedao.org> | ||
| Status: Draft | ||
| Category: Standards Track | ||
| Created: 2026-01-16 | ||
| License: MIT | ||
|
|
||
| # Abstract | ||
|
|
||
| This ZIP specifies a standard algorithm for deterministic scanning of Orchard | ||
| notes in Zcash wallets. The specification ensures that wallet implementations | ||
| produce identical results when scanning the same block range, regardless of | ||
| implementation details, scan order, or timing. | ||
|
|
||
| # Motivation | ||
|
|
||
| Current Zcash wallet implementations lack a standardized approach to scanning | ||
| Orchard notes. This leads to several critical issues: | ||
|
|
||
| **Non-Deterministic Results**: Different wallets may produce different results | ||
| when scanning the same block range. | ||
|
|
||
| **Inconsistent Wallet State**: Wallet restores may produce different results. | ||
|
Contributor
There was a problem hiding this comment. Same issue, this is also flatly incorrect. |
||
|
|
||
| **Interoperability Issues**: Users cannot reliably switch between wallet | ||
|
Contributor
There was a problem hiding this comment. Interoperability concerns are the purview of ZIP 315. If there are specific standards required for interoperability (such as standards around key handling), I would recommend that you suggest them there. |
||
| implementations. | ||
|
|
||
| # Specification | ||
|
|
||
| The deterministic scanning algorithm processes blocks in strict sequential order | ||
| by height, processes transactions within each block in deterministic order, | ||
| and processes Orchard actions within each transaction in deterministic order. | ||
|
|
||
| ## Key Requirements | ||
|
|
||
| 1. **Block Processing Order**: Blocks MUST be processed in ascending height order | ||
| 2. **Transaction Processing Order**: Transactions processed by index within block | ||
| 3. **Action Processing Order**: Actions processed by index within transaction | ||
| 4. **Scope Order**: External scope actions before Internal scope actions | ||
| 5. **Deduplication**: First occurrence kept when duplicates found | ||
|
|
||
| # References | ||
|
|
||
| - ZIP 32: Shielded Hierarchical Deterministic Wallets | ||
| - ZIP 224: Orchard | ||
| - ZIP 316: Unified Addresses | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is incorrect. The state of the wallet is a function of the contents of the blockchain; the order of scanning is irrelevant (modulo implementation bugs.)