This page is the Simplified Technical English version of ZIP 206. The source ZIP is the normative text. Read the writing rules to understand the marked words.
ZIP 206: Deployment of the Blossom Network Upgrade
ZIP: 206 Title: Deployment of the Blossom Network Upgrade Owners: Daira-Emma Hopwood <daira@jacaranda.org> Credits: Simon Liu Status: Final Category: Consensus / Network Created: 2019-07-29 License: MIT
Terminology
On this page, STE words are in the place of the BCP 14 key words of the source. Refer to the key word table.
In this document, the term "network upgrade" has the definition in ZIP 200 [zip-0200].
These terms have the definitions that follow:
- Blossom
- The code-name of the third Zcash network upgrade. This network upgrade also has the name Network Upgrade 2.
- Testnet
- The Zcash test network. Its definition is in [protocol].
- Mainnet
- The Zcash production network. Its definition is in [protocol].
Abstract
This ZIP contains the definition of the deployment of the Blossom network upgrade.
Specification
Blossom deployment
The primary sources of information about the consensus protocol changes for Blossom are:
- The Zcash Protocol Specification [protocol].
- Shorter Block Target Spacing [zip-0208].
- Network Upgrade Mechanism [zip-0200].
The mechanisms for the network handshake and for peer management that are defined in [zip-0201] also apply to this network upgrade.
These are the network upgrade constants [zip-0200] for the Blossom network upgrade:
- CONSENSUS_BRANCH_ID
0x2BB40E60- ACTIVATION_HEIGHT (Blossom)
-
Testnet: 584000
Mainnet: 653600
Nodes that are compatible with Blossom activation on testnet must advertise protocol version 170008 or later. Nodes that are compatible with Blossom activation on mainnet must advertise protocol version 170009 or later. The minimum peer protocol version that Blossom-compatible nodes connect to is 170002.
Pre-Blossom testnet nodes are nodes on testnet that advertise a protocol version less than 170008. Pre-Blossom mainnet nodes are nodes on mainnet that advertise a protocol version less than 170009.
For each network (testnet and mainnet), nodes that are compatible with Blossom activation on that network change the behaviour of their peer connection logic. The nodes make this change approximately three days before the Blossom activation height of that network. (The three days are defined in terms of block height.) With this change, the nodes prefer pre-Blossom peers on that network for eviction from the set of peer connections:
/** The period before a network upgrade activates, where connections to upgrading peers are preferred (in blocks). */ static const int NETWORK_UPGRADE_PEER_PREFERENCE_BLOCK_PERIOD = 24 * 24 * 3;
The implementation is similar to the implementation for Overwinter. The description of the Overwinter implementation is in [zip-0201].
After Blossom activation on testnet or mainnet, we recommend that Blossom nodes take steps to do these two things:
- Reject new connections from pre-Blossom nodes on that network.
- Disconnect all existing connections to pre-Blossom nodes on that network.
Backward compatibility
Before the activation of the network upgrade on each network, Blossom nodes and pre-Blossom nodes are compatible and can connect to each other. But Blossom nodes prefer to connect to other Blossom nodes. Thus pre-Blossom nodes are gradually disconnected in the period immediately before activation.
After the activation of the network upgrade, pre-Blossom nodes can still accept the numerically larger protocol version of Blossom as valid. But after the activation, Blossom nodes always disconnect peers that use lower protocol versions.
There is no new transaction version for Blossom. This is different from Overwinter and Sapling. Thus Blossom transactions are in the same v4 format as Sapling transactions. Blossom transactions also have the same version group ID. That is, the version group ID is 0x892F2085, as defined in section 7.1 of [protocol]. This does not mean that transactions are valid across the Blossom activation, because the applicable consensus branch ID must be used for signatures.
Support in zcashd
zcashd version 2.0.7 implements support for Blossom on testnet. That zcashd version advertises protocol version 170008. zcashd version 2.1.0 implements support for Blossom on mainnet. That zcashd version advertises protocol version 170009.
References
- [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
- [zip-0208]
- ZIP 208: Shorter Block Target Spacing