It includes some much-requested fixes for issues such as zPIV v1 spending as well as improvement to reduce orphan rates for zPoS. This is a minor release and not mandatory to update but is highly recommended.
Some highlight changes are:
- Adjustment to zPoS properties to reduce orphaned rate
- Zerocoin re-indexing performance improvement
- zPIV v1 spending issue fix
- Peer banning issue fix
- Core improvements.
Please note that the next major update will include key performance updates to zPIV spending that should significantly improve (reduce) zPIV spending times which will in turn further improve zPIV staking performance.
If you are running wallet 3.0.6 or below, you must upgrade to 188.8.131.52 or higher to ensure your wallet is connected to the main PIVX core blockchain.
Please take the time to fully read the release notes as always:
Download the appropriate wallet binary for your OS from the links below:
For Self-compilers, please use “git checkout v3.1.1” to compile. (not master)
How to Update
As always, it is recommended to backup the existing wallet.dat file to a safe location before upgrading if you haven’t done so already via File -> Backup wallet and saving it in a different directory with a new name. If you use CLI/Linux, you can backup using the command ./pivx-cli backupwallet. If your wallet is not running currently, you can back up the file “wallet.dat” from e.g. Start -> Run -> %APPDATA%\PIVX on Windows by making a copy elsewhere.
- Gracefully exit/stop the current wallet from the wallet. (File – Exit or ./pivx-cli stop)
- Download and install the new wallet appropriate for your OS.
Linux/Rpi: Overwrite the existing executable files with the newly downloaded wallet binaries.
Windows: Install via the setup executable file and run through the setup wizard to install.
Mac OSX: Download .dmg file, open .dmg then drag PIVX icon to the applications folder icon. (copy over /Applications/PIVX-Qt)
- Re-start the wallet. (Launch from your PIVX shortcut icon or ./pivxd for linux)
- Once the wallet finishes syncing, follow this guide to ensure you are on the right network chain.
- Upgrade completed.
- Will I lose my coins after the upgrade?
No, you will not lose your coins after the upgrade. In fact, we recommend everyone to upgrade to the latest wallet to benefit from increased security & stability that comes with it.
- I’m having issues with my wallet launching, not seeing my coins, having issues syncing etc
Please check the Knowledge-base Articles here:
or open a ticket at pivx.support
or ask for help on the support channels in PIVX Discord @ https://discord.pivx.org.
- Who can I ask if I don’t know how to upgrade still?
You can ask in support channels in PIVX Discord for real-time assistance.
If you aren’t yet a member there, you can join via https://discord.pivx.org
Also can open a ticket at pivx.support for more private support…
- I’m missing some zPIV that got minted and sent to the Accumulator. Where are they?
Firstly, make sure you aren’t using the same wallet in multiple places. If so, it could be the cause as zPIV is only visible from the wallet.dat that it minted from. Also, if you have tried swapping out your wallet.dat with previous backups in an attempt to recover your zPIV, make sure to NOT delete the latest wallet.dat as your most recent zPIV minting information does not exist in your older backups, So if you have restored to an older backup, please restore back the latest wallet.dat which was used to mint those zPIV. Then please follow this KB: https://pivx.freshdesk.com/solution/articles/30000025649
- My zPIV isn’t staking?
If you have zPIV that were minted with the 3.0.6 wallet or older, they are classified as zPIV v1 and are not able to be staked even after zPoS is activated. You will need to spend them back to your own address, then re-mint them back as zPIV using the 184.108.40.206 or higher wallet. Then they will become zPIV v2 which is able to be staked.
- What is Deterministic Seed (dzPIV) & how do I use it exactly to backup/restore my zPIV?
Please see this detailed post by presstab (PIVX core developer):