PIVX Core version 3.2.2 is now available from: https://github.com/pivx-project/pivx/releases
This is a new minor version release, including various bug fixes and performance improvements.
Please report bugs using the issue tracker at github: https://github.com/pivx-project/pivx/issues
PIVX Core v3.2.2 is a supplemental update to v3.2.0/1 containing minor bug fixes. Users are still advised to read the v3.2.0 Release Notes to familiarize themselves with the major feature changes.
While updating from v3.2.0 is not required, it is highly recommended, especially for anyone encountering the issues detailed in the Notable Changes section below.
How to Upgrade
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/PIVX-Qt (on Mac) or pivxd/pivx-qt (on Linux).
PIVX Core is extensively tested on multiple operating systems using the Linux kernel, macOS 10.10+, and Windows 7 and later.
Microsoft ended support for Windows XP on April 8th, 2014, No attempt is made to prevent installing or running the software on Windows XP, you can still do so at your own risk but be aware that there are known instabilities and issues. Please do not report issues about Windows XP to the issue tracker.
Apple released it's last Mountain Lion update August 13, 2015, and officially ended support on December 14, 2015. PIVX Core software starting with v3.2.0 will no longer run on MacOS versions prior to Yosemite (10.10). Please do not report issues about MacOS versions prior to Yosemite to the issue tracker.
PIVX Core should also work on most other Unix-like systems but is not frequently tested on them.
Minimum Supported MacOS Version
The minimum supported version of MacOS (OSX) has been moved from 10.8 Mountain Lion to 10.10 Yosemite. Users still running a MacOS version prior to Yosemite will need to upgrade their OS if they wish to continue using the latest version(s) of the PIVX Core wallet.
Improper rejection of valid blocks
A bug was discovered in the block acceptance portion of the code that resulted in rejection of otherwise valid blocks. This caused a race condition where some clients ended up on a low-difficulty chain.
This issue has been fixed, and no user funds were at risk.
More recent checkpoints have been added for mainnet. These help alleviate some of the load when (re-)syncing from the network.
3.2.2 Change log
Detailed release notes follow. This overview includes changes that affect behavior, not code moves, refactors and string updates. For convenience in locating the code changes and accompanying discussion, both the pull request and git merge commit are mentioned.
P2P Protocol and Network Code
a890dc97cd[NET] Valid forked blocks rejected fix. (furszy)
013676df00[Net] Add additional checkpoints (Fuzzbawls)
ec7993eac8[Net] Fix incorrect last checkpoint timestamp (Fuzzbawls)
Thanks to everyone who directly contributed to this release:
As well as everyone that helped with reviews and translating on Transifex, the QA team during Testing and the Node hosts supporting our Testnet.