v5.3.1

PIVX Core version v5.3.1 is now available from: https://github.com/pivx-project/pivx/releases

This is an important release for stakers and Masternodes: including several tier two synchronization, GUI and build system bug fixes.
We recommend everyone to update your node/wallet.

Please report bugs using the issue tracker at github: https://github.com/pivx-project/pivx/issues

How to Upgrade

If you are running an older version, shut it down. Wait until it has completely shut down, then run the installer (on Windows) or just copy over /Applications/PIVX-Qt (on Mac) or pivxd/pivx-qt (on Linux).

Notable Changes

GUI

• Duplicate transaction records bug fixed.
• Not visible shield and/or cold staking contacts addresses list bug fixed

Tier Two Network

• Not advancing (stalled) tier two synchronization bug fixed.
• Spork signer not persisting new spork value to DB bug fixed.

Build system

• "dirty" release build version name bug fixed.

5.3.1 Change log

GUI

• #2530 [GUI][BUG] remove duplicated coll. confirmation check in MNModel::data (random-zebra)
• #2491 [GUI] Translation cleanup (Fuzzbawls)
• #2551 [BUG][GUI] Fix random double/triple transaction record issue (random-zebra)
• #2557 [Trivial] Update labelSubtitleAddress text in send widget ui (random-zebra)
• #2555 [GUI] Fix not visible contacts list for shield/CS addrs (furszy)

Consensus

• #2562 [Consensus] Add checkpoints before v5.3.1 release (random-zebra)

Tier Two Network

• #2553 [BUG] Spork signer doesn't persist new spork value to DB (random-zebra)
• #2559 [BUG][TierTwo] Clear fulfilled requests when mnsync fails (random-zebra)
• #2560 [Bug][TierTwo] Mark peer sync request msg fulfilled only if the broadcast was performed (furszy)

Build system

• #2525 [Build] Get rid of CLIENT_DATE (furszy)
• #2541 [Gitian][Bug] Ignore changes to relic_conf.h.in (Fuzzbawls)
• #2546 [Snap] Fix nightly build's genbuild.sh patch (Fuzzbawls)

RPC

• #2540 [RPC][Doc] Fix RPC/cli example in setautocombinethreshold help (random-zebra)

Credits

Thanks to everyone who directly contributed to this release:

• furszy
• Fuzzbawls
• random-zebra
• W. J. van der Laan

As well as everyone that helped translating on Transifex, the QA team during Testing and the node hosts supporting our Testnet.

v5.3.0

PIVX Core version v5.3.0 is now available from: https://github.com/pivx-project/pivx/releases

Mandatory Update

PIVX Core v5.3.0 is a mandatory update for all users. This release contains new consensus rules and improvements that are not backwards compatible with older versions. Users will need to update their clients before enforcement of this update goes into effect.

Update enforcement is currently scheduled to go into effect at the following time:

Mainnet: block 3,014,000. ~10th September.

Masternodes will need to be restarted once both the masternode daemon and the controller wallet have been upgraded.
If you are running a Masternode over Tor, please read the "How To Upgrade" section.

Note: In preparation for the enforcement, upgraded peers will start rejecting non-upgraded peers few hours before the enforcement block height, we recommend everyone to be updated at max a day before the final time.

Please report bugs using the issue tracker at github: https://github.com/pivx-project/pivx/issues

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).

Important note for Masternodes running over Tor (v2 onion address):
Before starting the node, copy the content of the onion_private_key file, located inside the data directory into a new onion_v3_private_key file inside the same directory.
On linux: cp -f onion_private_key onion_v3_private_key.
If the onion_v3_private_key file already exist, replace the content with the content of the onion_private_key file.

This will allow you to bypass the v2 onion address deprecation and continue running the MN over Tor for now.
Be aware that the Tor network is completely removing v2 onion addresses support starting from Oct 15th (see "P2P and network changes" section).
After the v5.3 network upgrade enforcement, the MN will need to be migrated to run on a Tor v3 onion address (Update window Sept 15th - Oct 15th).
If it's not done on time, the node will drop off the network.

Sapling Parameters

In order to run, as all versions after 5.0.0, PIVX Core requires two files, sapling-output.params and sapling-spend.params (with total size ~50 MB), to be saved in a specific location.

For the following packages, no action is required by the user:

• macOS release dmg binaries will use the params that are bundled into the .app bundle.
• Windows installer .exe will automatically copy the files in the proper location.
• Linux PPA/Snap installs will automatically copy the files in the proper location.

For the other packages, the user must save the param files in the proper location:

• macOS/Linux tar.gz tarballs include a bash script (install-params.sh) to copy the parameters in the appropriate location.
• Windows .zip users need to manually copy the files from the share/pivx folder to the %APPDATA%\PIVXParams directory.
• self compilers can run the script from the repository sources (params/install-params.sh), or copy the files directly from the params subdirectory.

Compatibility

PIVX Core is extensively tested on multiple operating systems using the Linux kernel, macOS 10.12+, 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.

From PIVX Core v5.3 onwards, macOS versions earlier than 10.12 are no longer supported.

PIVX Core should also work on most other Unix-like systems but is not frequently tested on them.

The node's known peers are persisted to disk in a file called peers.dat. The format of this file has been changed in a backwards-incompatible way in order to accommodate the storage of Tor v3 and other BIP155 addresses. This means that if the file is modified by v5.3 or newer then older versions will not be able to read it. Those old versions, in the event of a downgrade, will log an error message "Incorrect keysize in addrman deserialization" and will continue normal operation as if the file was missing, creating a new empty one. (PR #2411)

Notable Changes

GUI changes

The launch-on-startup option is no longer available on macOS

Subtract Fee From Amount Control

A new checkbox in the send widget allows the user to deduct the fee from the transaction recipient amount.
The most common use-case is when sending the whole balance, or a selection of UTXOs, without getting any change back.
If the transaction has multiple recipients, each recipient can be checked with a toggleable button in the context menu, and the fee will be split, and subtracted evenly from the outputs selected (PR #2347).

Settings

A new checkbox added to the wallet settings to enable or disable automatic port mapping with NAT-PMP.
If both UPnP and NAT-PMP are enabled, a successful allocation from UPnP prevails over one from NAT-PMP.

Note: Successful automatic port mapping requires a router that supports either UPnP or NAT-PMP (PR #2338).

RPC-Console

The GUI RPC-Console now accepts "parenthesized syntax", nested commands, and simple queries (PR #2282.
A new command help-console (available only on the GUI console) documents how to use it:

This console accepts RPC commands using the standard syntax.
    example:    getblockhash 0

This console can also accept RPC commands using parenthesized syntax.
    example:    getblockhash(0)

Commands may be nested when specified with the parenthesized syntax.
    example:    getblock(getblockhash(0) true)

A space or a comma can be used to delimit arguments for either syntax.
    example:    getblockhash 0
                getblockhash,0

Named results can be queried with a non-quoted key string in brackets.
    example:    getblock(getblockhash(0) true)[tx]

Results without keys can be queried using an integer in brackets.
    example:    getblock(getblockhash(0),true)[tx][0]

P2P and network changes

Tor v3 hidden services support - addrv2 message (BIP155)

This release adds support for Tor version 3 hidden services, and rumoring them over the network to other peers using BIP155. Version 2 hidden services are still supported by PIVX Core, but the Tor network has started deprecating them, and will remove support soon. (PR #2411)

The Tor onion service that is automatically created by setting the -listenonion configuration parameter will now be created as a Tor v3 service instead of Tor v2. The private key that was used for Tor v2 (if any) will be left untouched in the onion_private_key file in the data directory (see -datadir) and can be removed if not needed. PIVX Core will no longer attempt to read it. The private key for the Tor v3 service will be saved in a file named onion_v3_private_key. To use the deprecated Tor v2 service (not recommended), then onion_private_key can be copied over onion_v3_private_key, e.g.
cp -f onion_private_key onion_v3_private_key.

Removal of reject network messages from PIVX Core (BIP61)

Nodes on the network can not generally be trusted to send valid ("reject") messages, so this should only ever be used when connected to a trusted node.
Please use the recommended alternatives if you rely on this feature:

• Testing or debugging of implementations of the PIVX P2P network protocol should be done by inspecting the log messages that are produced by a recent version of PIVX Core. PIVX Core logs debug messages (-debug=<category>) to a stream (-printtoconsole) or to a file (-debuglogfile=<debug.log>).

• Testing the validity of a block can be achieved by specific RPCs (submitblock)

• Testing the validity of a transaction can be achieved by specific RPCs (sendrawtransaction)

• Wallets should not use the absence of "reject" messages to indicate a transaction has propagated the network, nor should wallets use "reject" messages to set transaction fees. Wallets should rather use fee estimation to determine transaction fees. Thus, they could wait until the transaction has confirmed (taking into account the fee target they set (compare the RPC estimatesmartfee) or listen for the transaction announcement by other network peers to check for propagation.

Multi-wallet support

PIVX Core now supports loading multiple, separate wallets (PR #2337) with individual balances, keys and received transactions.

Multi-wallet is enabled by using more than one -wallet argument when starting PIVX client, either on the command line or in the pivx.conf config file.

In pivx-qt, only the first wallet will be displayed and accessible for creating and signing transactions. GUI selectable multiple wallets will be supported in a future version. However, even in 5.3, other loaded wallets will remain synchronized to the node's current tip in the background.

PIVX Core 5.3.0 contains the following changes to the RPC interface and pivx-cli for multi-wallet:

• When running PIVX Co...

v5.3.0rc1

First release candidate for the upcoming v5.3.0 release.

Full, finalized release notes will be available with the final release version.

v5.2.0.1

PIVX Core version v5.2.0.1 is now available from: https://github.com/pivx-project/pivx/releases.

This is a new optional patch version release, recommended for Masternodes.

You can find the complete upgrade information in the v5.2.0 release. Including the shortly coming update enforcement timeline.

v5.2.1.0 Change log

• #2402 Fix MN activation when the node received the mnb before initialize the MN (furszy)

v5.2.0

PIVX Core version v5.2.0 is now available from: https://github.com/pivx-project/pivx/releases

This is a new major version release, including various bug fixes and visual improvements.

Please report bugs using the issue tracker at github: https://github.com/pivx-project/pivx/issues

Mandatory Update

PIVX Core v5.2.0 is a mandatory update for all users. This release contains a protocol upgrade (to 70922), new consensus rules and improvements that are not backwards compatible with older versions. Users will need to update their clients before enforcement of this update goes into effect.

Update enforcement is currently scheduled to go into effect at the following block height:

Mainnet: 2,927,000

Masternodes will need to be restarted once both the masternode daemon and the controller wallet have been upgraded.

Note: In preparation for the enforcement, upgraded peers will start rejecting non-upgraded peers few hours before the enforcement block height, we recommend everyone to be updated at max a day before the final time.

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).

Sapling Parameters

In order to run, PIVX Core now requires two files, sapling-output.params and sapling-spend.params (with total size ~50 MB), to be saved in a specific location.

For the following packages, no action is required by the user:

• macOS release dmg binaries will use the params that are bundled into the .app bundle.
• Windows installer .exe will automatically copy the files in the proper location.
• Linux PPA/Snap installs will automatically copy the files in the proper location.

For the other packages, the user must save the param files in the proper location, before being able to run PIVX v5.2.0:

• macOS/Linux tar.gz tarballs include a bash script (install-params.sh) to copy the parameters in the appropriate location.
• Windows .zip users need to manually copy the files from the share/pivx folder to the %APPDATA%\PIVXParams directory.
• self compilers can run the script from the repository sources (params/install-params.sh), or copy the files directly from the params subdirectory.

Compatibility

PIVX Core is extensively tested on multiple operating systems using the Linux kernel, macOS 10.12+, and Windows 7 and later. Should also work on most other Unix-like systems but is not frequently tested on them.

v5.2.0 Change log

GUI

• #2259 fix QT 5.15 currentIndexChanged(QString) obsolete method call (furszy)
• #2260 Generate FAQ answer content programmatically (Fuzzbawls)
• #2305 Show the window when double clicking the taskbar icon (furszy)
• #2353 [GUI] Add search option to My Addresses list in receive widget (PicklesRcool)
• #2374 [Backport] Fix memory leaks in qt/guiutil.cpp (random-zebra)
• #2379 [BugFix] fix "not updating GUI balance" race condition (furszy)
• #2377 [BugFix][GUI] Fix minimize and close bugs (furszy)
• #2401 [GUI] BugFix, disappearing text in comboboxes (furszy)

Consensus

• #2258 [Script] Fix "split P2CS" vulnerability (random-zebra)
• #2428 [Consensus] Introduce 5.2 nuparams and use them to guard new P2CS rules (random-zebra)
• #2431 [Consensus] Bump active protocol version to 70922 (random-zebra)
• #2435 [Backport] Bump default block version to 10 (no enforcement) (random-zebra)
• #2441 [Consensus] v5.2 upgrade enforcement height (furszy).

Tier Two Network (Masternodes / Budget)

• #2395 [budget] partially fixing a race condition that could cause a good peer to be banned (furszy)
• #2437 [Backport] Add tiertwo_governance_reorg functional test (random-zebra)
• ##2440 Align budget payee validity to highest voted budget check. (furszy)

Build system:

• #2350 [build] depends macOS: point --sysroot to SDK (furszy)
• #2384 [depends] update Qt 5.9 source url (furszy)
• #2413 [CI] Remove Ubuntu 16.04 usage from GA workflow (furszy)
• #2433 [Build] Bump gitian descriptor version to 5.2 (fuzzbawls)

Wallet

• #2450 [wallet] fix segfault for P2CS inputs in CreateTransaction (furszy)

Miscellaneous

• #2348 [Cleanup] Cleaning unused gitian fingerprints (furszy)

Credits

Thanks to everyone who directly contributed to this release:

• Dan Raviv
• furszy
• Fuzzbawls
• ken2812221
• Kittywhiskers Van Gogh
• random-zebra
• PicklesRcool
• Sjors Provoost
• Volodia

As well as everyone that helped translating on Transifex, the QA team during Testing and the Node hosts supporting our Testnet.

v5.2.0rc1

First release candidate for the upcoming v5.2.0 release.

Full, finalized release notes will be available with the final release version.

v5.1.0

PIVX Core version v5.1.0 is now available from: https://github.com/pivx-project/pivx/releases

This is a new major version release, including various bug fixes and performance improvements, as well as updated translations.

Please report bugs using the issue tracker at github: https://github.com/pivx-project/pivx/issues

Recommended Update

This version is an optional, but recommended, update for all users and services.

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).

Sapling Parameters

In order to run, PIVX Core now requires two files, sapling-output.params and sapling-spend.params (with total size ~50 MB), to be saved in a specific location.

For the following packages, no action is required by the user:

• macOS release dmg binaries will use the params that are bundled into the .app bundle.
• Windows installer .exe will automatically copy the files in the proper location.
• Linux PPA/Snap installs will automatically copy the files in the proper location.

For the other packages, the user must save the param files in the proper location, before being able to run PIVX v5.0.0:

• macOS/Linux tar.gz tarballs include a bash script (install-params.sh) to copy the parameters in the appropriate location.
• Windows .zip users need to manually copy the files from the share/pivx folder to the %APPDATA%\PIVXParams directory.
• self compilers can run the script from the repository sources (params/install-params.sh), or copy the files directly from the params subdirectory.

Compatibility

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.

Notable Changes

• Faster blockchain synchronization and reindex.
• Faster GUI and overall responsiveness.
• Improved chain-state corruption recovery.
• Improved core performance and stability.
• A good amount of bugs fixed.

Disable PoW mining RPC Commands

A new configure flag has been introduced to allow more granular control over weather or not the PoW mining RPC commands are compiled into the wallet. By default they are not. This behavior can be overridden by passing --enable-mining-rpc to the configure script.

v5.1.0 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.

Block and transaction handling

• #2150 Revamping block validation interface interaction with wallet (furszy)
• #2179 [Backport] Make CTransaction actually immutable (furszy)
• #2192 Support for validation interface signals in background thread (furszy)
• #2203 Call wallet/validation notify callbacks in scheduler thread (without cs_main) (furszy)
• #2213 Remove dead zc checks from ATMP (furszy)
• #2226 [Refactoring] Prune invalid UTXOs from the coins cache (random-zebra)
• #2295 [Net_Processing] Cleaner block processing workflow (furszy)
• #2290 [Test] Fix concurrency issues in ActivateBestChain + optimization (furszy)
• #2284 Removing unneeded block serialization and signal from ABC (furszy)
• #2243 [Protocol] Block version 9 (random-zebra)

P2P protocol and network code

• #2090 Fail instead of truncate command name in CMessageHeader (random-zebra)
• #2118 Inv, mempool and validation improvements (furszy)
• #2172 Improve and document SOCKS code (random-zebra)

Wallet

• #2126 [Backport] Wallet database handling abstractions/simplifications (furszy)
• #2044 Making CWalletTx store TransactionRef (furszy)
• #2117 [BUG][Wallet] Restore AddressBook when marking used keys in the keypool (random-zebra)
• #2197 Close DB on error (Fuzzbawls)
• #2195 Solve an incorrect MakeTransactionRef usage for ATMP call inside the wallet and unit tests (furszy)
• #2201 CTransactionRef migration + CWalletTx/CMerkleTx refactor (furszy)
• #2218 Guarding wallet access from init and print error for unknown MN collaterals (furszy)
• #2232 Berkeley DB v6 compatibility fix (random-zebra)
• #2225 Rescan chain for wallet transactions process re-written (furszy)
• #2209 Killing wallet and GUI cs_main locks (furszy)

RPC and other APIs

• #2141 Fix argument parsing and example for getbalance (Fuzzbawls)
• #2147 fix getbalance transparent watch-only amount (furszy)
• #2154 validateaddress remove duplicate return address value (furszy)
• #2157 mnbudgetvote generalized, duplicated code cleaned (furszy)
• #2177 [BUG] Fix getblockindexstats-getfeeinfo with shield txes (random-zebra)
• #2283 getwalletinfo: Add last_processed_block return value (furszy)

GUI

• #2173 Prevent invalid dashboard txs list filter value loaded from settings (furszy)
• #2178 [BUG][GUI] Fix CWalletTx* casts to CTransaction* (random-zebra)
• #2161 send widget, hide contacts menu when clear event is triggered (furszy)
• #2174 Use wchar_t API explicitly on Windows (Fuzzbawls)
• #2219 FAQ remove freshdesk and SwiftX mention (furszy)
• #2211 Reduce whitespace around qr code fixes #1562 (dnchk)
• #2228 Fixing few shutdown problems (furszy)
• #2229 Transaction filter, minimize model data request + cleanup (furszy)
• #2244 Pre-5.1 make translate (Fuzzbawls)
• #2249 Make box of PIVX Send address return to purple when it's empty (PicklesRcool)
• #2247 Fix double fade-in Topbar Available click animation. Issue 2216 (PicklesRcool)
• #2237 Set fee to highest possible if input is too big (dnchk)
• #2215 Automatically set the lowest possible Custom Fee when user provided fee is too low (MishaPozdnikin)
• #2321 [GUI] Fix Cold Staking address list (Fuzzbawls)
• #2327 [BUG] Fix crash when sending shield notes from the GUI with coin control (random-zebra)

Tests and QA

• #2144 [BUG] Fix random range in feature_blockhashcache (random-zebra)
• #2146 Add checkblock benchmark test (random-zebra)
• #2148 [Core] Prevector Optimizations 2 (random-zebra)
• #2165 Check for diversified address equal to default one in zkeys_test (random-zebra)
• #2132 Add more cases to sighash_tests for malleated txes (random-zebra)
• #2153 Don't create dust outputs in small_txpuzzle_randfee (random-zebra)
• #2169 Introduce TestChainSetup fixture, pre-creating a N-blocks chain (random-zebra)
• #2190 Fix and enable zmq functional test in the test suite (furszy)
• #2176 Double spend inputs and notes unit tests coverage (furszy)
• #2194 [Backport] Disable the mempool P2P command when bloom filters disabled (furszy)
• #2189 [Bug][Refactoring] Miscellaneous fixes (random-zebra)
• #2206 script standard tests back ported (furszy)
• #2214 Fix various things -fsanitize complains about (random-zebra)
• #2221 updating rpc_invalidateblock.py to latest upstream (furszy)
• #2233 fix miner_tests block generation race condition (furszy)
• #2235 address.py: fix invalid keyhash_to_p2pkh() (furszy)
• #2254 sync_blocks and sync_mempool improvements (random-zebra)

Build system

• #2152 [CMake] Fix CMake builds on macOS Big Sur (Fuzzbawls)
• #2105 Don't compile PoW mining RPC commands by default (Fuzzbawls)
• #2198 [GA] Enable CMake macOS Build (Fuzzbawls)
• #2227 fixing gitian build fail with checksum mismatch (furszy)
• #2230 [GA] Dont run the feature_dbcrash test in GA (Fuzzbawls)

Tier Two Network (Masternodes / Budget)

• #2143 [BUG] Fix deadlock in GetNextMasternodeInQueueForPayment (random-zebra)
• #2170 Better pivx.conf Masternode data error notification (furszy)
• #2186 Improving masternode check inputs and add process (furszy)

Miscellaneous

• #2082 Generic event handler interface (furszy)
• #2155 [Miner] Rewrite miner code with proper encapsulation + test coverage (furszy)
• #2162 [Refactoring] Avoid dereference-of-casted-pointer (random-zebra)
• #2166 [BUG] Flush the chainstate after pruning invalid entries (random-zebra)
• #2167 [Logs] Add new "sporks" debug logging category (Fuzzbawls)
• #2185 [Backport] Use static_cast instead of C-style casts for non-fundamental types (furszy)
• #2188 [Core] More efficient rolling Bloom filter (random-zebra)
• #2191 [BugFix] Shutdown, stop threadGroup before dump data to disk (furszy)
• #2207 Use non-atomic flushing with block replay (furszy)
• #2205 logging: Remove unused return value from logprintstr (random-zebra)
• #2223 [BUG] Fix some chainstate-init-order bugs (random-zebra)
• #2224 Removing TX_ZEROCOINMINT and ScriptPubKeyToJSON (furszy)

Documentation

• #2187 WSL Depends builds need --disable-online-rust (Fuzzbawls)
• #2231 More Descriptive Budget RPCs (Liquid369)
• #2262 add reduce-memory.md (furszy)

Refactoring

• #2089 Fix some -Wdeprecated-copy warnings (random-zebra)
• #2092 [Cor...

v5.1.0rc3

Second release candidate for the upcoming v5.1.0 release.

Full, finalized release notes will be available with the final release version.

v5.1.0rc2

First release candidate for the upcoming v5.1.0 release.

Full, finalized release notes will be available with the final release version.

v5.0.1

PIVX Core version v5.0.1 is now available from: https://github.com/pivx-project/pivx/releases
Please report bugs using the issue tracker at github: https://github.com/pivx-project/pivx/issues

Mandatory Update

This is an emergency update.
A vulnerability with the budgeting system was discovered and has been fixed (PR 2137).
This release also contains a protocol upgrade (to 70921).
Users will need to update their clients before enforcement of this update goes into effect.
Update enforcement is currently scheduled to go into effect at the same block height that was scheduled for v5.0.0: 2700500

Masternodes will need to be restarted once both the masternode daemon and the controller wallet have been upgraded.

Important Note

No user's funds are at risk, but users facing a checkpoint error after upgrade need to resync the chain.