TL;DR: The 4.5.0, 4.5.1, and 4.5.1-1 zcashd nodes will reach End of Service on or about January 10th, 2022. Prior to that time, miners must upgrade to 4.6.0-1 and all other testnet and mainnet nodes should upgrade to either 4.6.0 or 4.6.0-1.
TL;DR: The 4.5.0, 4.5.1, and 4.5.1-1 zcashd nodes will reach End of Service on or about January 10, 2022. Prior to that time, all testnet and mainnet nodes should upgrade
It has become clear that the best way for ECC to contribute to the Zcash community over the next three years is to release an official ECC wallet on top of a highly interoperable Zcash protocol that leverages proof-of-stake consensus.
NU5 security assessments are complete, and no serious or critical issues were found in either audit.
This is a required update for all testnet nodes, and is highly recommended for mainnet nodes if you were using the deprecated getaddressesbyaccount RPC method.
The code preparations for the Network Upgrade 5 consensus rules are finished and included in this release. The following ZIPs are being deployed: ZIP 216: Require Canonical Jubjub Point Encodings
Electric Coin Co. (ECC) has entered into an agreement with Protocol Labs, the Filecoin Foundation, and the Ethereum Foundation to explore Halo R&D, including how the technology might be used in their respective ecosystems.
A successful transition to Proof of Stake would necessarily require support from Zcash users, a legitimate governance process, and a well designed technical migration process. This post outlines what the technical migration process might look like at the top level.
Nighthawk Wallet iOS and ECC Reference Wallet iOS users should upgrade to the latest versions in order to remediate a security vulnerability. No other wallets are affected by this bug,
The 4.3.0 release included a change to prevent redundant getheaders P2P requests, to reduce node bandwidth usage. This behaviour could be disabled by setting the config option -nooptimize-getheaders.
zcashd can now be configured to optionally expose an HTTP server that acts as a Prometheus scrape endpoint. The server will respond to GET requests on any request path.
UAs make Zcash easier to use by removing the complexity of multiple address types. This simplifies the user experience — no more juggling addresses — and increases interoperability between shielded-only applications and transparent-only applications.
