PivX has released a new mandatory update for all masternode holders, which was carried out on 30th August 2019 for the mainnet. The new PIVX Core Wallet 3.4.0 brings long-awaited updates and fixes. Continue reading for more details.
3.4.0 Update Notes
The new wallet version brings major changes to the network, which are a welcome sight. They are divided into a few categories – Core Updates, GUI Changes, RPC Changes, Build and Test System Updates.
Internal (Core) Updates
The first major change is the implementation of a Version 2 Stake Modifier, which is a 256-bit modifier that gets computed at every block. It works by taking the hash modifier of the previous block along with the input of the coinstake. Thus, in order for the protocol to work, the Proof of Stake kernel must refer to the modifier of the previous block. This change is scheduled to occur at testnet block 1,214,000 and mainnet block 1,967,000.
The next update is the elimination of needless key generation in the network. The whole staking process has been improved in order to not request an unused key from the keypool anymore. This should reduce wallet bloat and improve the efficiency of staking. Talking about efficiency, block index writes are now done in batches, improving the performance and reducing data corruption risks. Also, the odd wallet crashes on startup have been fixed as well.
Wallet GUI Changes
One of the more major changes for the GUI wallet is the removal of zero-fee transactions. This is because PivX needs to review its long-term viability. Additionally, quality of life change has been made to the information tab of the UI’s console window. A display is added showing both current data directory and the latest block hash seen by the client.
RPC, Testing Suite and Build System Updates
We have combined the last three categories as they are quick to cover. Both the preparebudget and submitbudget RPC commands will now require the inclusion of a canonical URL Scheme as part of their url parameter. The mentioned url field has also been changed to fit only 64 characters, so a URL shortening method may be necessary.
The Testing Suite is present in the update with changes to the functional testing readability. Maybe the most important aspect of it is that now failing scripts will be printed as outputs. The Build system also underwent changes. The configure step will now show more information upon failure due to an unsupported OpenSSL. The long-term plan is to make sure that the future consensus code does not depend on OpenSSL in any way.
Updating to the New Version
Before you start to update your Core wallet, we recommend backing it up first in a safe location. This can be done by accessing the File menu and then selecting the Backup wallet function in the GUI. For the CLI users, you can use the ./pivx-cli backupwallet command. Alternatively, if your wallet is not correctly running and you are using Windows OS, you can use the RUN function and type in %APPDATA%\PIVX. Then, you can freely copy the wallet.dat file in a safe location.
Starting the Update
- Stop and Exit the current wallet from “File” -> “Exit” or ./pivx-cli stop for CLI users
- Download and install the new wallet from the official PIVX Website. Make sure you download the one appropriate for your OS
- How to install for differed OS:
- Linux / Raspberry Pi – Overwrite the existing wallet binaries with the new ones
- Windows OS – Install from the .exe file with the setup wizard
- Mac OSx – Download and open the .dmg file, then drag the PIVX icon to the app folder icon
- Start the wallet from the new shortcut
- After it finishes its synchronization, please refer to this PIVX Freshdesk guide in order to confirm that you are on the right chain and you have not forked by mistake
- For Masternode users – please make sure that you have updated both the controller and masternode wallet and restart your masternode