Re: [ANN] Verus (VRSC) - zk-SNARK privacy, CPU-mining, 50/50 POW/POS, fair launch
ANNOUNCING HIGHLY RECOMMENDED NON-MANDATORY, CRITICAL FOR NOTARIES AND POOLS, v0.7.4
IT’S TESTNET RESET TIME
!
Version v0.7.4 can improve a mainnet node’s synchronization and this version also upgrades and resets the Verus testnet, preparing it for the testnet launch of the Ethereum/Rinkeby bridge and bringing Verus PBaaS multi-chain, multi-currency, Verus Vault ID timelocking, Verus MEV-resistant DeFi, and the Ethereum bridge much closer to a mainnet ready state.
This release fixes all known functionality issues reported from the previous testnet including some related to currency and blockchain launches, as well as being incorrectly able to reduce the timelock period on a Verus Vault locked ID. It also includes the ability to export an ID from one chain to another, using the “exportid”:true parameter in sendcurrency, enabling cross-chain use of VerusIDs. With this release, we will be resetting the Verus testnet. To use the new testnet, you must make sure to delete the vrsctest and .verustest/pbaas or VerusTest\pbaas folders beforehand.
While the new testnet is fully prepared and ready to launch vETH as the Ethereum gateway, which will be directly connected to the Rinkeby testnet, there is still work on the Ethereum side to complete. We do not have an exact day that we expect to launch the gateway on the new testnet. We have confirmed the bridge connection and transaction transfers between VerusTest and Rinkeby, and we do not expect the bridge to be much longer until we can launch it on this testnet.
In addition to being prepared for the Ethereum bridge launch, this release adds some new testnet capabilities, including the ability to send to IDs cross chain and export IDs from chain to chain using the “exportid”:true parameter with sendcurrency. IDs only need to be exported once and can then be used and managed directly as a forked ID on the destination chain.
Thanks to all who have been using the testnet and reporting issues. Although the testing on this release took a bit longer than usual, we need to make sure that we release the best quality possible. I want to also thank the dedicated community members who participated in release testing, including the new people who joined this time around. As always, this is a community project with community contributors in everything from design to development to testing, website, marketing, and literally everything else. All of us who contribute are community members who mined, staked, bought, or earned coins from contribution like anyone else could. If you would like things to go faster, we encourage you to contribute where you can on things that are needed to get to release and we will leverage that help to go faster together.
CLI Release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.7.4
GUI Release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.7.4
IT’S TESTNET RESET TIME
!Version v0.7.4 can improve a mainnet node’s synchronization and this version also upgrades and resets the Verus testnet, preparing it for the testnet launch of the Ethereum/Rinkeby bridge and bringing Verus PBaaS multi-chain, multi-currency, Verus Vault ID timelocking, Verus MEV-resistant DeFi, and the Ethereum bridge much closer to a mainnet ready state.
This release fixes all known functionality issues reported from the previous testnet including some related to currency and blockchain launches, as well as being incorrectly able to reduce the timelock period on a Verus Vault locked ID. It also includes the ability to export an ID from one chain to another, using the “exportid”:true parameter in sendcurrency, enabling cross-chain use of VerusIDs. With this release, we will be resetting the Verus testnet. To use the new testnet, you must make sure to delete the vrsctest and .verustest/pbaas or VerusTest\pbaas folders beforehand.
While the new testnet is fully prepared and ready to launch vETH as the Ethereum gateway, which will be directly connected to the Rinkeby testnet, there is still work on the Ethereum side to complete. We do not have an exact day that we expect to launch the gateway on the new testnet. We have confirmed the bridge connection and transaction transfers between VerusTest and Rinkeby, and we do not expect the bridge to be much longer until we can launch it on this testnet.
In addition to being prepared for the Ethereum bridge launch, this release adds some new testnet capabilities, including the ability to send to IDs cross chain and export IDs from chain to chain using the “exportid”:true parameter with sendcurrency. IDs only need to be exported once and can then be used and managed directly as a forked ID on the destination chain.
Thanks to all who have been using the testnet and reporting issues. Although the testing on this release took a bit longer than usual, we need to make sure that we release the best quality possible. I want to also thank the dedicated community members who participated in release testing, including the new people who joined this time around. As always, this is a community project with community contributors in everything from design to development to testing, website, marketing, and literally everything else. All of us who contribute are community members who mined, staked, bought, or earned coins from contribution like anyone else could. If you would like things to go faster, we encourage you to contribute where you can on things that are needed to get to release and we will leverage that help to go faster together.
CLI Release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.7.4
GUI Release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.7.4