Announcing v0.9.9-4 - RECOMMENDED FOR MAINNET, MANDATORY UPDATE FOR RELIABLE TESTNET OPERATION Mainnet Changes - low level stakeguard improvements, no functional changes What’s New for TestNet
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.9-4
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.9-4
This release fixes an issue that was causing testnet users to experience sync issues on chains that had more than one oracle upgrade for the same capability activated. There are no other significant changes.
Topic: [ANN] Verus (VRSC) - zk-SNARK privacy, CPU-mining, 50/50 POW/POS, fair launch - page 4. (Read 48711 times)
March 27, 2023, 08:14:01 AM
March 23, 2023, 06:20:16 PM
Announcing v0.9.9-3 - FULLY OPTIONAL UPDATE FOR MAINNET, MANDATORY UPDATE FOR CONTINUED TESTNET OPERATION Mainnet Changes - no protocol changes V0.9.9-3 introduces the prunespentwallettransactions CLI command and RPC API, providing a method for holders on testnet or mainnet of very large wallets to prune older spent transactions, which can improve performance for wallets that may be slowing down due to size. There are no mainnet protocol changes in v0.9.9-3 over the prior release.
What’s New for TestNet This release includes an activation that allows a major upgrade to the testnet Ethereum bridge contracts that is both not expected to be needed again on testnet and not ever needed on mainnet with the new contract upgrade model. This upgrade should clear all known issues on the bridge to Goerli, meaning any remaining bridge transactions will be delivered, and the ETH bridge should then be fully functional. The Path for PBaaS to Mainnet This testnet has actually been through a lot already, more than we expected before mainnet, and this last experience, along with its full restoration of cross-chain and all function has been very useful and was the impetus for the Verus Oracle Notification technology. In the process of getting here, we implemented the necessary changes and fixes to get everything back on track, but we also have remnants of these events in the daemon, and on the final protocol, these are there to enable compatibility with the history of testnet, not because we need these upgrades on mainnet PBaaS. It gave us experience, increased confidence, and pushed us to develop a fast, decentralized network response capability. At the same time, it would be best for our code base, both on the Verus side and in the ETH contracts if that testnet history is removed from the code before mainnet activation. Doing so would make the next upgrade incompatible with today’s testnet and its earlier history. As a result, we have decided that we will create one final testnet, but this time, we would do it a little differently than in the past. We will extend the pre-PBaaS upgrade on the existing testnet to a future date via the oracles. If you have started a chain and control the default oracle on any chain, please check the pbaas-development channel for instructions on setting your oracle to extend the upgrade. We will leave the current testnet running and fully functional, as we prepare the next release, which we expect to be ready for a mainnet PBaaS activation. We will effectively abandon this testnet and leave it running long enough to overlap with the next and final testnet instance before PBaaS release. You should be able to actually send currencies over from the first testnet to the second via Ethereum’s Goerli testnet, even map some VRSCTEST-CLASSIC or something else through the bridge, but we do not intend to update that daemon again, or continue to run nodes or notaries on the old test network for more than a couple weeks after the new testnet goes live. Thanks for all your help and contributions, both already made and those to come for this historic upcoming release!
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.9-3
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.9-3
What’s New for TestNet This release includes an activation that allows a major upgrade to the testnet Ethereum bridge contracts that is both not expected to be needed again on testnet and not ever needed on mainnet with the new contract upgrade model. This upgrade should clear all known issues on the bridge to Goerli, meaning any remaining bridge transactions will be delivered, and the ETH bridge should then be fully functional. The Path for PBaaS to Mainnet This testnet has actually been through a lot already, more than we expected before mainnet, and this last experience, along with its full restoration of cross-chain and all function has been very useful and was the impetus for the Verus Oracle Notification technology. In the process of getting here, we implemented the necessary changes and fixes to get everything back on track, but we also have remnants of these events in the daemon, and on the final protocol, these are there to enable compatibility with the history of testnet, not because we need these upgrades on mainnet PBaaS. It gave us experience, increased confidence, and pushed us to develop a fast, decentralized network response capability. At the same time, it would be best for our code base, both on the Verus side and in the ETH contracts if that testnet history is removed from the code before mainnet activation. Doing so would make the next upgrade incompatible with today’s testnet and its earlier history. As a result, we have decided that we will create one final testnet, but this time, we would do it a little differently than in the past. We will extend the pre-PBaaS upgrade on the existing testnet to a future date via the oracles. If you have started a chain and control the default oracle on any chain, please check the pbaas-development channel for instructions on setting your oracle to extend the upgrade. We will leave the current testnet running and fully functional, as we prepare the next release, which we expect to be ready for a mainnet PBaaS activation. We will effectively abandon this testnet and leave it running long enough to overlap with the next and final testnet instance before PBaaS release. You should be able to actually send currencies over from the first testnet to the second via Ethereum’s Goerli testnet, even map some VRSCTEST-CLASSIC or something else through the bridge, but we do not intend to update that daemon again, or continue to run nodes or notaries on the old test network for more than a couple weeks after the new testnet goes live. Thanks for all your help and contributions, both already made and those to come for this historic upcoming release!
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.9-3
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.9-3
March 16, 2023, 06:18:59 AM
Announcing v0.9.9-2 - CRITICAL SECURITY UPDATE FOR MAINNET AND REQUIRED UPDATE TO RESUME SUCCESSFUL MERGE MINING NOTARIZATION ON TESTNET
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.9-2
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.9-2
Important Mainnet Security Updates v0.9.9-2 introduces new mitigation code for the Rab13s vulnerability, announced by Halbourne 3 days ago as a zero day vulnerability in over 280 blockchains, including Zcash and Verus, that could allow someone to attack and bring down specific nodes that they may target through exhausting the node’s resources.
The Verus fix adapts a fix implemented in Zcash that also does a better job of preserving privacy while gossiping transactions around the network by making it harder to track their node of origin via listening nodes. This release also includes an important update of the OpenSSL library, which Verus uses for encrypted node connections and addresses a buffer overflow vulnerability in that library.
What’s New for TestNet This release re-enables cross-chain notarization, and represents the completion of a great deal of learning from the first roll out of auto notarization. Basically, we encountered two issues:
1) There was a notarization bug in a significantly updated approach that caused notarizations to fork, effectively simulating a worst case, unmitigated attack on the notarization system. While that did not cause the system to fail per se, it resulted in the generation of many perceived, although not real, notarization forks on the network.
2) Due to our effort to err on the side of more evidence than we believed was sufficient with auto notarization, then optimize to reduce the proofs required, the protocol was simply taking too long and generating too large proofs to be reasonable, required, or what we need on mainnet in any real scenario.
As a result, we will take a few days to change some parameters in the auto notarization protocol that will both reduce the total and maximum amount of proof required, as well as provide a sufficient level of cryptographic proof, similar in strength to the current proof model with more efficient and selective proof choices. We don’t expect this important step to take long, and until then, we will leave testnet on the pre-PBaaS to mainnet preparatory state. The good news is that since we have the new Verus Notification Oracle technology, we can enable everyone running on the current testnet to remain connected as all cross-chain transactions to and from PBaaS chains will resume flowing.
We are still seeing an error in BridgeKeeper, but since this release includes a mainnet security update and addresses all other known issues on testnet, we’ll release this immediately and update Bridgekeeper as soon as possible. In order to merge mine PBaaS chains with Verus or the Ethereum bridge to Goerli going forward, you will need to update to v0.9.9-2, which everyone should run for mainnet anyhow.
Once you update, please feel free to resume merge mining all PBaaS chains and Verus. You will need to wait for the BridgeKeeper update to be able to merge mine and stake with Ethereum’s Goerli. Thanks for all your testing! We’ve learned a great deal from this upgrade, and although it may feel like a delay that we took the time to learn and address it in place on the public network before moving on, this learning and consequent hardening will ensure the mainnet release will be more hardened than ever. Next steps are to upgrade auto notarization to be resilient to anything like this level of buildup over weeks automatically and prepare the mainnet release. Join us in testing everything in the pbaas-development channel. Contribute as you learn and build, and let's all make history together!
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.9-2
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.9-2
Important Mainnet Security Updates v0.9.9-2 introduces new mitigation code for the Rab13s vulnerability, announced by Halbourne 3 days ago as a zero day vulnerability in over 280 blockchains, including Zcash and Verus, that could allow someone to attack and bring down specific nodes that they may target through exhausting the node’s resources.
The Verus fix adapts a fix implemented in Zcash that also does a better job of preserving privacy while gossiping transactions around the network by making it harder to track their node of origin via listening nodes. This release also includes an important update of the OpenSSL library, which Verus uses for encrypted node connections and addresses a buffer overflow vulnerability in that library.
What’s New for TestNet This release re-enables cross-chain notarization, and represents the completion of a great deal of learning from the first roll out of auto notarization. Basically, we encountered two issues:
1) There was a notarization bug in a significantly updated approach that caused notarizations to fork, effectively simulating a worst case, unmitigated attack on the notarization system. While that did not cause the system to fail per se, it resulted in the generation of many perceived, although not real, notarization forks on the network.
2) Due to our effort to err on the side of more evidence than we believed was sufficient with auto notarization, then optimize to reduce the proofs required, the protocol was simply taking too long and generating too large proofs to be reasonable, required, or what we need on mainnet in any real scenario.
As a result, we will take a few days to change some parameters in the auto notarization protocol that will both reduce the total and maximum amount of proof required, as well as provide a sufficient level of cryptographic proof, similar in strength to the current proof model with more efficient and selective proof choices. We don’t expect this important step to take long, and until then, we will leave testnet on the pre-PBaaS to mainnet preparatory state. The good news is that since we have the new Verus Notification Oracle technology, we can enable everyone running on the current testnet to remain connected as all cross-chain transactions to and from PBaaS chains will resume flowing.
We are still seeing an error in BridgeKeeper, but since this release includes a mainnet security update and addresses all other known issues on testnet, we’ll release this immediately and update Bridgekeeper as soon as possible. In order to merge mine PBaaS chains with Verus or the Ethereum bridge to Goerli going forward, you will need to update to v0.9.9-2, which everyone should run for mainnet anyhow.
Once you update, please feel free to resume merge mining all PBaaS chains and Verus. You will need to wait for the BridgeKeeper update to be able to merge mine and stake with Ethereum’s Goerli. Thanks for all your testing! We’ve learned a great deal from this upgrade, and although it may feel like a delay that we took the time to learn and address it in place on the public network before moving on, this learning and consequent hardening will ensure the mainnet release will be more hardened than ever. Next steps are to upgrade auto notarization to be resilient to anything like this level of buildup over weeks automatically and prepare the mainnet release. Join us in testing everything in the pbaas-development channel. Contribute as you learn and build, and let's all make history together!
March 10, 2023, 05:32:46 PM
Announcing v0.9.9 - PBaaS Mainnet Preparation Release, MANDATORY FOR MAINNET AND CONTINUED TESTNET USE
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.9
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.9
What’s New
There is so much new and important in v0.9.9, and we are so close to the mainnet PBaaS release that this is a hard announcement to keep to a digestible size. Key points:
Preparing for #LaunchPBaaS: v0.9.9 is MANDATORY, meaning that you will need to upgrade to this release ASAP to stay reliably connected to mainnet after the first preparatory PBaaS upgrade is triggered, both for testnet and mainnet. While the current deadline for being upgraded is in 1 week, it is a soft fork that we would like to activate as soon as possible, and if we can believe that we have more than 50% of the validating network updated earlier than 1 week, we will trigger the activation with our Oracle Notification Technology described in #2. (Mainnet + Testnet)
Enabling Seamless Decentralized Network Upgrades: This release includes a Verus invention of consensus-capable oracle notifications built into the core protocol, which enable dynamic coordinated consensus changes that can be triggered at a time decided after the actual release which enables them, all without any compromise on decentralization. The Verus Community may decide that we are ready to go earlier than one week on this upgrade and activate it, even before its scheduled time. The good news is that this first test upgrade will primarily affect testnet and prepare for the mainnet PBaaS upgrade, so it is a perfect test case for a mainnet test run before we #LaunchPBaaS. This release actually has the ability to upgrade mainnet to PBaaS, but we believe it is prudent to have at least some time on this new protocol on testnet before the v1.0 release, which will upgrade mainnet. If we make no additional changes to the protocol in this release, which we do not intend to do at this time, this version may be able to follow the v1.0 upgrade. If we determine that it cannot, the oracle upgrade technology will enable the daemon to recognize that it is not capable and request that the user upgrade to a newer version without requiring a bootstrap for the upgrade. (Mainnet + Testnet)
This upgrade fixes all known testnet issues with no reset: Using v0.9.9, you should be able to sync fully and resume all cross-chain operations on the Verus test network, if you were not able to perform cross-chain operations or sync to the network on the prior version. As mentioned, someone seems to have mined with an intermediate version along the way on testnet and made the network unavailable without a bootstrap on the older daemon. This version should fix that issue as well as any cross-chain difficulties. Auto-notarization will be enabled on testnet in sync when the testfork executes. Until then, all witnessed cross-chain operations should be able to resume, if they have had difficulty. (Testnet until the #LaunchPBaaS release)
Bridging Blockchain Networks Without Witnesses: v0.9.9 is the first release of any blockchain protocol anywhere that we know of which enables cryptographically provable, cross-chain bridging across Verus and all PBaaS and other connected blockchains in the network, either combined with or independent of the need for notary witnesses. With notary witnesses, cross-chain transactions complete faster, but they are also checked against cryptographic evidence, making it difficult to impossible for anyone, including notary witnesses to take any action, even colluding with validators that would go against the wishes of the most chain power. We have been referring to this new cross-chain consensus technology as “auto-notarization”, as that is what it actually is, but it would also be accurate to call it Proof of Proof of Power, as that is how it works. For purposes of ensuring everyone understands the state of the technology, it is fully functional and we have taken great care to ensure it is sufficiently secure, but we have not yet had the protocol proven to an academic standard. Because of that, while it provides a security fall-back against misbehaving notary witnesses and will be fully functional and we believe sufficiently secure without notary witnesses on release, we currently recommend toconsider the protocol unproven at this time and that any serious PBaaS chains be launched with operational notary witnesses until further notice.
Using “notarizationprotocol”:1, which is also the default, a chain launch can specify notary witnesses that will be used when they do their job. Even if they stop witnessing for any reason, the protocol will fail-over to auto-notarization, ensuring that cross-chain transactions still function as expected, even if just for people to move their assets to another blockchain, although significantly more slowly and based solely on cryptographic proof and challenge resolution between merge miners and stakers. This cross-chain proof and challenge protocol operates even when witnesses are also operating and if miners and stakers continue to prove a more powerful chain than the one witnesses represent, the most powerful chain can still be confirmed. (Testnet until the #LaunchPBaaS release) Expanding L1 VerusID APIs: This release provides a major enhancement to the identity content multimap support with two new APIs, getidentityhistory and getidentitycontent that provide real-time mempool access and also introduce self-sovereign delete operations to identity content that can be used by applications, making it easy for applications to index, organize, and aggregate an unlimited amount of user content referenced by an identity and made available to the application. This is the technology we used for oracle upgrade notifications, as all of this is available at L1, making it possible to imagine future protocols that can deal smoothly with diverse community opinions worldwide, but always respect the sovereignty and decisions of all members on the network. (Testnet until the #LaunchPBaaS release)
Introducing Restricted VerusID Staking for PBaaS Chains: This release enables the stretch goal of restricted ID staking as an option for launching PBaaS chains. This option means that on such a PBaaS chain, only funds controlled by IDs with a parent of that PBaaS chain may stake blocks on that chain. When combined with restricted forms of ID issuance, whether approval or referral required and/or referral rewards, this capability opens up an entire new area for public/private blockchains and applications, as well as government, voting security, corporate, or organizational use cases.(Testnet until the #LaunchPBaaS release)
v0.9.9 represents the culmination of years of vision and work from across the entire community, and everyone who has been involved and contributed at all in any area over the last 5 years helped us get here today. From my perspective, I believe this represents a bigger potential benefit to the world than all of my prior professional efforts combined.
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.9
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.9
What’s New
There is so much new and important in v0.9.9, and we are so close to the mainnet PBaaS release that this is a hard announcement to keep to a digestible size. Key points:
Preparing for #LaunchPBaaS: v0.9.9 is MANDATORY, meaning that you will need to upgrade to this release ASAP to stay reliably connected to mainnet after the first preparatory PBaaS upgrade is triggered, both for testnet and mainnet. While the current deadline for being upgraded is in 1 week, it is a soft fork that we would like to activate as soon as possible, and if we can believe that we have more than 50% of the validating network updated earlier than 1 week, we will trigger the activation with our Oracle Notification Technology described in #2. (Mainnet + Testnet)
Enabling Seamless Decentralized Network Upgrades: This release includes a Verus invention of consensus-capable oracle notifications built into the core protocol, which enable dynamic coordinated consensus changes that can be triggered at a time decided after the actual release which enables them, all without any compromise on decentralization. The Verus Community may decide that we are ready to go earlier than one week on this upgrade and activate it, even before its scheduled time. The good news is that this first test upgrade will primarily affect testnet and prepare for the mainnet PBaaS upgrade, so it is a perfect test case for a mainnet test run before we #LaunchPBaaS. This release actually has the ability to upgrade mainnet to PBaaS, but we believe it is prudent to have at least some time on this new protocol on testnet before the v1.0 release, which will upgrade mainnet. If we make no additional changes to the protocol in this release, which we do not intend to do at this time, this version may be able to follow the v1.0 upgrade. If we determine that it cannot, the oracle upgrade technology will enable the daemon to recognize that it is not capable and request that the user upgrade to a newer version without requiring a bootstrap for the upgrade. (Mainnet + Testnet)
This upgrade fixes all known testnet issues with no reset: Using v0.9.9, you should be able to sync fully and resume all cross-chain operations on the Verus test network, if you were not able to perform cross-chain operations or sync to the network on the prior version. As mentioned, someone seems to have mined with an intermediate version along the way on testnet and made the network unavailable without a bootstrap on the older daemon. This version should fix that issue as well as any cross-chain difficulties. Auto-notarization will be enabled on testnet in sync when the testfork executes. Until then, all witnessed cross-chain operations should be able to resume, if they have had difficulty. (Testnet until the #LaunchPBaaS release)
Bridging Blockchain Networks Without Witnesses: v0.9.9 is the first release of any blockchain protocol anywhere that we know of which enables cryptographically provable, cross-chain bridging across Verus and all PBaaS and other connected blockchains in the network, either combined with or independent of the need for notary witnesses. With notary witnesses, cross-chain transactions complete faster, but they are also checked against cryptographic evidence, making it difficult to impossible for anyone, including notary witnesses to take any action, even colluding with validators that would go against the wishes of the most chain power. We have been referring to this new cross-chain consensus technology as “auto-notarization”, as that is what it actually is, but it would also be accurate to call it Proof of Proof of Power, as that is how it works. For purposes of ensuring everyone understands the state of the technology, it is fully functional and we have taken great care to ensure it is sufficiently secure, but we have not yet had the protocol proven to an academic standard. Because of that, while it provides a security fall-back against misbehaving notary witnesses and will be fully functional and we believe sufficiently secure without notary witnesses on release, we currently recommend toconsider the protocol unproven at this time and that any serious PBaaS chains be launched with operational notary witnesses until further notice.
Using “notarizationprotocol”:1, which is also the default, a chain launch can specify notary witnesses that will be used when they do their job. Even if they stop witnessing for any reason, the protocol will fail-over to auto-notarization, ensuring that cross-chain transactions still function as expected, even if just for people to move their assets to another blockchain, although significantly more slowly and based solely on cryptographic proof and challenge resolution between merge miners and stakers. This cross-chain proof and challenge protocol operates even when witnesses are also operating and if miners and stakers continue to prove a more powerful chain than the one witnesses represent, the most powerful chain can still be confirmed. (Testnet until the #LaunchPBaaS release) Expanding L1 VerusID APIs: This release provides a major enhancement to the identity content multimap support with two new APIs, getidentityhistory and getidentitycontent that provide real-time mempool access and also introduce self-sovereign delete operations to identity content that can be used by applications, making it easy for applications to index, organize, and aggregate an unlimited amount of user content referenced by an identity and made available to the application. This is the technology we used for oracle upgrade notifications, as all of this is available at L1, making it possible to imagine future protocols that can deal smoothly with diverse community opinions worldwide, but always respect the sovereignty and decisions of all members on the network. (Testnet until the #LaunchPBaaS release)
Introducing Restricted VerusID Staking for PBaaS Chains: This release enables the stretch goal of restricted ID staking as an option for launching PBaaS chains. This option means that on such a PBaaS chain, only funds controlled by IDs with a parent of that PBaaS chain may stake blocks on that chain. When combined with restricted forms of ID issuance, whether approval or referral required and/or referral rewards, this capability opens up an entire new area for public/private blockchains and applications, as well as government, voting security, corporate, or organizational use cases.(Testnet until the #LaunchPBaaS release)
v0.9.9 represents the culmination of years of vision and work from across the entire community, and everyone who has been involved and contributed at all in any area over the last 5 years helped us get here today. From my perspective, I believe this represents a bigger potential benefit to the world than all of my prior professional efforts combined.
March 07, 2023, 10:44:06 PM
Verus has technological innovations in many encryption fields. However, because it is a project without ICO, completely decentralized, and not controlled by bookmakers, not many people know and understand it. Because it does not have enough capital to promote in the market.
March 01, 2023, 07:37:18 PM
An article for verus.
Building a More Interoperable Future with Verus PBaaS & Proof of Power
https://blockster.com/building-a-more-interoperable-future-with-verus-pbaas-and-proof-of-power
Building a More Interoperable Future with Verus PBaaS & Proof of Power
https://blockster.com/building-a-more-interoperable-future-with-verus-pbaas-and-proof-of-power
February 22, 2023, 07:54:28 AM
Announcing v0.9.6-2, CRITICAL UPDATE FOR MAINNET
This release contains a critical update for the Verus daemon. This version does not support testnet, but a future version will be released shortly to support it. For more information on running testnet, please refer to the previous release or the next one.
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.6-2
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.6-2
This release contains a critical update for the Verus daemon. This version does not support testnet, but a future version will be released shortly to support it. For more information on running testnet, please refer to the previous release or the next one.
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.6-2
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.6-2
December 17, 2022, 08:43:07 PM
Announcing v0.9.6-1, RECOMMENDED UPDATE FOR MAINNET, CRITICAL FOR CONTINUED TESTNET AND ETHEREUM BRIDGE (GOERLI) USE What’s New THERE IS NO TESTNET RESET, AND ALL OTHER NOTES REMAIN THE SAME AS LAST RELEASE. v0.9.6-1 has no mainnet changes and fixes the following testnet issues: 1) Fault when initiating mining and staking on a small number of machines 2) Sync from scratch issues on testnet This release fixes all reported issues in all community testing. There are no protocol changes, and no known changes required. All network functions should work as intended.
Verus PBaaS and DeFi RC6 - BUG BOUNTIES At this time, we are not aware of any bugs or errors in the DeFi, ID, or PBaaS cross chain protocols on this version of testnet. We do not anticipate any changes to the PBaaS protocol before mainnet release, and we hope you will join us on testnet trying out all of the incredible capabilities and looking for any potential, remaining issues that can possibly be found before mainnet release. While we don’t expect it to be easy to find bugs in the protocol, The Verus Coin Foundation is offering a bounty of at least 500 VRSC (possibly more for security related reports) for the first 10 people (3 still unclaimed) who are first to report any actual protocol bug before mainnet release, meaning failure of a properly executed command or API on a functioning VRSCTEST or PBaaS chain to function as intended. If anyone is first to find and describe the exploit for an exploitable security hole in any part of the protocol, the bounty will be a minimum of 1,000 VRSC, and for a serious potential security issue, 10,000 $VRSC.
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.6-1
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.6-1
Verus PBaaS and DeFi RC6 - BUG BOUNTIES At this time, we are not aware of any bugs or errors in the DeFi, ID, or PBaaS cross chain protocols on this version of testnet. We do not anticipate any changes to the PBaaS protocol before mainnet release, and we hope you will join us on testnet trying out all of the incredible capabilities and looking for any potential, remaining issues that can possibly be found before mainnet release. While we don’t expect it to be easy to find bugs in the protocol, The Verus Coin Foundation is offering a bounty of at least 500 VRSC (possibly more for security related reports) for the first 10 people (3 still unclaimed) who are first to report any actual protocol bug before mainnet release, meaning failure of a properly executed command or API on a functioning VRSCTEST or PBaaS chain to function as intended. If anyone is first to find and describe the exploit for an exploitable security hole in any part of the protocol, the bounty will be a minimum of 1,000 VRSC, and for a serious potential security issue, 10,000 $VRSC.
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.6-1
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.6-1
December 10, 2022, 01:04:32 AM
good project, looking forward to test the new features
December 09, 2022, 07:27:09 PM
Announcing v0.9.6, HIGHLY RECOMMENDED UPDATE FOR MAINNET, MANDATORY FOR NEW, RESET TESTNET AND ETHEREUM BRIDGE (GOERLI) USE What’s New For mainnet, v0.9.6 fixes the following issues: 1) An error in fee calculation that can result in nodes having difficulty accepting large, complex transactions with many z-outputs into their mempools. 2) Marketplace offers were not showing up properly under getoffers. 3) When using the “-privatechange” wallet option with a private change address, attempts to make marketplace offers could fail. v0.9.6 RESETS TESTNET AND COMPLETES ALL PROTOCOL UPDATES FEATURES AND CAPABILITIES EXPECTED FOR THE MAINNET PBAAS UPGRADE. WE DO NOT HAVE ANY NEAR TERM PLAN FOR ANOTHER TESTNET RESET AFTER THE v0.9.6 UPGRADE. IF YOU HAVE USED TESTNET WITH VERSIONS PRIOR TO v0.9.6, MAKE SURE TO DELETE AND CLEAR ANY EXISTING TESTNET DATA FOLDERS AS DESCRIBED IN THE RELEASE NOTES LINKED BELOW.
Although this release is likely to be robust enough for mainnet release, we have come this far with quality and will not rush for a few days earlier upgrade. We still plan to review and complete a small number of hardening items before PBaaS 1.0 is ready for its mainnet release. That said, this release fixes all reported issues in all community testing. Community developers, including myself are grateful for all of the testing many have contributed to to date. It has made it possible to get incredible test coverage across all network capabilities, and we appreciate all of your participation and pushing of boundaries. This release is expected to be the final PBaaS protocol that will be released on mainnet. There are no known changes required, and all functions should work as intended. Verus PBaaS and DeFi RC6 - BUG BOUNTIES At this time, we are not aware of any bugs or errors in the DeFi, ID, or PBaaS cross chain protocols on this version of testnet. We do not anticipate any changes to the PBaaS protocol before mainnet release, and we hope you will join us on testnet trying out all of the incredible capabilities and looking for any potential, remaining issues that can possibly be found before mainnet release. While we don’t expect it to be easy to find bugs in the protocol, The Verus Coin Foundation is offering a bounty of at least 500 VRSC (possibly more for security related reports) for the first 10 people (5 still unclaimed) who are first to report any actual protocol bug before mainnet release, meaning failure of a properly executed command or API on a functioning VRSCTEST or PBaaS chain to function as intended. If anyone is first to find and describe the exploit for an exploitable security hole in any part of the protocol, the bounty will be a minimum of 1,000 VRSC, and for a serious potential security issue, 10,000 $VRSC.
The rest of these release notes are the same as the prior release. We encourage you to drop by the pbaas-development channel, help the community prepare for mainnet release in the next week or two and start building your vision today!
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.6
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.6
Although this release is likely to be robust enough for mainnet release, we have come this far with quality and will not rush for a few days earlier upgrade. We still plan to review and complete a small number of hardening items before PBaaS 1.0 is ready for its mainnet release. That said, this release fixes all reported issues in all community testing. Community developers, including myself are grateful for all of the testing many have contributed to to date. It has made it possible to get incredible test coverage across all network capabilities, and we appreciate all of your participation and pushing of boundaries. This release is expected to be the final PBaaS protocol that will be released on mainnet. There are no known changes required, and all functions should work as intended. Verus PBaaS and DeFi RC6 - BUG BOUNTIES At this time, we are not aware of any bugs or errors in the DeFi, ID, or PBaaS cross chain protocols on this version of testnet. We do not anticipate any changes to the PBaaS protocol before mainnet release, and we hope you will join us on testnet trying out all of the incredible capabilities and looking for any potential, remaining issues that can possibly be found before mainnet release. While we don’t expect it to be easy to find bugs in the protocol, The Verus Coin Foundation is offering a bounty of at least 500 VRSC (possibly more for security related reports) for the first 10 people (5 still unclaimed) who are first to report any actual protocol bug before mainnet release, meaning failure of a properly executed command or API on a functioning VRSCTEST or PBaaS chain to function as intended. If anyone is first to find and describe the exploit for an exploitable security hole in any part of the protocol, the bounty will be a minimum of 1,000 VRSC, and for a serious potential security issue, 10,000 $VRSC.
The rest of these release notes are the same as the prior release. We encourage you to drop by the pbaas-development channel, help the community prepare for mainnet release in the next week or two and start building your vision today!
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.6
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.6
November 16, 2022, 10:25:39 AM
Announcing v0.9.5-2, RECOMMENDED UPDATE FOR MAINNET - CRITICAL FOR CONTINUED TESTNET USE YOU MUST BE UPDATED TO v0.9.5 OR LATER BY BLOCK 2291830, AT APPROXIMATELY 11:00 PM UTC, SATURDAY, NOVEMBER 19th, 2022 TO RELIABLY STAY SYNCHRONIZED TO THE VERUS MAINNET. WHILE THERE MAY BE A MAINNET PBAAS UPGRADE BEFORE THAT DATE, WE RECOMMEND THAT IF YOU HAVE NOT UPGRADED YET, THAT YOU DO SO NOW.
As with all v0.9.5-* releases, this release updates the Komodo notaries to season 6, with an activation height of 2291830, at approximately 11:00 PM UTC, Saturday, November 19th, 2022. ## What’s New For mainnet, this release labels spendable transactions for the getaddressutxos RPC API, which is used by Verus Mobile. This update is critical for users that have not upgraded to v0.9.5+ before block 2291830. For testnet, v0.9.5-2 introduces minor notarization fixes that will be important for those intending to launch and witness PBaaS chains. ## Ethereum Bridge Although its deployment has been delayed, there are no technical blockers, and we still expect the Ethereum bridge to be brought back up on the new Verus testnet within the next day or two.
We encourage you to drop by the pbaas-development channel, help the community prepare for the imminent mainnet release of the PBaaS upgrade and start building your vision today!
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.5-2
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.5-2
We encourage you to drop by the pbaas-development channel, help the community prepare for the imminent mainnet release of the PBaaS upgrade and start building your vision today!
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.5-2
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.5-2
September 21, 2022, 09:06:08 AM
ANNOUNCING v0.9.4, HIGHLY RECOMMENDED FOR MAINNET -- MANDATORY FOR TESTNET USE
Man, that wallet sucks big time. It is, hands down, one of the worst, least intuitive wallets I've ever come across. In addition to that, I've lost coins (or at least can't find them) twice for who knows what reason. And sometimes coins other than VRSC show up in it, sometimes not. There's no obvious way to make a backup or to restore a wallet....the whole thing is just a big mess, and it's turned me sour on VRSC completely--and I like the idea of the coin a lot, too.I've seen similar complaints on Reddit as well, so I know I'm not the only one who's frustrated. Oh, and if I were the dev team I'd seriously be looking into getting the coin listed on some reputable exchanges. Safetrade is as much of a clusterfuck as the Verus wallet is.
I am very sorry about your experience.
We have a wiki that could help you out.
Try bootstrapping your wallet if you are running the native mode https://wiki.verus.io/#!how-to/how-to_bootstrap.md
Also wallets are located here
Linux: ~/.komodo/VRSC
Mac OS: ~/Library/Application Support/Komodo/VRSC
Windows 10: %AppData%\Roaming\Komodo\VRSC\
OS independent through Verus Desktop: Click help, Show Verus data folder (default)
September 21, 2022, 08:55:37 AM
Announcing v0.9.4-4, UNCHANGED FOR MAINNET -- RECOMMENDED FOR CONTINUED TESTNET USE, MANDATORY FOR CONTINUED TESTNET MERGE OR BRIDGE MINING
This release has no material mainnet changes.
This release primarily upgrades the ETH bridge and also fixes a PBaaS cross-chain notarization issue that made miners and stakers consider themselves ineligible to enter cross-chain notarizations. There are no actual protocol changes.
The ETH bridge upgrade introduces the ability to enter notarizations between Ethereum Goerli and VRSCTEST using bridgekeeper without an Ethereum private key in your bridgekeeper configuration. This will enable you to still mine and potentially earn by agreeing or disagreeing with notarizations mined into the Verus blockchain, without needing to make transactions on or spend Ethereum for fees. This should also work with a free Infura account.
As a reminder, you can access the Verus <-> Ethereum testnet bridge here: https://ethtest.verus.services/, using your metamask or favorite Ethereum web wallet set to Goerli, to covert currencies on Verus and either send to a VerusID or other address, or even bounce right out to an Ethereum address when the MEV-resistant conversion is complete. To use these features you will need to get some Goerli Ethereum, either from a faucet on Goerli or via the Verus testnet liquidity baskets on Verus testnet, which you can easily send across to Ethereum.
The rest of these release notes are the same as the prior release. Drop by the discord pbaas-development channel to help us prepare for mainnet and start building your vision today!
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.4-4
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.4-4
This release has no material mainnet changes.
This release primarily upgrades the ETH bridge and also fixes a PBaaS cross-chain notarization issue that made miners and stakers consider themselves ineligible to enter cross-chain notarizations. There are no actual protocol changes.
The ETH bridge upgrade introduces the ability to enter notarizations between Ethereum Goerli and VRSCTEST using bridgekeeper without an Ethereum private key in your bridgekeeper configuration. This will enable you to still mine and potentially earn by agreeing or disagreeing with notarizations mined into the Verus blockchain, without needing to make transactions on or spend Ethereum for fees. This should also work with a free Infura account.
As a reminder, you can access the Verus <-> Ethereum testnet bridge here: https://ethtest.verus.services/, using your metamask or favorite Ethereum web wallet set to Goerli, to covert currencies on Verus and either send to a VerusID or other address, or even bounce right out to an Ethereum address when the MEV-resistant conversion is complete. To use these features you will need to get some Goerli Ethereum, either from a faucet on Goerli or via the Verus testnet liquidity baskets on Verus testnet, which you can easily send across to Ethereum.
The rest of these release notes are the same as the prior release. Drop by the discord pbaas-development channel to help us prepare for mainnet and start building your vision today!
CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.4-4
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.4-4
September 08, 2022, 12:52:40 PM
Hi,
We've have Verus (VRSC) on http://zpool.ca/algo/verushash. See below for connection details.
Fee only: 0.5% or less
BTC payouts are processed once a day for balances above 0.0015
Payouts for all other currencies are made automatically every 4 hours for balances above 0.05 and balances more than 0.0125 are included in one of the payouts each day.
- Sample configurations -
To mine verushash and get paid in VRSC:
Code:
-a verushash -o stratum+tcp://verushash.mine.zpool.ca:6143 -u VRSC_ADDRESS -p c=VRSC,zap=VRSC
Exchange to BTC:
Code:
-a verushash -o stratum+tcp://verushash.mine.zpool.ca:6143 -u BTC_ADDRESS -p c=BTC
All of our ports are NiceHash friendly, no need to specify any extra details
SSL/TLS is available for all ports. Simply prepend the port with a 5. Example for verushash: 56143
==============================
Support: https://discord.gg/n45n6Jj
Twitter: https://twitter.com/_zpool_
September 08, 2022, 12:46:52 AM
ANNOUNCING v0.9.4, HIGHLY RECOMMENDED FOR MAINNET -- MANDATORY FOR TESTNET USE
Man, that wallet sucks big time. It is, hands down, one of the worst, least intuitive wallets I've ever come across. In addition to that, I've lost coins (or at least can't find them) twice for who knows what reason. And sometimes coins other than VRSC show up in it, sometimes not. There's no obvious way to make a backup or to restore a wallet....the whole thing is just a big mess, and it's turned me sour on VRSC completely--and I like the idea of the coin a lot, too.I've seen similar complaints on Reddit as well, so I know I'm not the only one who's frustrated. Oh, and if I were the dev team I'd seriously be looking into getting the coin listed on some reputable exchanges. Safetrade is as much of a clusterfuck as the Verus wallet is.
August 27, 2022, 08:56:52 PM
ANNOUNCING v0.9.4, HIGHLY RECOMMENDED FOR MAINNET -- MANDATORY FOR TESTNET USE
This release fixes a mainnet issue that may, in rare cases, cause a node to deadlock. It also adds the following new features to mainnet:
* Auto TLS encrypted connections between nodes on mainnet and testnet, no action needed, but you can require that all connections be encrypted by starting the daemon with “-tlsenforcement”.
* A new “-idindex” flag that enables 3 new APIs to lookup identities by their primary addresses or revocation and recovery addresses, getidentitywithaddress, getidentitywithrevocation, and getidentitywithrecovery.
* Generally improved multithreading within the daemon. These improvements allow anyone to now write applications to easily graph or display public relationships between identities, transparent addresses, and transactions without compromising the privacy of private addresses, messages, or transactions between identities using name@:private endpoints, z-addresses or communicating via off-chain channels.
TESTNET PBaaS UPGRADE For testnet, this is RC2 of the PBaaS protocol and has some significant and important advances and changes. In addition to a great deal of progress hardening for mainnet, v0.9.4 introduces the following new features to the PBaaS testnet: All features above for mainnet * NFT mapped tokens and tokenized ID control In v0.9.4, as with v0.9.3, you can use root identities to create any kind of currencies, .veth IDs to create Ethereum mapped currencies, and what is new in v0.9.4 is that you can now use any type of ID or sub-ID to create a new kind of currency that will always have a 1 Satoshi supply and enable anyone holding it to have power over the ID that issued it. This type of currency is called tokenized ID control and can be treated like a super NFT over all copies of the source ID on all chains that were exported to other chains after the currency was created. Once the Ethereum contracts are upgraded with this capability,.veth or IDs with root names on the Verus blockchain can be used to create Ethereum NFT mapped currencies, which enable a Cryptopunk, Ethrock, or whatever other NFT you’d like to not only be sent to Verus, held on a revocable/recoverable ID, and also permanently upleveled with ID powers, being cryptographically bound as an ID’s permanent control token that can be sent to any chain or to Ethereum and back. This unique Verus-only technology and VerusIDs enable new models of complex, atomic and fully decentralized transactions. By using exported IDs across any number of networks and an ID control token, ownership of an unlimited array of assets across an unlimited number of networks can for the first time ever, have ownership transferred in one transaction. While NFT mapped tokens are supported on the RC2 PBaaS protocol, they have not yet been implemented in the Ethereum contracts. You will not be able to send NFTs from Ethereum to Verus or PBaaS chains until that work is complete, which we do not expect to take a great deal of time. * Liquidity currencies now support new methods to burn currency with the following results: burnweight - available to centralized currencies only and enables burning the primary currency to raise the reserve ratio weights of all reserves. burn for reserve currencies - in prior releases, burn was only used for primary currencies and would reduce the supply of a currency relative to its reserves, increasing the on-chain value of the primary currency. In v0.9.4, you can now also “burn” reserve currencies in a liquidity basket currency, which simply donates that amount of reserve into the currency’s reserves without taking any new supply in exchange. This is available to decentralized or centralized currencies.
* Bridgekeeper is now available for permissionless bridge notarization and selectable in the GUI on the mining page. For CLI, we will make a Node application available for testing in the next few days.
* RC1 cross-chain witness and notarization protocol enhanced for RC2 as follows: In RC2, any notarization to be confirmed must be first posted publicly to allow for potential to prove invalidity, and then later confirmed. In the prior protocol, a witnessed notarization could be posted to a chain and accepted when first seen. Upon analysis and discussion with @allbits and others, we realized that the attack vector of even stolen notary/witness keys combined with an in-secret 51% combined hash/stake attack could be prevented if we changed the protocol to first require posting the ready to finalize data and allow notaries who recognize that there is a signature on chain for something they don’t agree with (likely stolen key), to simply revoke their identity, which will prevent that notarization from ever being confirmed. This same security feature is supported between all PBaaS chains and has been implemented in the Ethereum contracts for witnesses as well. This new protocol also provides for other types of evidence to prevent finalization, such as proof that there exists a more powerful (most power rule) tip than one witnessed. Enabling decentralized, cross-chain most power rules is an advance in cross-chain protocols that over time will strongly protect censorship resistance qualities of any multichain protocol.
The above technology required changes to generalize evidence types between chains, enabling cryptographic enforcement that all notarizations are ultimately determined by miners and stakers and finalized by witnesses who must follow most power (stake+work) rules based on the protocol. Witnesses cannot finalize a chain tip unless alternating miners and stakers have posted 3 consecutive, agreeing, progressing cross-chain notarizations, without intervening disagreement, trading off more certain cross-chain transaction latency for one that depends on miners and stakers, meaning maximum decentralization and a high cost to DoS attack cross-chain, approaching impossible over any significant length of time. This approach makes the incentivized merge mining and bridge mining opportunities, as well as miner/staker participation, automatically part of and also critical to the cross-chain protocol. In v0.9.4, all users on the network may mine the Ethereum bridge via the bridgekeeper tool on the mining page in the GUI.
Testnet Reset To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
Linux: ~/.Komodo/vrsctest, ~/.verustest
Mac OS: ~/Library/Application Support/Komodo/vrsctest, ~/Library/Application\ Support/VerusTest
Windows 10: %AppData%\Roaming\Komodo\vrsctest, %AppData%\Roaming\VerusTest or %AppData%\Komodo\vrsctest, %AppData%\Roaming\VerusTest
Download binaries and additional release notes:
CLI: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.4
GUI: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.4
This release fixes a mainnet issue that may, in rare cases, cause a node to deadlock. It also adds the following new features to mainnet:
* Auto TLS encrypted connections between nodes on mainnet and testnet, no action needed, but you can require that all connections be encrypted by starting the daemon with “-tlsenforcement”.
* A new “-idindex” flag that enables 3 new APIs to lookup identities by their primary addresses or revocation and recovery addresses, getidentitywithaddress, getidentitywithrevocation, and getidentitywithrecovery.
* Generally improved multithreading within the daemon. These improvements allow anyone to now write applications to easily graph or display public relationships between identities, transparent addresses, and transactions without compromising the privacy of private addresses, messages, or transactions between identities using name@:private endpoints, z-addresses or communicating via off-chain channels.
TESTNET PBaaS UPGRADE For testnet, this is RC2 of the PBaaS protocol and has some significant and important advances and changes. In addition to a great deal of progress hardening for mainnet, v0.9.4 introduces the following new features to the PBaaS testnet: All features above for mainnet * NFT mapped tokens and tokenized ID control In v0.9.4, as with v0.9.3, you can use root identities to create any kind of currencies, .veth IDs to create Ethereum mapped currencies, and what is new in v0.9.4 is that you can now use any type of ID or sub-ID to create a new kind of currency that will always have a 1 Satoshi supply and enable anyone holding it to have power over the ID that issued it. This type of currency is called tokenized ID control and can be treated like a super NFT over all copies of the source ID on all chains that were exported to other chains after the currency was created. Once the Ethereum contracts are upgraded with this capability,.veth or IDs with root names on the Verus blockchain can be used to create Ethereum NFT mapped currencies, which enable a Cryptopunk, Ethrock, or whatever other NFT you’d like to not only be sent to Verus, held on a revocable/recoverable ID, and also permanently upleveled with ID powers, being cryptographically bound as an ID’s permanent control token that can be sent to any chain or to Ethereum and back. This unique Verus-only technology and VerusIDs enable new models of complex, atomic and fully decentralized transactions. By using exported IDs across any number of networks and an ID control token, ownership of an unlimited array of assets across an unlimited number of networks can for the first time ever, have ownership transferred in one transaction. While NFT mapped tokens are supported on the RC2 PBaaS protocol, they have not yet been implemented in the Ethereum contracts. You will not be able to send NFTs from Ethereum to Verus or PBaaS chains until that work is complete, which we do not expect to take a great deal of time. * Liquidity currencies now support new methods to burn currency with the following results: burnweight - available to centralized currencies only and enables burning the primary currency to raise the reserve ratio weights of all reserves. burn for reserve currencies - in prior releases, burn was only used for primary currencies and would reduce the supply of a currency relative to its reserves, increasing the on-chain value of the primary currency. In v0.9.4, you can now also “burn” reserve currencies in a liquidity basket currency, which simply donates that amount of reserve into the currency’s reserves without taking any new supply in exchange. This is available to decentralized or centralized currencies.
* Bridgekeeper is now available for permissionless bridge notarization and selectable in the GUI on the mining page. For CLI, we will make a Node application available for testing in the next few days.
* RC1 cross-chain witness and notarization protocol enhanced for RC2 as follows: In RC2, any notarization to be confirmed must be first posted publicly to allow for potential to prove invalidity, and then later confirmed. In the prior protocol, a witnessed notarization could be posted to a chain and accepted when first seen. Upon analysis and discussion with @allbits and others, we realized that the attack vector of even stolen notary/witness keys combined with an in-secret 51% combined hash/stake attack could be prevented if we changed the protocol to first require posting the ready to finalize data and allow notaries who recognize that there is a signature on chain for something they don’t agree with (likely stolen key), to simply revoke their identity, which will prevent that notarization from ever being confirmed. This same security feature is supported between all PBaaS chains and has been implemented in the Ethereum contracts for witnesses as well. This new protocol also provides for other types of evidence to prevent finalization, such as proof that there exists a more powerful (most power rule) tip than one witnessed. Enabling decentralized, cross-chain most power rules is an advance in cross-chain protocols that over time will strongly protect censorship resistance qualities of any multichain protocol.
The above technology required changes to generalize evidence types between chains, enabling cryptographic enforcement that all notarizations are ultimately determined by miners and stakers and finalized by witnesses who must follow most power (stake+work) rules based on the protocol. Witnesses cannot finalize a chain tip unless alternating miners and stakers have posted 3 consecutive, agreeing, progressing cross-chain notarizations, without intervening disagreement, trading off more certain cross-chain transaction latency for one that depends on miners and stakers, meaning maximum decentralization and a high cost to DoS attack cross-chain, approaching impossible over any significant length of time. This approach makes the incentivized merge mining and bridge mining opportunities, as well as miner/staker participation, automatically part of and also critical to the cross-chain protocol. In v0.9.4, all users on the network may mine the Ethereum bridge via the bridgekeeper tool on the mining page in the GUI.
Testnet Reset To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
Linux: ~/.Komodo/vrsctest, ~/.verustest
Mac OS: ~/Library/Application Support/Komodo/vrsctest, ~/Library/Application\ Support/VerusTest
Windows 10: %AppData%\Roaming\Komodo\vrsctest, %AppData%\Roaming\VerusTest or %AppData%\Komodo\vrsctest, %AppData%\Roaming\VerusTest
Download binaries and additional release notes:
CLI: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.4
GUI: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.4
May 29, 2022, 03:47:50 AM
Read up this medium article guys.
https://medium.com/veruscoin/community-currencies-a-case-study-to-explore-new-technical-possibilities-ede897433b55
https://medium.com/veruscoin/community-currencies-a-case-study-to-explore-new-technical-possibilities-ede897433b55
January 18, 2022, 07:45:25 AM
great!vrsc verus is also good, it is very promising in the future!
vrsc,great ! when will it rise to $10? I guess it will rise to $20 in the near future.
[moderator's note: consecutive posts merged]
vrsc,great ! when will it rise to $10? I guess it will rise to $20 in the near future.
[moderator's note: consecutive posts merged]
Check your verusID vault anywhere in the world! https://www.vaultalert.net/
November 26, 2021, 12:51:01 AM
great!vrsc verus is also good, it is very promising in the future!
vrsc,great ! when will it rise to $10? I guess it will rise to $20 in the near future.
[moderator's note: consecutive posts merged]
vrsc,great ! when will it rise to $10? I guess it will rise to $20 in the near future.
[moderator's note: consecutive posts merged]
November 15, 2021, 10:38:37 AM
Announcing MANDATORY Verus v0.9.0 Mainnet Release of Verus Vault and the on-chain NFT and ID Marketplace
TO REMAIN CONNECTED TO THE MAINNET VERUS BLOCKCHAIN, YOU MUST UPGRADE FULL NODES TO v0.9.0 OR LATER BY BLOCK 1796400, which is expected to occur on or around Monday, November 29th at 6:15PM UTC.
Verus ID and NFT Marketplace
Buy and sell VerusIDs on-chain, advertising your offer directly to the owner of an ID or NFT, or posting the sale of your NFT on the worldwide blockchain for all the world to see. Execute transactions in a completely decentralized way. Pay or offer to pay from a transparent or zero-knowledge private address, still auditable by you. Accept payment to either as well, and best of all, execute your transactions directly, peer-to-peer without any intermediary necessary. Don’t worry the on-chain model still makes room for owners to select and share proceeds with value added agents, marketing organizations, or other participants in a new economy of provable digital ownership. It’s the next step in the evolution of VerusID, the most powerful self-sovereign identity and secure funds storage model in the digital world.
Verus Vault
With Verus Vault you can now protect funds on a VerusID, even from theft of a private key! If you lock your VerusID with Vault you cannot spend funds from that identity at all until it is again unlocked. While locked, you can still stake those same funds on the Verus network and earn by doing so. Of course, you can also still receive funds.
IT IS IMPORTANT TO NOTE THAT ENABLING REVOCATION, RECOVERY, AND ALL VERUS VAULT CAPABILITIES REQUIRE YOU TO HAVE ONE PRIMARY IDENTITY, AND AT LEAST ONE REVOCATION/RECOVERY ID CONFIGURED.
A locked VerusID can always be revoked and recovered by its revocation and recovery authority identities, which circumvents the lock. At the same time, anyone with only the primary keys, even a multisig of primary keys must first unlock, then wait for the predetermined unlock time before they can spend or access funds. This gives you, or maybe a company that specializes in watching the blockchain to whom you've assigned the revocation ID time to revoke and recover whenever an unauthorized unlock occurs. That means that like a bank, setting a 24 hour unlock delay on your locked IDs actually provides the first decentralized solution to the infamous 5 dollar wrench attack.
In addition to a new level of blockchain protection and decentralized funds recovery, Verus Vault provides the same security for your IDs and NFTs as well as time locks for other purposes, such as vesting schedules, trusts, and inheritance. With Verus Vault, you can now protect and recover your funds, preserving all your assets and generational blockchain wealth from common forms of crypto loss or theft, no bank required.
Testnet Reset
To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
- Linux:
Countdown to Activation
https://countdown.verus.io/activation/
CLI: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.0
GUI: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.0
TO REMAIN CONNECTED TO THE MAINNET VERUS BLOCKCHAIN, YOU MUST UPGRADE FULL NODES TO v0.9.0 OR LATER BY BLOCK 1796400, which is expected to occur on or around Monday, November 29th at 6:15PM UTC.
Verus ID and NFT Marketplace
Buy and sell VerusIDs on-chain, advertising your offer directly to the owner of an ID or NFT, or posting the sale of your NFT on the worldwide blockchain for all the world to see. Execute transactions in a completely decentralized way. Pay or offer to pay from a transparent or zero-knowledge private address, still auditable by you. Accept payment to either as well, and best of all, execute your transactions directly, peer-to-peer without any intermediary necessary. Don’t worry the on-chain model still makes room for owners to select and share proceeds with value added agents, marketing organizations, or other participants in a new economy of provable digital ownership. It’s the next step in the evolution of VerusID, the most powerful self-sovereign identity and secure funds storage model in the digital world.
Verus Vault
With Verus Vault you can now protect funds on a VerusID, even from theft of a private key! If you lock your VerusID with Vault you cannot spend funds from that identity at all until it is again unlocked. While locked, you can still stake those same funds on the Verus network and earn by doing so. Of course, you can also still receive funds.
IT IS IMPORTANT TO NOTE THAT ENABLING REVOCATION, RECOVERY, AND ALL VERUS VAULT CAPABILITIES REQUIRE YOU TO HAVE ONE PRIMARY IDENTITY, AND AT LEAST ONE REVOCATION/RECOVERY ID CONFIGURED.
A locked VerusID can always be revoked and recovered by its revocation and recovery authority identities, which circumvents the lock. At the same time, anyone with only the primary keys, even a multisig of primary keys must first unlock, then wait for the predetermined unlock time before they can spend or access funds. This gives you, or maybe a company that specializes in watching the blockchain to whom you've assigned the revocation ID time to revoke and recover whenever an unauthorized unlock occurs. That means that like a bank, setting a 24 hour unlock delay on your locked IDs actually provides the first decentralized solution to the infamous 5 dollar wrench attack.
In addition to a new level of blockchain protection and decentralized funds recovery, Verus Vault provides the same security for your IDs and NFTs as well as time locks for other purposes, such as vesting schedules, trusts, and inheritance. With Verus Vault, you can now protect and recover your funds, preserving all your assets and generational blockchain wealth from common forms of crypto loss or theft, no bank required.
Testnet Reset
To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
- Linux:
Code:
~/.Komodo/vrsctest
~/.verustest
- Mac OS: ~/.verustest
Code:
~/Library/Application Support/Komodo/vrsctest
~/Library/Application\ Support/VerusTest
- Windows 10: ~/Library/Application\ Support/VerusTest
Code:
%AppData%\Roaming\Komodo\vrsctest
%AppData%\Roaming\VerusTest
or %AppData%\Roaming\VerusTest
Code:
%AppData%\Komodo\vrsctest
%AppData%\Roaming\VerusTest
%AppData%\Roaming\VerusTest
Countdown to Activation
https://countdown.verus.io/activation/
CLI: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.0
GUI: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.0
Jump to: