Zcash in Simplified Technical English
This site has the Zcash protocol specification and the Zcash Improvement Proposals (ZIPs) in Simplified Technical English (STE). STE is the controlled language of the ASD-STE100 standard. STE text has short sentences, the active voice and one word for one meaning.
The source documents at zips.z.cash are the normative text. This site is in progress. The documents below are from source commit c41951cc43.
Read the writing rules first. The STE replacements for the BCP 14 key words are in the rules.
Protocol specification
ZIPs
- ZIP 0: ZIP Process
- ZIP 1: Network Upgrade Policy and Scheduling
- ZIP 2: Design Considerations for Network Upgrades
- ZIP 68: Relative lock-time using consensus-enforced sequence numbers
- ZIP 76: Transaction Signature Validation before Overwinter
- ZIP 112: CHECKSEQUENCEVERIFY
- ZIP 113: Median Time Past as endpoint for lock-time calculations
- ZIP 129: Zcash Transparent Multisig Setup
- ZIP 143: Transaction Signature Validation for Overwinter
- ZIP 173: Bech32 Format
- ZIP 200: Network Upgrade Mechanism
- ZIP 201: Network Peer Management for Overwinter
- ZIP 202: Version 3 Transaction Format for Overwinter
- ZIP 203: Transaction Expiry
- ZIP 205: Deployment of the Sapling Network Upgrade
- ZIP 206: Deployment of the Blossom Network Upgrade
- ZIP 207: Funding Streams
- ZIP 208: Shorter Block Target Spacing
- ZIP 209: Prohibit Out-of-Range Chain Value Pool Balances
- ZIP 210: Sapling Anchor Deduplication within Transactions
- ZIP 211: Disabling Addition of New Value to the Sprout Chain Value Pool
- ZIP 212: Allow Recipient to Derive Ephemeral Secret from Note Plaintext
- ZIP 213: Shielded Coinbase
- ZIP 214: Consensus rules for a Zcash Development Fund
- ZIP 215: Explicitly Defining and Modifying Ed25519 Validation Rules
- ZIP 216: Require Canonical Jubjub Point Encodings
- ZIP 217: Aggregate Signatures
- ZIP 219: Disabling Addition of New Value to the Sapling Chain Value Pool
- ZIP 220: Zcash Shielded Assets
- ZIP 221: FlyClient - Consensus-Layer Changes
- ZIP 222: Transparent Zcash Extensions
- ZIP 223: Reduce Block Target Spacing from 25 to 20 Seconds
- ZIP 224: Orchard Shielded Protocol
- ZIP 225: Version 5 Transaction Format
- ZIP 229: Version 6 Transaction Format
- ZIP 233: Network Sustainability Mechanism: Removing Funds From Circulation
- ZIP 234: Network Sustainability Mechanism: Issuance Smoothing
- ZIP 235: Remove 60% of Transaction Fees From Circulation
- ZIP 236: Blocks should balance exactly
- ZIP 237: Network Sustainability Mechanism: Halving-Preserving Issuance
- ZIP 240: Standard Transaction Rules
- ZIP 243: Transaction Signature Validation for Sapling
- ZIP 244: Transaction Identifier Non-Malleability
- ZIP 245: Transaction Identifier Digests & Signature Validation for Transparent Zcash Extensions
- ZIP 246: Digests for the Withdrawn Version 6 Transaction Format
- ZIP 250: Deployment of the Heartwood Network Upgrade
- ZIP 251: Deployment of the Canopy Network Upgrade
- ZIP 252: Deployment of the NU5 Network Upgrade
- ZIP 253: Deployment of the NU6 Network Upgrade
- ZIP 254: Deployment of the NU7 Network Upgrade (Withdrawn)
- ZIP 255: Deployment of the NU6.1 Network Upgrade
- ZIP 256: Deployment of Consensus Bug Fixes Between NU6.1 and NU6.2
- ZIP 257: Deployment of the Orchard Temporary Vulnerability Mitigation and NU6.2 Network Upgrade
- ZIP 258: Deployment of the NU6.3 Network Upgrade
- ZIP 259: Deployment of the NU7 Network Upgrade
- ZIP 260: Extending Block Messages with Additional Authentication Data
- ZIP 270: Key Rotation for Tracked Signing Keys
- ZIP 271: Dev Fund Extension and One-Time Disbursement
- ZIP 300: Cross-chain Atomic Transactions
- ZIP 303: Sprout Payment Disclosure
- ZIP 305: Best Practices for Hardware Wallets supporting Sapling
- ZIP 306: Security Considerations for Anchor Selection
- ZIP 309: Blind Off-chain Lightweight Transactions (BOLT)
- ZIP 314: Privacy upgrades to the Zcash light client protocol
- ZIP 317: Proportional Transfer Fee Mechanism
- ZIP 319: Options for Shielded Pool Retirement
- ZIP 322: Generic Signed Message Format
- ZIP 323: Specification of getblocktemplate for Zcash
- ZIP 332: Wallet Recovery from zcashd HD Seeds
- ZIP 339: Wallet Recovery Words
- ZIP 350: Bech32m
- ZIP 402: New Wallet Database Format
- ZIP 403: Verification Behaviour of zcashd
- ZIP 416: Spending Key Derivation in the
zcashdwallet - ZIP 1001: Keep the Block Distribution as Initially Defined — 90% to Miners
- ZIP 1002: Opt-in Donation Feature
- ZIP 1003: 20% Split Evenly Between the ECC and the Zcash Foundation, and a Voting System Mandate
- ZIP 1004: Miner-Directed Dev Fund
- ZIP 1005: Zcash Community Funding System
- ZIP 1006: Development Fund of 10% to a 2-of-3 Multisig with Community-Involved Third Entity
- ZIP 1007: Enforce Development Fund Commitments with a Legal Charter
- ZIP 1008: Fund ECC for Two More Years
- ZIP 1009: Five-Entity Strategic Council
- ZIP 1010: Compromise Dev Fund Proposal With Diverse Funding Streams
- ZIP 1011: Decentralize the Dev Fee
- ZIP 1012: Dev Fund to ECC + ZF + Major Grants
- ZIP 1013: Keep It Simple, Zcashers: 10% to ECC, 10% to ZF
- ZIP 1014: Establishing a Dev Fund for ECC, ZF, and Major Grants
- ZIP 1015: Block Subsidy Allocation for Non-Direct Development Funding
- ZIP 1016: Community and Coinholder Funding Model
- ZIP 2001: Lockbox Funding Streams
- ZIP 2002: Explicit Fees
- ZIP 2003: Disallow version 4 transactions
- ZIP 2004: Remove the dependency of consensus on note encryption
- ZIP 2006: Restricting Transfers into the Orchard Pool
- ZIP 2007: Quantum Recoverability for a Subset of Transparent Addresses
- ZIP 2008: Update to
FS_FPF_ZCG_H3address list - ZIP 2009: Reduce Marginal Fee to 1000 Zatoshis and Raise the Weight Ratio Cap to 10