zcashd releases happen approximately every six weeks, although this may change if a
particular release is delayed, or if a hotfix release occurs.
zcashd release is generally supported for 16 weeks. Occasionally this changes for
individual releases (for example, near to a Network Upgrade activation).
These two policies mean that there are generally at least two separate
currently supported at any given time.
zcashd version released by ECC has an End-of-Support height. When the Zcash chain
reaches this height,
zcashd will automatically shut down, and the binary will refuse to
restart. This is for several reasons:
zcashdmaintainers do not have the resources to maintain old versions of
- Each time a user upgrades their
zcashdnode, they are re-confirming that they are happy to run the Zcash consensus rules encoded in the version of
zcashdthey are running. This is an important part of the overall strategy for changes to the node and consensus rules; users who want to follow different rules (or even just have a different End-of-Support halt policy) will obtain a
zcashdbinary from some other source, with its own support policies.
- Knowing that old versions will shut down is useful for planning backwards-incompatible
changes in Network Upgrades. A Network Upgrade activation can be targeted for a height
where we know that all released
zcashdversions which did not support the Network Upgrade will have shut down by the time the Network Upgrade activates.
The End-of-Support height for a running
zcashd can be queried over JSON-RPC using the
The following table shows End-of-Support information for recent
zcashd releases. It is
automatically updated during each release. "End of Support" dates are estimated at that
time, and may shift due to changes in network solution power.
|End of Support