Announcing Verus v1.2.3-5 - MANDATORY UPDATE FOR MAINNET, HIGHLY RECOMMENDED FOR TESTNET TO ADDRESS A CROSS-CHAIN TRAFFIC BLOCKAGE BETWEEN Verus AND vARRR BLOCKCHAINS, AND TO PREVENT ANY SIMILAR BLOCKAGE IN THE FUTURE ON ANY CHAIN, THIS VERSION IS MANDATORY TO STAY CONNECTED TO MAINNET CHAINS AND RECOMMENDED FOR TESTNET.

PLEASE UPGRADE BEFORE: VERUS MAINNET BLOCK 3143920 - EXPECTED AT ~17:00 UTC ON MONDAY, JULY 22ND

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

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

It is possible, if the community decides, to change the activation time to either earlier or later via oracle notification. If the community does decide to change the activation, for example after Tuesday’s meeting, it will be announced here with the most possible notice. We hope and believe this target activation should be acceptable notice and also timely enough for all users.

As long as people do not change the default notification oracle for their Verus nodes, nodes older than v1.2.3-5 running on the Verus blockchain will pause and wait for upgrade just before the activation block. If you do not have time to update in the next week or before activation, and this happens to you, you should be able to simply close, upgrade, and continue when you are able.

Verus v1.2.3-5 contains a fix in the verification code for advanced cross-chain proofs that was falsely rejecting valid cross-chain proofs between Verus and PBaaS chains, only in the case of mainnet.

There are no other protocol or functional changes in v1.2.3-5.