Add ZIP draft "Zcash Adoption Pool (ZAP)"
Reaffirm the portion of Protocol-defined Ecosystem Funding allocated to Zcash Community Grants (ZCG), and focus on its original goal described in ZIP 1015 — to accelerate Zcash adoption as broadly as possible. To better reflect that focus and to clarify the original intent of ZIP 1015, this portion of funds will be called the "Zcash Adoption Pool".
Radar summary of the original source
An open proposal—not a live product.
Radar found activity on the original proposal source. Open means the source still lists it as open; it does not mean the proposal is approved, merged, or implemented.
- Status
- Open proposal
- Source
- Zcash Improvement Proposals
- Source activity
- Confidence
- Source-linked record
ZIPs
Zcash Improvement Proposals
Radar summary of the original source
Related activity
- Original source
ZIPs 317 and 2009: Undo the premature memo-bundle revision, and update and apply ZIP 2009
This updates ZIP 317 and ZIP 2009 in eleven commits. It is the separate PR for moving ZIP 2009 to Proposed that the revert in #1405 refers to, together with the ZIP 2009 changes that go with it. ZIP 317 These two commits come first, because they correct an earlier departure from the ZIP 0 process. Remove the draft revision for memo bundles — ZIP 231's fee changes had been applied to ZIP 317, first directly and then as the draft Revision 2, although ZIP 231 is still a Draft.
- Original source
Add draft ZIP: 10-second Block Target Spacing
Rendered. Proposes reducing the block target spacing from 25 seconds (ZIP 218, NU7) to 10 seconds in NU8. The change is limited to latency. The block subsidy, halving interval, funding-stream address periods, NSM reissuance, difficulty averaging window, block size limit and shielded action limits are all scaled by 5/2, so issuance, block space and shielded capacity per unit of time stay at their NU7 values.
Add draft ZIP: Compact Block Relay
Rendered. Proposes compact block relay for Zcash, adapting BIP 152, as tracked in #360. A compact block carries the full Zcash header, 6-byte short IDs derived from each transaction's ZIP 239 wtxid (or txid before v5), and the prefilled coinbase. The receiver rebuilds the block from its mempool, requests missing transactions once, and falls back to the full block. Peers that both opt in may announce a block extending their best tip once its header, proof of work and transaction commitments are authenticated, before full validation completes.