From 2eb0ed8ef06951f25d2ff0eeeeeeac3ef7290ff4 Mon Sep 17 00:00:00 2001 From: Daira Emma Hopwood Date: Sat, 28 Oct 2023 15:34:22 +0100 Subject: [PATCH] Updates to reference BCP 14 rather than RFC 2119. fixes #729 Also change two "should"s in ZIP 224 to "SHOULD"s. Signed-off-by: Daira Emma Hopwood --- zip-0000.html | 6 +++--- zip-0000.rst | 5 +++-- zip-0032.html | 6 +++--- zip-0032.rst | 6 +++--- zip-0143.html | 6 +++--- zip-0143.rst | 5 +++-- zip-0155.html | 6 +++--- zip-0155.rst | 5 +++-- zip-0173.html | 6 +++--- zip-0173.rst | 5 +++-- zip-0200.html | 6 +++--- zip-0200.rst | 4 ++-- zip-0201.html | 6 +++--- zip-0201.rst | 4 ++-- zip-0202.html | 6 +++--- zip-0202.rst | 4 ++-- zip-0205.html | 6 +++--- zip-0205.rst | 4 ++-- zip-0206.html | 6 +++--- zip-0206.rst | 5 +++-- zip-0207.html | 6 +++--- zip-0207.rst | 5 +++-- zip-0208.html | 6 +++--- zip-0208.rst | 4 ++-- zip-0209.html | 6 +++--- zip-0209.rst | 4 ++-- zip-0210.html | 6 +++--- zip-0210.rst | 4 ++-- zip-0211.html | 6 +++--- zip-0211.rst | 4 ++-- zip-0212.html | 6 +++--- zip-0212.rst | 5 +++-- zip-0213.html | 6 +++--- zip-0213.rst | 4 ++-- zip-0214.html | 6 +++--- zip-0214.rst | 5 +++-- zip-0215.html | 6 +++--- zip-0215.rst | 4 ++-- zip-0216.html | 6 +++--- zip-0216.rst | 6 +++--- zip-0221.html | 6 +++--- zip-0221.rst | 4 ++-- zip-0222.html | 6 +++--- zip-0222.rst | 4 ++-- zip-0224.html | 10 +++++----- zip-0224.rst | 9 +++++---- zip-0225.html | 6 +++--- zip-0225.rst | 4 ++-- zip-0239.html | 6 +++--- zip-0239.rst | 5 +++-- zip-0243.html | 6 +++--- zip-0243.rst | 5 +++-- zip-0244.html | 6 +++--- zip-0244.rst | 9 +++++---- zip-0245.html | 6 +++--- zip-0245.rst | 9 +++++---- zip-0250.html | 6 +++--- zip-0250.rst | 5 +++-- zip-0251.html | 6 +++--- zip-0251.rst | 5 +++-- zip-0252.html | 6 +++--- zip-0252.rst | 4 ++-- zip-0301.html | 6 +++--- zip-0301.rst | 5 +++-- zip-0304.html | 6 +++--- zip-0304.rst | 4 ++-- zip-0307.html | 6 +++--- zip-0307.rst | 4 ++-- zip-0308.html | 6 +++--- zip-0308.rst | 5 +++-- zip-0313.html | 6 +++--- zip-0313.rst | 5 +++-- zip-0316.html | 6 +++--- zip-0316.rst | 7 ++++--- zip-0317.html | 6 +++--- zip-0317.rst | 5 +++-- zip-0321.html | 6 +++--- zip-0321.rst | 5 +++-- zip-0400.html | 6 +++--- zip-0400.rst | 4 ++-- zip-0401.html | 6 +++--- zip-0401.rst | 4 ++-- zip-1001.html | 6 +++--- zip-1001.rst | 5 +++-- zip-1002.html | 6 +++--- zip-1002.rst | 5 +++-- zip-1003.html | 6 +++--- zip-1003.rst | 5 +++-- zip-1004.html | 6 +++--- zip-1004.rst | 5 +++-- zip-1006.html | 6 +++--- zip-1006.rst | 5 +++-- zip-1007.html | 6 +++--- zip-1007.rst | 5 +++-- zip-1008.html | 6 +++--- zip-1008.rst | 4 ++-- zip-1010.html | 6 +++--- zip-1010.rst | 5 +++-- zip-1013.html | 6 +++--- zip-1013.rst | 4 ++-- zip-1014.html | 6 +++--- zip-1014.rst | 5 +++-- zip-guide.html | 6 +++--- zip-guide.rst | 5 +++-- 104 files changed, 301 insertions(+), 271 deletions(-) diff --git a/zip-0000.html b/zip-0000.html index d3a5f89d..82633d81 100644 --- a/zip-0000.html +++ b/zip-0000.html @@ -23,7 +23,7 @@ Category: Process Created: 2019-02-16 License: BSD-2-Clause

Terminology

-

The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", "MAY", "RECOMMENDED", "OPTIONAL", and "REQUIRED" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", "MAY", "RECOMMENDED", "OPTIONAL", and "REQUIRED" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

The term "network upgrade" in this document is to be interpreted as described in ZIP 200. 3

Abstract

@@ -359,11 +359,11 @@ Updates:

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0000.rst b/zip-0000.rst index 02726b7c..f9a219c9 100644 --- a/zip-0000.rst +++ b/zip-0000.rst @@ -23,7 +23,8 @@ Terminology The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", "MAY", "RECOMMENDED", "OPTIONAL", and "REQUIRED" in this document are to -be interpreted as described in RFC 2119. [#RFC2119]_ +be interpreted as described in BCP 14 [#BCP14]_ when, and only when, +they appear in all capitals. The term "network upgrade" in this document is to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -800,7 +801,7 @@ See Also References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#RFC3552] `RFC 3552: Guidelines for Writing RFC Text on Security Considerations `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ .. [#conduct] `Zcash Code of Conduct `_ diff --git a/zip-0032.html b/zip-0032.html index 333d780e..ba8a8077 100644 --- a/zip-0032.html +++ b/zip-0032.html @@ -25,7 +25,7 @@ License: MIT \(% This ZIP makes heavy use of mathematical markup. If you can see this, you may want to instead view the rendered version at https://zips.z.cash/zip-0032 .\)

Terminology

-

The key words "MUST", "MUST NOT", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "MUST NOT", and "MAY" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

"Jubjub" refers to the elliptic curve defined in 15.

A "chain code" is a cryptovalue that is needed, in addition to a spending key, in order to derive descendant keys and addresses of that key.

The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.12 of the Zcash Protocol Specification 10.

@@ -979,11 +979,11 @@ License: MIT

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0032.rst b/zip-0032.rst index 823fffa9..e702501a 100644 --- a/zip-0032.rst +++ b/zip-0032.rst @@ -20,8 +20,8 @@ Terminology =========== -The key words "MUST", "MUST NOT", and "MAY" in this document are to be interpreted as described in RFC 2119. -[#RFC2119]_ +The key words "MUST", "MUST NOT", and "MAY" in this document are to be interpreted as described +in BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. "Jubjub" refers to the elliptic curve defined in [#protocol-jubjub]_. @@ -687,7 +687,7 @@ Reference Implementation References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#bip-0032] `BIP 32: Hierarchical Deterministic Wallets `_ .. [#bip-0039] `BIP 39: Mnemonic code for generating deterministic keys `_ .. [#bip-0043] `BIP 43: Purpose Field for Deterministic Wallets `_ diff --git a/zip-0143.html b/zip-0143.html index b149066f..f162e950 100644 --- a/zip-0143.html +++ b/zip-0143.html @@ -18,7 +18,7 @@ Category: Consensus Created: 2017-12-27 License: MIT

Terminology

-

The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

The terms "consensus branch", "epoch", and "network upgrade" in this document are to be interpreted as described in ZIP 200. 10

The term "Overwinter" in this document is to be interpreted as described in ZIP 201. 11

@@ -348,11 +348,11 @@ sighash: 23652e76cb13b85a0e3363bb5fca061fa791c40c533eccee899364e6e60bb4f7

https://github.com/zcash/zcash/pull/2903

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0143.rst b/zip-0143.rst index 65c7bd59..f9b44f14 100644 --- a/zip-0143.rst +++ b/zip-0143.rst @@ -16,7 +16,8 @@ Terminology =========== -The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in RFC 2119. [#RFC2119]_ +The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in BCP 14 [#BCP14]_ +when, and only when, they appear in all capitals. The terms "consensus branch", "epoch", and "network upgrade" in this document are to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -454,7 +455,7 @@ https://github.com/zcash/zcash/pull/2903 References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol-sproutsend] `Zcash Protocol Specification, Version 2021.2.16. Section 4.7.1: Sending Notes (Sprout) `_ .. [#wiki-checksig] `OP\_CHECKSIG. Bitcoin Wiki `_ .. [#quadratic] diff --git a/zip-0155.html b/zip-0155.html index 4db409bb..bde36482 100644 --- a/zip-0155.html +++ b/zip-0155.html @@ -18,7 +18,7 @@ License: BSD-2-Clause Discussions-To: <https://github.com/zcash/zips/issues/542> Pull-Request: <https://github.com/zcash/zips/pull/543>

Terminology

-

The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", 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 term "network upgrade" in this document is to be interpreted as described in ZIP 200. 4

The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.12 of the Zcash Protocol Specification 2.

"P2P network" means the Zcash peer-to-peer network.

@@ -185,11 +185,11 @@ CHECKSUM = H(".onion checksum" || PUBKEY || VERSION)[:2] // first 2 bytes

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0155.rst b/zip-0155.rst index fbe83772..7850c3fa 100644 --- a/zip-0155.rst +++ b/zip-0155.rst @@ -17,7 +17,8 @@ Terminology =========== The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" in this -document are to be interpreted as described in RFC 2119. [#RFC2119]_ +document are to be interpreted as described in BCP 14 [#BCP14]_ when, and only +when, they appear in all capitals. The term "network upgrade" in this document is to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -237,7 +238,7 @@ Acknowledgements for BIP 155: References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol-networks] `Zcash Protocol Specification, Version 2021.2.16 [NU5 proposal]. Section 3.12 Mainnet and Testnet `_ .. [#bip-0155] `BIP 155: addrv2 message `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ diff --git a/zip-0173.html b/zip-0173.html index ee4cc528..d9fa2969 100644 --- a/zip-0173.html +++ b/zip-0173.html @@ -18,7 +18,7 @@ Category: Standards / Wallet Created: 2018-06-13 License: MIT

Terminology

-

The key words "MUST", "MUST NOT", "SHOULD", and "SHOULD NOT" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "MUST NOT", "SHOULD", and "SHOULD NOT" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

The term "network upgrade" in this document is to be interpreted as described in ZIP 200. 4

The term "Sapling" in this document is to be interpreted as described in ZIP 205. 5

@@ -350,11 +350,11 @@ def bech32_verify_checksum(hrp, data):

This document is closely based on BIP 173 written by Pieter Wuille and Greg Maxwell, which was inspired by the address proposal by Rusty Russell and the base32 proposal by Mark Friedenbach. BIP 173 also had input from Luke Dashjr, Johnson Lau, Eric Lombrozo, Peter Todd, and various other reviewers.

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0173.rst b/zip-0173.rst index fc023f61..4df7105b 100644 --- a/zip-0173.rst +++ b/zip-0173.rst @@ -17,7 +17,8 @@ Terminology =========== The key words "MUST", "MUST NOT", "SHOULD", and "SHOULD NOT" in this document are -to be interpreted as described in RFC 2119. [#RFC2119]_ +to be interpreted as described in BCP 14 [#BCP14]_ when, and only when, they appear +in all capitals. The term "network upgrade" in this document is to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -461,7 +462,7 @@ Eric Lombrozo, Peter Todd, and various other reviewers. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later `_ .. [#zip-0032] `ZIP 32: Shielded Hierarchical Deterministic Wallets `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ diff --git a/zip-0200.html b/zip-0200.html index c8757dd4..6e5259b9 100644 --- a/zip-0200.html +++ b/zip-0200.html @@ -14,7 +14,7 @@ Category: Consensus Created: 2018-01-08 License: MIT

Terminology

-

The key words "MUST", "SHOULD", "SHOULD NOT", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "SHOULD", "SHOULD NOT", 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 terms below are to be interpreted as follows:

Block chain
@@ -117,11 +117,11 @@ License: MIT

https://github.com/zcash/zcash/pull/2898

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0200.rst b/zip-0200.rst index d379ba53..5b373337 100644 --- a/zip-0200.rst +++ b/zip-0200.rst @@ -13,7 +13,7 @@ Terminology =========== The key words "MUST", "SHOULD", "SHOULD NOT", and "MAY" in this document are to be interpreted as -described in RFC 2119. [#RFC2119]_ +described in BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The terms below are to be interpreted as follows: @@ -223,7 +223,7 @@ https://github.com/zcash/zcash/pull/2898 References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#consensual-currency] `Consensual Currency. Electric Coin Company blog `_ .. [#release-lifecycle] - `Release Cycle and Lifetimes. Electric Coin Company blog `_ diff --git a/zip-0201.html b/zip-0201.html index 73d525da..70d0e687 100644 --- a/zip-0201.html +++ b/zip-0201.html @@ -15,7 +15,7 @@ Category: Network Created: 2018-01-15 License: MIT

Terminology

-

The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "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 terms "consensus branch" and "network upgrade" in this document are to be interpreted as described in ZIP 200. 3

The terms below are to be interpreted as follows:

@@ -185,11 +185,11 @@ if (nActivationHeight > 0 &&

https://github.com/zcash/zcash/pull/2919

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0201.rst b/zip-0201.rst index 833d7c88..9d2de1e9 100644 --- a/zip-0201.rst +++ b/zip-0201.rst @@ -14,7 +14,7 @@ Terminology =========== The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted as described -in RFC 2119. [#RFC2119]_ +in BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The terms "consensus branch" and "network upgrade" in this document are to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -248,7 +248,7 @@ https://github.com/zcash/zcash/pull/2919 References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#zip-0143] `ZIP 143: Transaction Signature Validation for Overwinter `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ .. [#zip-0202] `ZIP 202: Version 3 Transaction Format for Overwinter `_ diff --git a/zip-0202.html b/zip-0202.html index 02be1243..a6d148ba 100644 --- a/zip-0202.html +++ b/zip-0202.html @@ -15,7 +15,7 @@ Category: Consensus Created: 2018-01-10 License: MIT

Terminology

-

The key words "MUST", "MUST NOT", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "MUST NOT", 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 terms "consensus branch", "network upgrade", and "consensus rule change" in this document are to be interpreted as described in ZIP 200. 3

The term "Overwinter" in this document is to be interpreted as described in ZIP 201. 4

@@ -331,11 +331,11 @@ License: MIT

https://github.com/zcash/zcash/pull/2925

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0202.rst b/zip-0202.rst index a3bba95a..b14d9394 100644 --- a/zip-0202.rst +++ b/zip-0202.rst @@ -14,7 +14,7 @@ Terminology =========== The key words "MUST", "MUST NOT", and "MAY" in this document are to be interpreted as described in -RFC 2119. [#RFC2119]_ +BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The terms "consensus branch", "network upgrade", and "consensus rule change" in this document are to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -281,7 +281,7 @@ https://github.com/zcash/zcash/pull/2925 References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#zip-0143] `ZIP 143: Transaction Signature Validation for Overwinter `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ .. [#zip-0201] `ZIP 201: Network Handshaking for Overwinter `_ diff --git a/zip-0205.html b/zip-0205.html index 40c80552..92b534ca 100644 --- a/zip-0205.html +++ b/zip-0205.html @@ -15,7 +15,7 @@ Category: Consensus / Network Created: 2018-10-08 License: MIT

Terminology

-

The key words "MUST" and "SHOULD" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST" and "SHOULD" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

The terms "consensus branch" and "network upgrade" in this document are to be interpreted as described in ZIP 200. 7

The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.12 of the Zcash Protocol Specification 3.

The terms below are to be interpreted as follows:

@@ -74,11 +74,11 @@ static const int NETWORK_UPGRADE_PEER_PREFERENCE_BLOCK_PERIOD = 24 * 24 * 3;Support for Sapling consensus rules was implemented in zcashd version 2.0.0. The majority of support for RPC calls and persistence of Sapling z-addresses was implemented in version 2.0.1. Both of these versions advertise protocol version 170007.

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0205.rst b/zip-0205.rst index b66e2269..7d7e2833 100644 --- a/zip-0205.rst +++ b/zip-0205.rst @@ -14,7 +14,7 @@ Terminology =========== The key words "MUST" and "SHOULD" in this document are to be interpreted as -described in RFC 2119. [#RFC2119]_ +described in BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The terms "consensus branch" and "network upgrade" in this document are to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -143,7 +143,7 @@ version 170007. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later `_ .. [#protocol-networks] `Zcash Protocol Specification, Version 2021.2.16. Section 3.12: Mainnet and Testnet `_ .. [#protocol-constants] `Zcash Protocol Specification, Version 2021.2.16. Section 5.3: Constants `_ diff --git a/zip-0206.html b/zip-0206.html index e73bc1e5..de5170f5 100644 --- a/zip-0206.html +++ b/zip-0206.html @@ -15,7 +15,7 @@ Category: Consensus / Network Created: 2019-07-29 License: MIT

Terminology

-

The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "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 term "network upgrade" in this document is to be interpreted as described in ZIP 200. 3

The terms below are to be interpreted as follows:

@@ -71,11 +71,11 @@ static const int NETWORK_UPGRADE_PEER_PREFERENCE_BLOCK_PERIOD = 24 * 24 * 3;Support for Blossom on testnet is implemented in zcashd version 2.0.7, which advertises protocol version 170008. Support for Blossom on mainnet is implemented in zcashd version 2.1.0, which advertises protocol version 170009.

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0206.rst b/zip-0206.rst index 0f0af270..aacf3952 100644 --- a/zip-0206.rst +++ b/zip-0206.rst @@ -14,7 +14,8 @@ Terminology =========== The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be -interpreted as described in RFC 2119. [#RFC2119]_ +interpreted as described in BCP 14 [#BCP14]_ when, and only when, they appear in +all capitals. The term "network upgrade" in this document is to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -121,7 +122,7 @@ in ``zcashd`` version 2.1.0, which advertises protocol version 170009. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ .. [#zip-0201] `ZIP 201: Network Peer Management for Overwinter `_ diff --git a/zip-0207.html b/zip-0207.html index e73a6917..1fa6890e 100644 --- a/zip-0207.html +++ b/zip-0207.html @@ -16,7 +16,7 @@ Category: Consensus Created: 2019-01-04 License: MIT

Terminology

-

The key words "MUST", "SHOULD", "SHOULD NOT", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "SHOULD", "SHOULD NOT", 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 terms "block subsidy" and "halving" in this document are to be interpreted as described in sections 3.9 and 7.7 of the Zcash Protocol Specification. 3 7

The terms "consensus branch" and "network upgrade" in this document are to be interpreted as described in ZIP 200. 10

The terms below are to be interpreted as follows:

@@ -223,11 +223,11 @@ License: MIT

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0207.rst b/zip-0207.rst index 2923a09e..0667aad1 100644 --- a/zip-0207.rst +++ b/zip-0207.rst @@ -14,7 +14,8 @@ Terminology =========== The key words "MUST", "SHOULD", "SHOULD NOT", and "MAY" in this document are -to be interpreted as described in RFC 2119. [#RFC2119]_ +to be interpreted as described in BCP 14 [#BCP14]_ when, and only when, they +appear in all capitals. The terms "block subsidy" and "halving" in this document are to be interpreted as described in sections 3.9 and 7.7 of the Zcash Protocol Specification. @@ -233,7 +234,7 @@ Reference Implementation References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later `_ .. [#protocol-subsidyconcepts] `Zcash Protocol Specification, Version 2021.2.16. Section 3.10: Block Subsidy and Founders' Reward `_ .. [#protocol-networks] `Zcash Protocol Specification, Version 2021.2.16. Section 3.12: Mainnet and Testnet `_ diff --git a/zip-0208.html b/zip-0208.html index b2a1c4ec..d406ec64 100644 --- a/zip-0208.html +++ b/zip-0208.html @@ -17,7 +17,7 @@ Created: 2019-01-10 License: MIT Pull-Request: <https://github.com/zcash/zips/pull/237>

Terminology

-

The key words "MUST" and "SHOULD" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST" and "SHOULD" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

The terms "block chain", "consensus rule change", "consensus branch", and "network upgrade" are to be interpreted as defined in 9.

The term "block target spacing" means the time interval between blocks targeted by the difficulty adjustment algorithm in a given consensus branch. It is normally measured in seconds. (This is also sometimes called the "target block time", but "block target spacing" is the term used in the Zcash Protocol Specification 6.)

The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.12 of the Zcash Protocol Specification 4.

@@ -203,11 +203,11 @@ static const int NETWORK_UPGRADE_PEER_PREFERENCE_BLOCK_PERIOD = 1728;

https://github.com/zcash/zcash/pull/4025

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0208.rst b/zip-0208.rst index 8d12848d..d85ffe77 100644 --- a/zip-0208.rst +++ b/zip-0208.rst @@ -16,7 +16,7 @@ Terminology =========== The key words "MUST" and "SHOULD" in this document are to be interpreted as -described in RFC 2119. [#RFC2119]_ +described in BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The terms "block chain", "consensus rule change", "consensus branch", and "network upgrade" are to be interpreted as defined in [#zip-0200]_. @@ -394,7 +394,7 @@ https://github.com/zcash/zcash/pull/4025 References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#preblossom-protocol] `Zcash Protocol Specification, Version 2018.0-beta-37 (exactly) `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later `_ .. [#protocol-networks] `Zcash Protocol Specification, Version 2021.2.16. Section 3.12: Mainnet and Testnet `_ diff --git a/zip-0209.html b/zip-0209.html index 4305bd1a..ba8a2191 100644 --- a/zip-0209.html +++ b/zip-0209.html @@ -15,7 +15,7 @@ Category: Consensus Created: 2019-02-25 License: MIT

Terminology

-

The key words "MUST", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "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 term "block chain" and "network upgrade" are to be interpreted as defined in 3.

The "Sprout chain value pool balance" for a given block chain is the sum of all vpub_old fields for transactions in the block chain, minus the sum of all vpub_new fields for transactions in the block chain.

The "Sapling chain value pool balance" for a given block chain is the negation of the sum of all valueBalanceSapling fields for transactions in the block chain.

@@ -39,11 +39,11 @@ License: MIT

This specification was deployed in zcashd v2.0.4 for Testnet, and in zcashd v2.0.5 for Mainnet. The application to the Orchard chain value pool balance will be deployed from NU5 activation 4.

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0209.rst b/zip-0209.rst index d29cf189..5f11cb9c 100644 --- a/zip-0209.rst +++ b/zip-0209.rst @@ -14,7 +14,7 @@ Terminology =========== The key words "MUST", "SHOULD", and "MAY" in this document are to be interpreted as described in -RFC 2119. [#RFC2119]_ +BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The term "block chain" and "network upgrade" are to be interpreted as defined in [#zip-0200]_. @@ -83,7 +83,7 @@ The application to the Orchard chain value pool balance will be deployed from NU References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol-networks] `Zcash Protocol Specification, Version 2021.2.16 or later. Section 3.12: Mainnet and Testnet `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ .. [#zip-0252] `ZIP 252: Deployment of the NU5 Network Upgrade `_ diff --git a/zip-0210.html b/zip-0210.html index 54e535d3..259d861b 100644 --- a/zip-0210.html +++ b/zip-0210.html @@ -17,7 +17,7 @@ License: MIT

This ZIP has been withdrawn because a similar change has been incorporated into the ZIP 225 proposal for a version 5 transaction format. 5

Terminology

-

The key words "MUST" and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST" 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 term "network upgrade" in this document is to be interpreted as described in ZIP 200 3.

The term "Sapling" in this document is to be interpreted as described in ZIP 205 4.

@@ -50,11 +50,11 @@ License: MIT

TBD

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0210.rst b/zip-0210.rst index 822335b4..bee141a9 100644 --- a/zip-0210.rst +++ b/zip-0210.rst @@ -20,7 +20,7 @@ Terminology =========== The key words "MUST" and "MAY" in this document are to be interpreted as described in -RFC 2119. [#RFC2119]_ +BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The term "network upgrade" in this document is to be interpreted as described in ZIP 200 [#zip-0200]_. @@ -112,7 +112,7 @@ TBD References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol-txnencoding] `Zcash Protocol Specification, Version 2021.2.16. Section 7.1: Transaction Encoding and Consensus `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ .. [#zip-0205] `ZIP 205: Deployment of the Sapling Network Upgrade `_ diff --git a/zip-0211.html b/zip-0211.html index 99dc5705..dbf97a69 100644 --- a/zip-0211.html +++ b/zip-0211.html @@ -15,7 +15,7 @@ Category: Consensus Created: 2019-03-29 License: MIT

Terminology

-

The key words "MUST", "SHOULD", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "SHOULD", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

The term "network upgrade" in this document is to be interpreted as described in ZIP 200 3.

The term "Sprout shielded protocol" in this document refers to the shielded payment protocol defined at the launch of the Zcash network.

The term "Sapling shielded protocol" in this document refers to the shielded payment protocol introduced in the Sapling network upgrade 4 2.

@@ -62,11 +62,11 @@ License: MIT

https://github.com/zcash/zcash/pull/4489

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0211.rst b/zip-0211.rst index 5508d48f..3c9c07db 100644 --- a/zip-0211.rst +++ b/zip-0211.rst @@ -14,7 +14,7 @@ Terminology =========== The key words "MUST", "SHOULD", and "OPTIONAL" in this document are to be interpreted -as described in RFC 2119. [#RFC2119]_ +as described in BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The term "network upgrade" in this document is to be interpreted as described in ZIP 200 [#zip-0200]_. @@ -143,7 +143,7 @@ https://github.com/zcash/zcash/pull/4489 References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ .. [#zip-0205] `ZIP 205: Deployment of the Sapling Network Upgrade `_ diff --git a/zip-0212.html b/zip-0212.html index bbfe42bf..613b4d12 100644 --- a/zip-0212.html +++ b/zip-0212.html @@ -15,7 +15,7 @@ Category: Consensus Created: 2019-03-31 License: MIT

Terminology

-

The key words "MUST", "MUST NOT", "SHOULD NOT", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "MUST NOT", "SHOULD NOT", 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 following functions are defined in the Zcash Protocol Specification 2 according to the type (Sapling or Orchard) of note plaintext being processed:

  • let @@ -280,11 +280,11 @@ License: MIT

    The discovery that diversified address unlinkability depended on the zk-SNARK knowledge assumption was made by Sean Bowe and Zooko Wilcox.

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0212.rst b/zip-0212.rst index 79954c98..f637f1ee 100644 --- a/zip-0212.rst +++ b/zip-0212.rst @@ -13,7 +13,8 @@ Terminology =========== The key words "MUST", "MUST NOT", "SHOULD NOT", and "MAY" in this document are -to be interpreted as described in RFC 2119. [#RFC2119]_ +to be interpreted as described in BCP 14 [#BCP14]_ when, and only when, they appear +in all capitals. The following functions are defined in the Zcash Protocol Specification [#protocol]_ according to the type (Sapling or Orchard) of note plaintext being processed: @@ -324,7 +325,7 @@ knowledge assumption was made by Sean Bowe and Zooko Wilcox. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later `_ .. [#protocol-abstractprfs] `Zcash Protocol Specification, Version 2021.2.16. Section 4.1.2: Pseudo Random Functions `_ .. [#protocol-abstractcommit] `Zcash Protocol Specification, Version 2021.2.16. Section 4.1.8: Commitment `_ diff --git a/zip-0213.html b/zip-0213.html index b3c5736d..f40ada08 100644 --- a/zip-0213.html +++ b/zip-0213.html @@ -14,7 +14,7 @@ Category: Consensus Created: 2019-03-30 License: MIT

Terminology

-

The key words "MUST" and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST" 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 term "network upgrade" in this document is to be interpreted as described in ZIP 200 2.

The term "Sapling" in this document is to be interpreted as described in ZIP 205 3.

The terms "Founders' Reward" and "funding stream" in this document are to be interpreted as described in ZIP 207 4.

@@ -77,11 +77,11 @@ License: MIT

https://github.com/zcash/zcash/pull/4256

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0213.rst b/zip-0213.rst index fea99b37..5914317a 100644 --- a/zip-0213.rst +++ b/zip-0213.rst @@ -13,7 +13,7 @@ Terminology =========== The key words "MUST" and "MAY" in this document are to be interpreted as described in -RFC 2119. [#RFC2119]_ +BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The term "network upgrade" in this document is to be interpreted as described in ZIP 200 [#zip-0200]_. @@ -199,7 +199,7 @@ https://github.com/zcash/zcash/pull/4256 References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ .. [#zip-0205] `ZIP 205: Deployment of the Sapling Network Upgrade `_ .. [#zip-0207] `ZIP 207: Split Founders' Reward `_ diff --git a/zip-0214.html b/zip-0214.html index ae2bff3c..4c52384a 100644 --- a/zip-0214.html +++ b/zip-0214.html @@ -15,7 +15,7 @@ Created: 2020-02-28 License: MIT Discussions-To: <https://forum.zcashcommunity.com/t/community-sentiment-polling-results-nu4-and-draft-zip-1014/35560>

Terminology

-

The key words "MUST", "SHALL", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "SHALL", "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 term "Zcash" in this document is to be interpreted as described in the Zcash Trademark Donation and License Agreement (6 or successor agreement).

The term "network upgrade" in this document is to be interpreted as described in ZIP 200 8 and the Zcash Trademark Donation and License Agreement (6 or successor agreement).

The term "block subsidy" in this document is to be interpreted as described in section 3.10 of the Zcash Protocol Specification 3.

@@ -267,11 +267,11 @@ FS_ZIP214_MG.AddressList[0..50] = ["t2Gvxv2uNM7hbbACjNox4H6DjByoKZ2Fa3P"] * 51This proposal is intended to be deployed with Canopy. 11

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0214.rst b/zip-0214.rst index 62902537..5d8871d3 100644 --- a/zip-0214.rst +++ b/zip-0214.rst @@ -14,7 +14,8 @@ Terminology =========== The key words "MUST", "SHALL", "SHOULD", and "MAY" in this document are to be -interpreted as described in RFC 2119. [#RFC2119]_ +interpreted as described in BCP 14 [#BCP14]_ when, and only when, they appear +in all capitals. The term "Zcash" in this document is to be interpreted as described in the Zcash Trademark Donation and License Agreement ([#trademark]_ or successor @@ -336,7 +337,7 @@ This proposal is intended to be deployed with Canopy. [#zip-0251]_ References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later `_ .. [#protocol-subsidyconcepts] `Zcash Protocol Specification, Version 2021.2.16. Section 3.10: Block Subsidy, Funding Streams, and Founders' Reward `_ .. [#protocol-networks] `Zcash Protocol Specification, Version 2021.2.16. Section 3.12: Mainnet and Testnet `_ diff --git a/zip-0215.html b/zip-0215.html index 9e939ba0..4fe952bc 100644 --- a/zip-0215.html +++ b/zip-0215.html @@ -15,7 +15,7 @@ Category: Consensus Created: 2020-04-27 License: BSD-2-Clause

Terminology

-

The key words "MUST" and "MUST NOT" in this document is to be interpreted as described in RFC 2119. 1

+

The key words "MUST" and "MUST NOT" in this document is to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

Abstract

Zcash uses Ed25519 signatures as part of Sprout transactions. However, Ed25519 does not clearly define criteria for signature validity, and implementations conformant to RFC 8032 2 need not agree on whether signatures are valid. This is unacceptable for a consensus-critical application like Zcash. Currently, Zcash inherits criteria for signature validity from an obsolete version of libsodium. Instead, this ZIP settles the situation by explicitly defining the Ed25519 validity criteria and changing them to be compatible with batch validation.

@@ -80,11 +80,11 @@ License: BSD-2-Clause

This is intended to be deployed with the Canopy Network Upgrade 6, which is scheduled to activate on Mainnet 4 at block height 1046400.

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0215.rst b/zip-0215.rst index 7ee618f2..25b28226 100644 --- a/zip-0215.rst +++ b/zip-0215.rst @@ -13,7 +13,7 @@ Terminology =========== The key words "MUST" and "MUST NOT" in this document is to be interpreted as described -in RFC 2119. [#RFC2119]_ +in BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. Abstract @@ -111,7 +111,7 @@ which is scheduled to activate on Mainnet [#protocol-networks]_ at block height References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#RFC8032] `RFC 8032: Edwards-Curve Digital Signature Algorithm (EdDSA) `_ .. [#protocol-2020.1.1] `Zcash Protocol Specification, Version 2020.1.1 `_ .. [#protocol-networks] `Zcash Protocol Specification, Version 2021.2.16. Section 3.12: Mainnet and Testnet `_ diff --git a/zip-0216.html b/zip-0216.html index 928022b6..482288d3 100644 --- a/zip-0216.html +++ b/zip-0216.html @@ -17,7 +17,7 @@ Created: 2021-02-11 License: MIT Discussions-To: <https://github.com/zcash/zips/issues/400>

Terminology

-

The key word "MUST" in this document is to be interpreted as described in RFC 2119. 1

+

The key word "MUST" in this document is to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

The term "network upgrade" in this document is to be interpreted as described in ZIP 200. 12

Abstract

@@ -206,11 +206,11 @@ Discussions-To: <https://g

This ZIP is proposed to activate with Network Upgrade 5. Requirements on points encoded in payment addresses and full viewing keys MAY be enforced in advance of NU5 activation.

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0216.rst b/zip-0216.rst index 70a35ecd..6fc35343 100644 --- a/zip-0216.rst +++ b/zip-0216.rst @@ -14,8 +14,8 @@ Terminology =========== -The key word "MUST" in this document is to be interpreted as described in RFC 2119. -[#RFC2119]_ +The key word "MUST" in this document is to be interpreted as described in BCP 14 [#BCP14]_ +when, and only when, they appear in all capitals. The term "network upgrade" in this document is to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -214,7 +214,7 @@ payment addresses and full viewing keys MAY be enforced in advance of NU5 activa References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later [NU5 proposal] `_ .. [#protocol-spenddesc] `Zcash Protocol Specification, Version 2021.2.16 [NU5 proposal]. Section 4.4: Spend Descriptions `_ .. [#protocol-outputdesc] `Zcash Protocol Specification, Version 2021.2.16 [NU5 proposal]. Section 4.5: Output Descriptions `_ diff --git a/zip-0221.html b/zip-0221.html index 1f6d6862..a4e119e7 100644 --- a/zip-0221.html +++ b/zip-0221.html @@ -18,7 +18,7 @@ Category: Consensus Created: 2019-03-30 License: MIT

Terminology

-

The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST", "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 terms "consensus branch", "epoch", and "network upgrade" in this document are to be interpreted as described in ZIP 200. 8

Light client
@@ -661,11 +661,11 @@ License: MIT

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0221.rst b/zip-0221.rst index 144fcfb2..74b42e15 100644 --- a/zip-0221.rst +++ b/zip-0221.rst @@ -16,7 +16,7 @@ Terminology =========== The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted -as described in RFC 2119. [#RFC2119]_ +as described in BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The terms "consensus branch", "epoch", and "network upgrade" in this document are to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -827,7 +827,7 @@ Additional Reading References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#FlyClient] `FlyClient protocol `_ .. [#protocol-blockheader] `Zcash Protocol Specification, Version 2021.2.16. Section 7.6: Block Header Encoding and Consensus `_ .. [#protocol-workdef] `Zcash Protocol Specification, Version 2021.2.16. Section 7.7.5: Definition of Work `_ diff --git a/zip-0222.html b/zip-0222.html index 23a61f08..33e2237b 100644 --- a/zip-0222.html +++ b/zip-0222.html @@ -18,7 +18,7 @@ Category: Consensus Created: 2019-07-01 License: MIT

Terminology

-

The key words "MUST" and "MAY" in this document are to be interpreted as described in RFC 2119. 1

+

The key words "MUST" 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 term "network upgrade" in this document is to be interpreted as described in ZIP 200 6.

The term "prefix-free" in this document is to be interpreted as to mean that no valid encoding of a value may have the same binary representation as any prefix of the binary encoding of another value of the same type.

The term "non-malleable" in this document is to be interpreted as described in ZIP 244 7.

@@ -286,11 +286,11 @@ nShieldedSpend, and nJoinSplit MUST be nonzero in

References

- +
- +
1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
diff --git a/zip-0222.rst b/zip-0222.rst index 019e81ee..156e65ee 100644 --- a/zip-0222.rst +++ b/zip-0222.rst @@ -17,7 +17,7 @@ Terminology =========== The key words "MUST" and "MAY" in this document are to be interpreted as described in -RFC 2119. [#RFC2119]_ +BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The term "network upgrade" in this document is to be interpreted as described in ZIP 200 [#zip-0200]_. @@ -321,7 +321,7 @@ at Zcon1 that led to the earlier draft version of this ZIP. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later `_ .. [#protocol-constants] `Zcash Protocol Specification, Version 2021.2.16. Section 5.3: Constants `_ .. [#protocol-txnconsensus] `Zcash Protocol Specification, Version 2021.2.16. Section 7.1: Transaction Consensus Rules `_ diff --git a/zip-0224.html b/zip-0224.html index 53085db3..dfde043b 100644 --- a/zip-0224.html +++ b/zip-0224.html @@ -20,7 +20,7 @@ Created: 2021-02-27 License: MIT Discussions-To: <https://github.com/zcash/zips/issues/435>

Terminology

-

The key word "MUST" in this document is to be interpreted as described in RFC 2119. 1

+

The key words "MUST" and "SHOULD" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.12 of the Zcash Protocol Specification 5.

Abstract

@@ -164,9 +164,9 @@ Discussions-To: <https://g
  • The "transparent turnstile" created by the \(\mathsf{valueBalanceOrchard}\) field, combined with the consensus checks that each pool's balance cannot be negative, together enforce that any potential counterfeiting bugs in the Orchard protocol or implementation are contained within the Orchard pool, and similarly any potential counterfeiting bugs in existing shielded pools cannot cause inflation of the Orchard pool.
    • -
  • Spending funds residing in the Orchard pool to a non-Orchard address will reveal the value of the transaction. This is a necessary side-effect of the transparent turnstile, but can be mitigated by migrating the majority of shielded activity to the Orchard pool and making these transactions a minority. Wallets should convey within their transaction creation UX that amounts are revealed in these situations. +
  • Spending funds residing in the Orchard pool to a non-Orchard address will reveal the value of the transaction. This is a necessary side-effect of the transparent turnstile, but can be mitigated by migrating the majority of shielded activity to the Orchard pool and making these transactions a minority. Wallets SHOULD convey within their transaction creation UX that amounts are revealed in these situations.
    • @@ -186,11 +186,11 @@ Discussions-To: <https://g

    This ZIP is proposed to activate with Network Upgrade 5.

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0224.rst b/zip-0224.rst index 8fa69faf..789750bc 100644 --- a/zip-0224.rst +++ b/zip-0224.rst @@ -17,7 +17,8 @@ Terminology =========== -The key word "MUST" in this document is to be interpreted as described in RFC 2119. [#RFC2119]_ +The key words "MUST" and "SHOULD" in this document are to be interpreted as described in +BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.12 of the Zcash Protocol Specification [#protocol-networks]_. @@ -248,10 +249,10 @@ considerations: - Spending funds residing in the Orchard pool to a non-Orchard address will reveal the value of the transaction. This is a necessary side-effect of the transparent turnstile, but can be mitigated by migrating the majority of shielded activity to the Orchard pool - and making these transactions a minority. Wallets should convey within their transaction + and making these transactions a minority. Wallets SHOULD convey within their transaction creation UX that amounts are revealed in these situations. - - Wallets should take steps to migrate their user bases to store funds uniformly within + - Wallets SHOULD take steps to migrate their user bases to store funds uniformly within the Orchard pool. Best practices for wallet handling of multiple pools will be covered in a subsequent ZIP. [#zip-0315]_ @@ -278,7 +279,7 @@ This ZIP is proposed to activate with Network Upgrade 5. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#zcash-paramgen] `Parameter Generation `_ .. [#bctv14-vuln] `Zcash Counterfeiting Vulnerability Successfully Remediated `_ .. [#protocol-orchard] `Zcash Protocol Specification, Version 2021.2.16 or later [NU5 proposal] `_ diff --git a/zip-0225.html b/zip-0225.html index 650f1ed3..2830d955 100644 --- a/zip-0225.html +++ b/zip-0225.html @@ -20,7 +20,7 @@ Created: 2021-02-28 License: MIT Discussions-To: <https://github.com/zcash/zips/issues/440>

    Terminology

    -

    The key words "MUST" and "MAY" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST" 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.

    Abstract

    @@ -471,11 +471,11 @@ Discussions-To: <https://g

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0225.rst b/zip-0225.rst index d70c5d64..08b7c2ea 100644 --- a/zip-0225.rst +++ b/zip-0225.rst @@ -18,7 +18,7 @@ Terminology =========== The key words "MUST" and "MAY" in this document are to be interpreted as described in -RFC 2119. [#RFC2119]_ +BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The character § is used when referring to sections of the Zcash Protocol Specification [#protocol]_. @@ -321,7 +321,7 @@ Reference implementation References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later [NU5 proposal] `_ .. [#protocol-spenddesc] `Zcash Protocol Specification, Version 2021.2.16 [NU5 proposal]. Section 4.4: Spend Descriptions `_ .. [#protocol-outputdesc] `Zcash Protocol Specification, Version 2021.2.16 [NU5 proposal]. Section 4.5: Output Descriptions `_ diff --git a/zip-0239.html b/zip-0239.html index 6cae71ea..4d09ee36 100644 --- a/zip-0239.html +++ b/zip-0239.html @@ -17,7 +17,7 @@ License: MIT Discussions-To: <https://github.com/zcash/zips/issues/515> Pull-Request: <https://github.com/zcash/zips/pull/516>

    Terminology

    -

    The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "RECOMMENDED" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "RECOMMENDED" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

    The term "network upgrade" in this document is to be interpreted as described in ZIP 200. 4

    The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.12 of the Zcash Protocol Specification 2.

    The term "txid" means a transaction identifier, computed as a SHA-256d hash of the transaction data for v4 and earlier transactions, or as specified in 6 for v5 and later transactions.

    @@ -68,11 +68,11 @@ Pull-Request: <https://githu

    This ZIP is partly based on BIP 339, written by Suhas Daftuar. 9

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0239.rst b/zip-0239.rst index a8d5c581..65ff5cd8 100644 --- a/zip-0239.rst +++ b/zip-0239.rst @@ -16,7 +16,8 @@ Terminology =========== The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "RECOMMENDED" in this -document are to be interpreted as described in RFC 2119. [#RFC2119]_ +document are to be interpreted as described in BCP 14 [#BCP14]_ when, and only when, +they appear in all capitals. The term "network upgrade" in this document is to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -189,7 +190,7 @@ This ZIP is partly based on BIP 339, written by Suhas Daftuar. [#bip-0339]_ References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol-networks] `Zcash Protocol Specification, Version 2021.2.16 [NU5 proposal]. Section 3.12 Mainnet and Testnet `_ .. [#protocol-txnencoding] `Zcash Protocol Specification, Version 2021.2.16 [NU5 proposal]. Section 7.1: Transaction Encoding and Consensus `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ diff --git a/zip-0243.html b/zip-0243.html index 5d2c371f..2e497df5 100644 --- a/zip-0243.html +++ b/zip-0243.html @@ -16,7 +16,7 @@ Category: Consensus Created: 2018-04-10 License: MIT

    Terminology

    -

    The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

    The terms "consensus branch", "epoch", and "network upgrade" in this document are to be interpreted as described in ZIP 200. 5

    The term "Sapling" in this document is to be interpreted as described in ZIP 205. 6

    @@ -443,11 +443,11 @@ vJoinSplit: 00

    https://github.com/zcash/zcash/pull/3233

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0243.rst b/zip-0243.rst index fae782f2..e1190850 100644 --- a/zip-0243.rst +++ b/zip-0243.rst @@ -14,7 +14,8 @@ Terminology =========== -The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in RFC 2119. [#RFC2119]_ +The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in BCP 14 [#BCP14]_ +when, and only when, they appear in all capitals. The terms "consensus branch", "epoch", and "network upgrade" in this document are to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -527,7 +528,7 @@ https://github.com/zcash/zcash/pull/3233 References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, version 2021.2.16 or later `_ .. [#BLAKE2-personalization] `"BLAKE2: simpler, smaller, fast as MD5", Section 2.8 `_ .. [#zip-0143] `ZIP 143: Transaction Signature Validation for Overwinter `_ diff --git a/zip-0244.html b/zip-0244.html index c00e0490..8cc9b216 100644 --- a/zip-0244.html +++ b/zip-0244.html @@ -18,7 +18,7 @@ Created: 2021-01-06 License: MIT Discussions-To: <https://github.com/zcash/zips/issues/411>

    Terminology

    -

    The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

    The terms "consensus branch", "epoch", and "network upgrade" in this document are to be interpreted as described in ZIP 200. 3

    The term "field encoding" refers to the binary serialized form of a Zcash transaction field, as specified in section 7.1 of the Zcash protocol specification 2.

    @@ -436,11 +436,11 @@ terminator [0u8;32]

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0244.rst b/zip-0244.rst index a107e772..496ae133 100644 --- a/zip-0244.rst +++ b/zip-0244.rst @@ -16,10 +16,11 @@ Terminology =========== -The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in RFC 2119. [#RFC2119]_ +The key words "MUST" and "MUST NOT" in this document are to be interpreted as described +in BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. -The terms "consensus branch", "epoch", and "network upgrade" in this document are to be interpreted as -described in ZIP 200. [#zip-0200]_ +The terms "consensus branch", "epoch", and "network upgrade" in this document are to be +interpreted as described in ZIP 200. [#zip-0200]_ The term "field encoding" refers to the binary serialized form of a Zcash transaction field, as specified in section 7.1 of the Zcash protocol specification @@ -881,7 +882,7 @@ Reference implementation References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol-txnencoding] `Zcash Protocol Specification, Version 2021.2.16 [NU5 proposal]. Section 7.1: Transaction Encoding and Consensus `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ .. [#zip-0221] `ZIP 221: FlyClient - Consensus Layer Changes `_ diff --git a/zip-0245.html b/zip-0245.html index 82acf618..63ad4c9b 100644 --- a/zip-0245.html +++ b/zip-0245.html @@ -15,7 +15,7 @@ Created: 2021-01-13 License: MIT Discussions-To: <https://github.com/zcash/zips/issues/384>

    Terminology

    -

    The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

    The terms "consensus branch", "epoch", and "network upgrade" in this document are to be interpreted as described in ZIP 200. 2

    Abstract

    @@ -122,11 +122,11 @@ A.4: sapling_auth_digest (32-byte hash output)

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0245.rst b/zip-0245.rst index 5748cc81..e8350a52 100644 --- a/zip-0245.rst +++ b/zip-0245.rst @@ -13,10 +13,11 @@ Terminology =========== -The key words "MUST" and "MUST NOT" in this document are to be interpreted as described in RFC 2119. [#RFC2119]_ +The key words "MUST" and "MUST NOT" in this document are to be interpreted as described +in BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. -The terms "consensus branch", "epoch", and "network upgrade" in this document are to be interpreted as -described in ZIP 200. [#zip-0200]_ +The terms "consensus branch", "epoch", and "network upgrade" in this document are to be +interpreted as described in ZIP 200. [#zip-0200]_ Abstract @@ -189,7 +190,7 @@ Reference implementation References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ .. [#zip-0222] `ZIP 222: Transparent Zcash Extensions `_ .. [#zip-0244] `ZIP 244: Transaction Identifier Non-Malleability `_ diff --git a/zip-0250.html b/zip-0250.html index 746d59af..aac84c5c 100644 --- a/zip-0250.html +++ b/zip-0250.html @@ -14,7 +14,7 @@ Category: Consensus / Network Created: 2020-02-28 License: MIT

    Terminology

    -

    The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST", "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 term "network upgrade" in this document is to be interpreted as described in ZIP 200. 3

    The terms below are to be interpreted as follows:

    @@ -74,11 +74,11 @@ static const int NETWORK_UPGRADE_PEER_PREFERENCE_BLOCK_PERIOD = 1728;

    Support for Heartwood on testnet will be implemented in zcashd version 2.1.2, which will advertise protocol version 170010. Support for Heartwood on mainnet will be implemented in zcashd version 3.0.0, which will advertise protocol version 170011.

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0250.rst b/zip-0250.rst index 304498f5..755c56c5 100644 --- a/zip-0250.rst +++ b/zip-0250.rst @@ -13,7 +13,8 @@ Terminology =========== The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be -interpreted as described in RFC 2119. [#RFC2119]_ +interpreted as described in BCP 14 [#BCP14]_ when, and only when, they appear in +all capitals. The term "network upgrade" in this document is to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -127,7 +128,7 @@ be implemented in ``zcashd`` version 3.0.0, which will advertise protocol versio References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ .. [#zip-0201] `ZIP 201: Network Peer Management for Overwinter `_ diff --git a/zip-0251.html b/zip-0251.html index 1322980c..8cbbc612 100644 --- a/zip-0251.html +++ b/zip-0251.html @@ -14,7 +14,7 @@ Category: Consensus / Network Created: 2020-02-28 License: MIT

    Terminology

    -

    The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST", "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 term "network upgrade" in this document is to be interpreted as described in ZIP 200. 5

    The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.12 of the Zcash Protocol Specification 3.

    "Canopy" is the code-name for the fifth Zcash network upgrade, also known as Network Upgrade 4.

    @@ -71,11 +71,11 @@ static const int NETWORK_UPGRADE_PEER_PREFERENCE_BLOCK_PERIOD = 1728;

    Support for Canopy on testnet will be implemented in zcashd version 3.1.0, which will advertise protocol version 170012. Support for Canopy on mainnet will be implemented in zcashd version 4.0.0, which will advertise protocol version 170013.

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0251.rst b/zip-0251.rst index d75d0767..f9e30de8 100644 --- a/zip-0251.rst +++ b/zip-0251.rst @@ -13,7 +13,8 @@ Terminology =========== The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be -interpreted as described in RFC 2119. [#RFC2119]_ +interpreted as described in BCP 14 [#BCP14]_ when, and only when, they appear in +all capitals. The term "network upgrade" in this document is to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -127,7 +128,7 @@ in ``zcashd`` version 4.0.0, which will advertise protocol version 170013. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later `_ .. [#protocol-networks] `Zcash Protocol Specification, Version 2021.2.16. Section 3.12: Mainnet and Testnet `_ .. [#protocol-txnencoding] `Zcash Protocol Specification, Version 2021.2.16. Section 7.1: Transaction Encoding and Consensus `_ diff --git a/zip-0252.html b/zip-0252.html index 2aea508f..326ce077 100644 --- a/zip-0252.html +++ b/zip-0252.html @@ -17,7 +17,7 @@ License: MIT Discussions-To: <https://github.com/zcash/zips/issues/440> Pull-Request: <https://github.com/zcash/zips/pull/446>

    Terminology

    -

    The key words "MUST" and "SHOULD" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST" and "SHOULD" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

    The term "network upgrade" in this document is to be interpreted as described in ZIP 200. 6

    The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.12 of the Zcash Protocol Specification 3.

    @@ -123,11 +123,11 @@ static const int NETWORK_UPGRADE_PEER_PREFERENCE_BLOCK_PERIOD = 1728;

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0252.rst b/zip-0252.rst index 83133433..a7a291bc 100644 --- a/zip-0252.rst +++ b/zip-0252.rst @@ -16,7 +16,7 @@ Terminology =========== The key words "MUST" and "SHOULD" in this document are to be interpreted as -described in RFC 2119. [#RFC2119]_ +described in BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The term "network upgrade" in this document is to be interpreted as described in ZIP 200. [#zip-0200]_ @@ -222,7 +222,7 @@ peers, and reject new connections from pre-NU5 peers. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol] `Zcash Protocol Specification, Version 2021.2.16 or later `_ .. [#protocol-networks] `Zcash Protocol Specification, Version 2021.2.16 [NU5 proposal]. Section 3.12: Mainnet and Testnet `_ .. [#protocol-txnencoding] `Zcash Protocol Specification, Version 2021.2.16 [NU5 proposal]. Section 7.1: Transaction Encoding and Consensus `_ diff --git a/zip-0301.html b/zip-0301.html index 798c6be4..d575f647 100644 --- a/zip-0301.html +++ b/zip-0301.html @@ -19,7 +19,7 @@ Category: Standards / Ecosystem Created: 2016-09-23 License: MIT

    Terminology

    -

    The key words "MUST", "MUST NOT", "SHOULD", "MAY", and "RECOMMENDED" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST", "MUST NOT", "SHOULD", "MAY", and "RECOMMENDED" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

    Abstract

    This ZIP describes the Zcash variant of the Stratum protocol, used by miners to communicate with mining pool servers.

    @@ -342,11 +342,11 @@ License: MIT

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0301.rst b/zip-0301.rst index 772338ed..5c05bc03 100644 --- a/zip-0301.rst +++ b/zip-0301.rst @@ -18,7 +18,8 @@ Terminology =========== The key words "MUST", "MUST NOT", "SHOULD", "MAY", and "RECOMMENDED" in this -document are to be interpreted as described in RFC 2119. [#RFC2119]_ +document are to be interpreted as described in BCP 14 [#BCP14]_ when, and only +when, they appear in all capitals. Abstract @@ -488,7 +489,7 @@ Thanks to: References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol-blockheader] `Zcash Protocol Specification, Version 2020.1.15. Section 7.3: Block Headers `_ .. [#protocol-difficulty] `Zcash Protocol Specification, Version 2020.1.15. Section 7.6.2: Difficulty filter `_ .. [#Slushpool-Stratum] `Stratum Mining Protocol. Slush Pool `_ diff --git a/zip-0304.html b/zip-0304.html index 040f2e09..df9d5d80 100644 --- a/zip-0304.html +++ b/zip-0304.html @@ -19,7 +19,7 @@ License: MIT Discussions-To: <https://github.com/zcash/zips/issues/345> Pull-Request: <https://github.com/zcash/zips/pull/376>

    Terminology

    -

    The key words "MUST" and "SHOULD" in this document is to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST" and "SHOULD" in this document is to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

    Abstract

    This proposal describes a mechanism for creating signatures with Sapling addresses, suitable for use by the signmessage and verifymessage RPC methods in zcashd.

    @@ -310,11 +310,11 @@ Pull-Request: <https://githu

    https://github.com/zcash/librustzcash/pull/210

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0304.rst b/zip-0304.rst index 7c6b5492..a0e48b94 100644 --- a/zip-0304.rst +++ b/zip-0304.rst @@ -17,7 +17,7 @@ Terminology =========== The key words "MUST" and "SHOULD" in this document is to be interpreted as described in -RFC 2119. [#RFC2119]_ +BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. Abstract @@ -275,7 +275,7 @@ https://github.com/zcash/librustzcash/pull/210 References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#RFC4648] `RFC 4648: The Base16, Base32, and Base64 Data Encodings `_ .. [#protocol] `Zcash Protocol Specification, Version 2020.1.15 or later `_ .. [#protocol-merklepath] `Zcash Protocol Specification, Version 2020.1.15. Section 4.8: Merkle path validity `_ diff --git a/zip-0307.html b/zip-0307.html index e0b75774..ed49efa1 100644 --- a/zip-0307.html +++ b/zip-0307.html @@ -18,7 +18,7 @@ Status: Draft Created: 2018-09-17 License: MIT

    Terminology

    -

    The key words "MUST", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST", "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 terms below are to be interpreted as follows:

    Light client
    @@ -523,11 +523,11 @@ License: MIT

    This proposal is supported by a set of libraries and reference code made available by the Electric Coin Company.

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0307.rst b/zip-0307.rst index d840f636..cfc65bf1 100644 --- a/zip-0307.rst +++ b/zip-0307.rst @@ -16,7 +16,7 @@ Terminology =========== The key words "MUST", "SHOULD", and "MAY" in this document are to be interpreted as -described in RFC 2119. [#RFC2119]_ +described in BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. The terms below are to be interpreted as follows: @@ -608,7 +608,7 @@ Electric Coin Company. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol-merkletree] `Zcash Protocol Specification, Version 2020.1.15. Section 3.7: Note Commitment Trees `_ .. [#protocol-merklepath] `Zcash Protocol Specification, Version 2020.1.15. Section 4.8: Merkle Path Validity `_ .. [#protocol-saplingdecryptivk] `Zcash Protocol Specification, Version 2020.1.15. Section 4.17.2: Decryption using an Incoming Viewing Key (Sapling) `_ diff --git a/zip-0308.html b/zip-0308.html index b1ab5c31..169ea644 100644 --- a/zip-0308.html +++ b/zip-0308.html @@ -16,7 +16,7 @@ Category: Standards / RPC / Wallet Created: 2018-11-27 License: MIT

    Terminology

    -

    The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST", "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 terms below are to be interpreted as follows:

    Sprout protocol
    @@ -230,11 +230,11 @@ License: MIT

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0308.rst b/zip-0308.rst index bca93ed0..5ea28402 100644 --- a/zip-0308.rst +++ b/zip-0308.rst @@ -15,7 +15,8 @@ Terminology =========== The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to -be interpreted as described in RFC 2119. [#RFC2119]_ +be interpreted as described in BCP 14 [#BCP14]_ when, and only when, they +appear in all capitals. The terms below are to be interpreted as follows: @@ -426,7 +427,7 @@ The following PRs implement this specification: References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#transparent-value-pool] `Zcash Protocol Specification, Version 2020.1.15. Sections 3.4, 4.11 and 4.12 `_ .. [#zip-0032] `ZIP 32: Shielded Hierarchical Deterministic Wallets `_ .. [#zip-0205] `ZIP 205: Deployment of the Sapling Network Upgrade `_ diff --git a/zip-0313.html b/zip-0313.html index 36ef86c4..f992628c 100644 --- a/zip-0313.html +++ b/zip-0313.html @@ -20,7 +20,7 @@ License: MIT Discussions-To: <https://forum.zcashcommunity.com/t/zip-reduce-default-shielded-transaction-fee-to-1000-zats/37566> Pull-Request: <https://github.com/zcash/zips/pull/408>

    Terminology

    -

    The key words "SHOULD" and "RECOMMENDED" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "SHOULD" and "RECOMMENDED" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

    The term "conventional transaction fee" in this document is in reference to the value of a transaction fee that is conventionally used by wallets, and that a user can reasonably expect miners on the Zcash network to accept for including a transaction in a block.

    Abstract

    @@ -84,11 +84,11 @@ Pull-Request: <https://githu

    Thanks to Nathan Wilcox for suggesting improvements to the denial of service section. Thanks to Daira Emma Hopwood and Deirdre Connolly for reviewing and fixing the wording in this ZIP.

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0313.rst b/zip-0313.rst index 765bca51..185b7845 100644 --- a/zip-0313.rst +++ b/zip-0313.rst @@ -19,7 +19,8 @@ Terminology =========== The key words "SHOULD" and "RECOMMENDED" in this document are to be -interpreted as described in RFC 2119. [#RFC2119]_ +interpreted as described in BCP 14 [#BCP14]_ when, and only when, they +appear in all capitals. The term "conventional transaction fee" in this document is in reference to the value of a transaction fee that is conventionally used by wallets, @@ -205,7 +206,7 @@ the wording in this ZIP. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#nathan-1] `Conventional Shielded Fees `_ .. [#ian-1] `Ian Miers. Mechanism for fee suggester/oracle `_ .. [#zooko-1] `Zooko Wilcox. Tweet on reducing tx fees `_ diff --git a/zip-0316.html b/zip-0316.html index 96a4ad61..6cc68afa 100644 --- a/zip-0316.html +++ b/zip-0316.html @@ -24,7 +24,7 @@ Created: 2021-04-07 License: MIT Discussions-To: <https://github.com/zcash/zips/issues/482>

    Terminology

    -

    The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST", "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 terms below are to be interpreted as follows:

    Recipient
    @@ -732,11 +732,11 @@ c^{n+m}}{q}.\)

    The authors would like to thank Benjamin Winston, Zooko Wilcox, Francisco Gindre, Marshall Gaucher, Joseph Van Geffen, Brad Miller, Deirdre Connolly, Teor, Eran Tromer, Conrado Gouvêa, and Marek Bielik for discussions on the subject of Unified Addresses and Unified Viewing Keys.

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0316.rst b/zip-0316.rst index d4618b05..19f6d13b 100644 --- a/zip-0316.rst +++ b/zip-0316.rst @@ -21,8 +21,9 @@ Terminology =========== -The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are to -be interpreted as described in RFC 2119. [#RFC2119]_ +The key words "MUST", "MUST NOT", "SHOULD", and "MAY" in this document are +to be interpreted as described in BCP 14 [#BCP14]_ when, and only when, they +appear in all capitals. The terms below are to be interpreted as follows: @@ -1028,7 +1029,7 @@ Unified Addresses and Unified Viewing Keys. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol-nu5] `Zcash Protocol Specification, Version 2022.2.19 or later [NU5 proposal] `_ .. [#protocol-notation] `Zcash Protocol Specification, Version 2022.2.19. Section 2: Notation `_ .. [#protocol-saplingkeycomponents] `Zcash Protocol Specification, Version 2022.2.19. Section 4.2.2: Sapling Key Components `_ diff --git a/zip-0317.html b/zip-0317.html index acbb8520..25c198c7 100644 --- a/zip-0317.html +++ b/zip-0317.html @@ -23,7 +23,7 @@ License: MIT Discussions-To: <https://forum.zcashcommunity.com/t/zip-proportional-output-fee-mechanism-pofm/42808> Pull-Request: <https://github.com/zcash/zips/pull/631>

    Terminology

    -

    The key words "SHOULD", "SHOULD NOT", "RECOMMENDED", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "SHOULD", "SHOULD NOT", "RECOMMENDED", 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 term "conventional transaction fee" in this document is in reference to the value of a transaction fee that is conventionally used by wallets, and that a user can reasonably expect miners on the Zcash network to accept for including a transaction in a block.

    The terms "Mainnet, "Testnet", and "zatoshi" in this document are defined as in 2.

    @@ -495,11 +495,11 @@ Pull-Request: <https://githu

    Thanks to Madars Virza for initially proposing a fee mechanism similar to that proposed in this ZIP 5, and for finding a potential weakness in an earlier version of the block template construction algorithm. Thanks also to Kris Nuttycombe, Jack Grigg, Francisco Gindre, Greg Pfeil, Teor, and Deirdre Connolly for reviews and suggested improvements.

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0317.rst b/zip-0317.rst index b40bdc4e..ef38249b 100644 --- a/zip-0317.rst +++ b/zip-0317.rst @@ -21,7 +21,8 @@ Terminology =========== The key words "SHOULD", "SHOULD NOT", "RECOMMENDED", and "MAY" in this document -are to be interpreted as described in RFC 2119. [#RFC2119]_ +are to be interpreted as described in BCP 14 [#BCP14]_ when, and only when, they +appear in all capitals. The term "conventional transaction fee" in this document is in reference to the value of a transaction fee that is conventionally used by wallets, @@ -567,7 +568,7 @@ Deirdre Connolly for reviews and suggested improvements. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#protocol-networks] `Zcash Protocol Specification, Version 2022.3.8. Section 3.12: Mainnet and Testnet `_ .. [#protocol-txnencoding] `Zcash Protocol Specification, Version 2022.3.8. Section 7.1: Transaction Encoding and Consensus `_ .. [#sigop-limit] `zcash/zips issue #568 - Document block transparent sigops limit consensus rule `_ diff --git a/zip-0321.html b/zip-0321.html index 28e9753d..9bf60824 100644 --- a/zip-0321.html +++ b/zip-0321.html @@ -17,7 +17,7 @@ Discussions-To: <https://g Pull-Request: <https://github.com/zcash/zips/pull/395> License: MIT

    Terminology

    -

    The key words "MUST", "MUST NOT", "SHOULD", "RECOMMENDED", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST", "MUST NOT", "SHOULD", "RECOMMENDED", 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 terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.11 of the Zcash Protocol Specification 10.

    The terms below are to be interpreted as follows:

    @@ -140,11 +140,11 @@ zcash:%74mEZhbWHTpdKMw5it8YDspUXSMGQyFwovpU?amount=1

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0321.rst b/zip-0321.rst index f71ec0e4..99a720da 100644 --- a/zip-0321.rst +++ b/zip-0321.rst @@ -16,7 +16,8 @@ Terminology =========== The key words "MUST", "MUST NOT", "SHOULD", "RECOMMENDED", and "MAY" in this -document are to be interpreted as described in RFC 2119. [#RFC2119]_ +document are to be interpreted as described in BCP 14 [#BCP14]_ when, and only +when, they appear in all capitals. The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.11 of the Zcash Protocol Specification [#protocol-networks]_. @@ -310,7 +311,7 @@ of old clients to upgrade. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#RFC5234] `RFC 5234: Augmented BNF for Syntax Specifications: ABNF `_ .. [#RFC3986] `RFC 3986: URI Generic Syntax, Appendix A. Collected ABNF for URI `_ .. [#base64url] `RFC 4648 section 5: Base64 Encoding with URL and Filename Safe Alphabet `_ diff --git a/zip-0400.html b/zip-0400.html index 704bb007..430a6516 100644 --- a/zip-0400.html +++ b/zip-0400.html @@ -14,7 +14,7 @@ Category: Wallet Created: 2020-05-26 License: MIT

    Terminology

    -

    The key words "MUST" and "MAY" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST" and "MAY" in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.

    Abstract

    This proposal defines the current format used in zcashd for wallet persistent storage, commonly known as wallet.dat.

    @@ -469,11 +469,11 @@ License: MIT

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0400.rst b/zip-0400.rst index c146771a..b692cd67 100644 --- a/zip-0400.rst +++ b/zip-0400.rst @@ -13,7 +13,7 @@ Terminology =========== The key words "MUST" and "MAY" in this document are to be interpreted as described in -RFC 2119. [#RFC2119]_ +BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. Abstract ======== @@ -141,7 +141,7 @@ For a deeper understanding of the current encryption mechanism please refer to [ References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#BDB] `Oracle Berkeley Database `_ .. [#ZIP400Issue] `ZIP 400 issue `_ .. [#zip-0032] `ZIP 32: Shielded Hierarchical Deterministic Wallets `_ diff --git a/zip-0401.html b/zip-0401.html index 4fb5fee7..9061762f 100644 --- a/zip-0401.html +++ b/zip-0401.html @@ -15,7 +15,7 @@ Category: Network Created: 2019-09-09 License: MIT

    Terminology

    -

    The key words "MUST", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119. 1

    +

    The key words "MUST", "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.

    Abstract

    This proposal specifies a change to the behaviour of zcashd nodes intended to mitigate denial-of-service from transaction flooding.

    @@ -87,11 +87,11 @@ License: MIT

    References

    - +
    - +
    1RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
    diff --git a/zip-0401.rst b/zip-0401.rst index 8adc4342..49521c62 100644 --- a/zip-0401.rst +++ b/zip-0401.rst @@ -13,7 +13,7 @@ Terminology =========== The key words "MUST", "SHOULD", and "MAY" in this document are to be interpreted -as described in RFC 2119. [#RFC2119]_ +as described in BCP 14 [#BCP14]_ when, and only when, they appear in all capitals. Abstract @@ -232,7 +232,7 @@ Reference implementation References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#zip-0208] `ZIP 208: Shorter Block Target Spacing `_ .. [#zip-0239] `ZIP 239: Relay of Version 5 Transactions `_ .. [#zip-0252] `ZIP 252: Deployment of the NU5 Network Upgrade `_ diff --git a/zip-1001.html b/zip-1001.html index 9873bcfc..8aeb5808 100644 --- a/zip-1001.html +++ b/zip-1001.html @@ -15,7 +15,7 @@ Created: 2019-08-01 License: CC BY-SA 4.0 <https://creativecommons.org/licenses/by-sa/4.0/> Discussions-To: <https://forum.zcashcommunity.com/t/zip-proposal-keep-the-block-distribution-as-initaly-defined-90-to-miners/33843>

    Terminology

    -

    The key words "MUST", "MUST NOT", "SHOULD", and "SHOULD NOT" in this document are to be interpreted as described in RFC 2119. 2

    +

    The key words "MUST", "MUST NOT", "SHOULD", and "SHOULD NOT" in this document are to be interpreted as described in BCP 14 2 when, and only when, they appear in all capitals.

    For clarity this ZIP defines these terms:

    • Mining software in the context of this ZIP refers to pool software, local mining software, or staking software.
      • @@ -76,11 +76,11 @@ Discussions-To: <

      References

      - +
      - +
      2RFC 2119: Key words for use in RFCs to Indicate Requirement LevelsInformation 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"
      diff --git a/zip-1001.rst b/zip-1001.rst index 1353b1b4..1644ef61 100644 --- a/zip-1001.rst +++ b/zip-1001.rst @@ -16,7 +16,8 @@ Terminology .. role:: editor-note The key words "MUST", "MUST NOT", "SHOULD", and "SHOULD NOT" in this document -are to be interpreted as described in RFC 2119. [#RFC2119]_ +are to be interpreted as described in BCP 14 [#BCP14]_ when, and only when, +they appear in all capitals. For clarity this ZIP defines these terms: @@ -107,7 +108,7 @@ This ZIP requires no changes to current consensus implementations. References ========== -.. [#RFC2119] `RFC 2119: Key words for use in RFCs to Indicate Requirement Levels `_ +.. [#BCP14] `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" `_ .. [#funding] `Zcash blog: Funding, Incentives, and Governance. February 1, 2016 `_ .. [#spec-subsidies] `Zcash Protocol Specification, Version 2019.0.8 exactly. Section 7.7: Calculation of Block Subsidy and Founders Reward `_ .. [#spec-foundersreward] `Zcash Protocol Specification, Version 2019.0.8 exactly. Section 7.8: Payment of Founders’ Reward `_ diff --git a/zip-1002.html b/zip-1002.html index 49eb7f0d..35a0b102 100644 --- a/zip-1002.html +++ b/zip-1002.html @@ -15,7 +15,7 @@ Created: 2019-07-17 License: CC BY-SA 4.0 <https://creativecommons.org/licenses/by-sa/4.0/> Discussions-To: <https://forum.zcashcommunity.com/t/zip-proposal-a-genuine-opt-in-protocol-level-development-donation-option/33846>

      Terminology

      -

      The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" in this document are to be interpreted as described in RFC 2119. 3

      +

      The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" in this document are to be interpreted as described in BCP 14 3 when, and only when, they appear in all capitals.

      This ZIP defines these terms: