ZIP: Unassigned {numbers are assigned by ZIP editors}
Title: {Something Short and To the Point}
Owners: First Owner <email>
        ...
Credits: First Credited
         ...
Status: Draft
Category: {Consensus | Standards Track | Network | RPC | Wallet | Informational | Process}
Created: yyyy-mm-dd
License: {usually MIT}
Pull-Request: <https://github.com/zcash/zips/pull/???>

Terminology

{Edit this to reflect the key words that are actually used.} The key words “MUST”, “REQUIRED”, “MUST NOT”, “SHOULD”, and “MAY” in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

The character § is used when referring to sections of the Zcash Protocol Specification. 2

The terms “Mainnet” and “Testnet” are to be interpreted as described in § 3.12 ‘Mainnet and Testnet’. 3

The term “full validator” in this document is to be interpreted as defined in § 3.3 ‘The Block Chain’. 4.

The terms below are to be interpreted as follows:

{Term to be defined}

:{Definition.}

{Another term}

:{Definition.}

Abstract

Motivation

Privacy Implications

Requirements

Non-requirements

Specification

{details heading}

{ details body }


Rationale

Deployment

Reference implementation

Open issues

References


  1. Information on BCP 14 — “RFC 2119: Key words for use in RFCs to Indicate Requirement Levels” and “RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words”  ↩︎

  2. Zcash Protocol Specification, Version 2025.6.3 [NU6.1] or later  ↩︎

  3. protocol-networks  ↩︎

  4. Zcash Protocol Specification, Version 2025.6.3 [NU6.1]. Section 3.3: The Block Chain  ↩︎