Skip to content

v2.0.21
Compare
Choose a tag to compare
@cronicc cronicc released this 20 May 04:24
v2.0.21
This tag was signed with the committer’s verified signature.
cronicc
GPG key ID: FB7053CE4991B669
Learn about vigilant mode.
567d66e
This commit was signed with the committer’s verified signature.
cronicc
GPG key ID: FB7053CE4991B669
Learn about vigilant mode.

Binaries

Windows and macOS binaries are signed with a valid certificate,
see included instructions.txt for Win/Mac command line wallets.

Install

Debian package dependencies:

Depends amd64: libc6 (>= 2.18), libgcc1 (>= 1:4.2), libgomp1 (>= 4.9), libstdc++6 (>= 5.2)
Depends arm64: libc6 (>= 2.25), libgcc1 (>= 1:4.2), libgomp1 (>= 4.9), libstdc++6 (>= 7)

Notable Changes

  • Fix for upstream CVE-2020-8806
    • Changes how nodes enforce timestamp requirements on block headers. Miners and pools should make sure the blocks they generate conform to the new stricter timestamp requirements. Getblocktemplate will always provide a valid timestamp. For details see https://electriccoin.co/blog/new-releases-2-1-1-and-hotfix-2-1-1-1/
    • This change will be deployed by soft-fork on mainnet block 740600 (v2.0.20 mainnet deprecation +8d) and on testnet block 651100 (v2.0.20 mainnet deprecation -7d), pools have the opportunity to test on testnet in the 2 weeks leading up to the mainnet soft-fork.
  • Removal of time adjustment
    • Prior to v2.0.21, zend would adjust the local time that it used by up to 70 minutes, according to a median of the times sent by the first 200 peers to connect to it. This mechanism was inherently insecure, since an adversary making multiple connections to the node could effectively control its time within that +/- 70 minute window (this is called a "timejacking attack"). In the v2.0.21 release, in addition to other mitigations for timejacking attacks, as a simplification the time adjustment code has now been completely removed. Node operators should instead simply ensure that local time is set reasonably accurately. If it appears that the node has a significantly different time than its peers, a warning will still be logged and indicated on the metrics screen if enabled.
  • Introduce new optional parameter sendChangeToSource to zen-cli z_sendmany 
    (boolean, optional, default = false) If true and fromaddress is a taddress return the change to it
  • The deprecation/release cycle has been changed to 26 weeks/bianually
    • next deprecation to occur 2 weeks before the next block reward halving
Assets 14
Loading