Announcing Verus v1.2.4-2 - CRITICAL UPDATE TO PREVENT POTENTIAL PBaaS, CROSS-CHAIN OR FORK ISSUES UPDATE TO v1.2.4-2 OR GREATER IS RECOMMENDED AS SOON AS POSSIBLE TO PREVENT THE POSSIBILITY OF YOUR NODE FALLING OUT OF SYNC WITH THE MAIN CHAIN OR DELAYS ON CROSS-CHAIN NOTARIZATION FOR PBaaS CHAINS AFTER A REORG

CLI RELEASE: https://github.com/VerusCoin/VerusCoin/releases/tag/v1.2.4-2
GUI RELEASE: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v1.2.4-2

GUI TESTNET RELEASE: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v1.2.4-2-testnet

v1.2.4-2 Addresses an issue that occurred on the vARRR chain with overly aggressive memory caching of blockchain information that has the potential to cause a PBaaS chain node to fall out of sync in the case of a reorg. It also fixes another issue that can sometimes delay the resolution of cross-chain notarizations if a fork on a PBaaS chain forces a cross-chain challenge competition. The vARRR fork has been resolved.

The oracle notification to disable cross-chain functionality has been removed, resuming cross-chain transactions. Thanks to those that helped provide information and that took timely action to update. If you wound up on the vARRR fork, a resync is the most straightforward and reliable way to fix your node. In addition, v1.2.4-2 adds checking and will throw errors if the cli command sendrawtransaction is used and the transaction being sent is recognized as having an absurdly high fee payment.

As there are transactions you could make where this check might still allow an excessively high fee to be sent, this is intended to help prevent simple errors on typical send types of transactions, such as forgetting a change output. Even after this update, please always double check that your transactions have appropriate change outputs before using sendrawtransaction. v1.2.4-2 HAS NO PROTOCOL CHANGES