Changes to release notes.
This commit is contained in:
parent
7d21fdb582
commit
7095fa9307
|
@ -2,7 +2,7 @@ Notable changes
|
||||||
===============
|
===============
|
||||||
|
|
||||||
This release fixes a security issue described at
|
This release fixes a security issue described at
|
||||||
https://z.cash/support/security/announcements/security-announcement-2020-02-05/ .
|
https://z.cash/support/security/announcements/security-announcement-2020-02-06/ .
|
||||||
|
|
||||||
This release also adds a `-maxtimeadjustment` option to set the maximum time, in
|
This release also adds a `-maxtimeadjustment` option to set the maximum time, in
|
||||||
seconds, by which the node's clock can be adjusted based on the clocks of its
|
seconds, by which the node's clock can be adjusted based on the clocks of its
|
||||||
|
@ -11,6 +11,12 @@ This is a change from the previous behaviour, which was to adjust the clock by u
|
||||||
to 70 minutes forward or backward. The maximum setting for this option is now
|
to 70 minutes forward or backward. The maximum setting for this option is now
|
||||||
25 minutes (1500 seconds).
|
25 minutes (1500 seconds).
|
||||||
|
|
||||||
|
Fix for incorrect banning of nodes during syncing
|
||||||
|
-------------------------------------------------
|
||||||
|
After activation of the Blossom network upgrade, a node that is syncing the
|
||||||
|
block chain from before Blossom would incorrectly ban peers that send it a
|
||||||
|
Blossom transaction. This resulted in slower and less reliable syncing (#4283).
|
||||||
|
|
||||||
Changelog
|
Changelog
|
||||||
=========
|
=========
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue