Zcash guides
Zcash ZIPs: Protocol Proposals and Status
Quick Answer
Inspect a ZIP header, its full specification and a pinned source version. Treat status, planned upgrade inclusion, code changes and chain activation as separate evidence questions. The retrieved ZIP repository index lists planned NU7 documents, including ZIP 218, ZIP 235, ZIP 237, ZIP 2003 and ZIP 2008, and points to ZIP 259 for the deployment definition.
Key Takeaways
- ZIPs describe proposed or specified changes to Zcash.
- Document status, implementation support and chain activation are separate facts.
- Read the full specification and pinned source version for an upgrade.
Start with a version, not a remembered number
The retrieved ZIP repository index lists planned NU7 documents, including ZIP 218, ZIP 235, ZIP 237, ZIP 2003 and ZIP 2008, and points to ZIP 259 for the deployment definition. Planned inclusion is a repository statement about the proposal set.
It is not an activation record. For a reproducible claim, save the exact source version rather than a mutable main-branch link.
Read the metadata before the abstract
Our selected sources expose ZIP number, title, owners, Status, Created, License and discussion references. ZIP 259, ZIP 218 and ZIP 237 are Draft in the stored versions.
Their creation dates and source-check dates have different meanings: Created is document metadata, while checked_at records when this project retrieved the bytes. Neither is an activation date.
Use document differences as a review aid
An immutable before-and-after comparison gives a reviewer a bounded set of textual changes. It should include both original URLs, commits and hashes, not just a generated summary.
The local tool reports added and removed lines while preserving their original line positions. The method ignores ordering changes when identical lines are merely moved, so it is intentionally not called a semantic consensus diff.
License and evidence scope
The index says the repository contents use MIT unless an individual file says otherwise. The stored ZIP 237 declares BSD-2-Clause, illustrating why a repository-level default should not replace per-file inspection.
License text does not grant trademark or branding approval, and this local project has not completed its reuse ledger. The index is a navigation source, not a substitute for reading each proposal.
FAQ
Does merged text mean activated consensus?
No. Repository presence does not provide network, activation height, node enforcement or observed chain evidence.
Can I cite the current branch URL?
It is useful for discovery, but an immutable commit URL and retrieval hash make a specific claim reproducible after the branch changes.
Sources and Methodology
Page updated: . Source observation dates remain separate.
Source checked: 2026-10-01T16:25:34.414023+00:00
Source version and supporting details
- NU7 ZIPs: planned deployment list and pointer to ZIP 259.
- License: MIT unless otherwise stated in individual files.
a735caf76ed8d3fa0a50e4f6b706ca9dac39079b
b2cdc68621535bdd8e317f06b31ca63f3bd44f81da6babf33279ddaa512d2fb8
Source checked: 2026-10-01T16:25:35.451039+00:00
Source version and supporting details
- Header: Status Draft; License BSD-2-Clause.
a735caf76ed8d3fa0a50e4f6b706ca9dac39079b
ebd58b627baa9b5552278aa5b124002d0fcb46c6030e61ff6970303e57061216
Source checked: 2026-10-01T16:25:34.767189+00:00
Source version and supporting details
- Header fields and Draft status.
a735caf76ed8d3fa0a50e4f6b706ca9dac39079b
5e6f2b934137be8d7fc989812f9d1e66d29fbf4e35f7b621372f7d18b170e5b0
Source dates describe the referenced observation or document, not a live price. How data is checked ยท Corrections