Announcing Verus v1.2.2-4 - MANDATORY UPDATE FOR vARRR MAINNET SUPPORT BEFORE vARRR BLOCK 67000 (in approximately 1 month) OR EARLIER IF DECIDED BY THE vARRR COMMUNITY. NEW PBaaS CHAINS SHOULD LAUNCH USING v1.2.2-4
MANDATORY UPDATE FOR CONTINUED VERUS TESTNET USAGE
CRITICAL UPDATE FOR VERUS MINING AND STAKING NODES
A small number of recently exported VerusIDs from Verus to vARRR exposed an issue that is not a security issue but has a potential unintended consequence for some users. Due to the way that VerusID locks and unlocks work, VerusIDs that have been locked, then unlocked, then exported to vARRR from Verus may end up locked on vARRR until a block height very far in the future that is the block where it actually unlocked on Verus. This happened to 3 IDs that were exported.
v1.2.2-4 will check in the sendcurrency command when a VerusID is exported to another chain if the timelock is set as an absolute timelock (specific to chain), or if the timelock is non-zero on an unlocked ID. If so, sendcurrency will throw an error along with a specific command needed to zero the value before exporting the ID.
At block 67000 on vARRR, v1.2.2-4 and all PBaaS chains will begin clearing this condition as part of importing an ID. After that time, someone in the community may make a pull request to remove the warning and failure on sendcurrency, which will no longer have a potential unintended consequence.
v1.2.2-4 Fixes an issue with Verus Desktop on Windows, which could sometimes result in the Verus daemon seeming to be closed when it was not. We believe this may have resulted in the need for some Windows users to bootstrap, even when Windows Update hadn’t directly rebooted their system.
v1.2.2-4 Enables adding VRSC as a vARRR currency or vARRR as a Verus currency in Verus Desktop and has UI improvements for defi functions
v1.2.2-4 Fixes a testnet-only issue that was preventing proper processing of CUR and REX currencies on testnet. The “Disable DeFi” oracle has been activated on testnet during this update, and when it is deactivated, v1.2.2-3 or lower will no longer be compatible with testnet. Please upgrade as soon as possible to use testnet. We expect to remove the disable notification sometime tomorrow.