[ANN] Verus (VRSC) - zk-SNARK privacy, CPU-mining, 50/50 POW/POS, fair launch

[VerusCoin]

Announcing v0.7.3-2 CRITICAL mainnet upgrade and the world premier of the Verus Project’s new PBaaS technology multicurrency, multichain DeFi protocols and immediate public availability of its fully functional, multichain testnet.

Soon^TM is today! With no programming, you can now create new identities, currencies, liquidity pools, and blockchains for your business, your government, your projects, a worthy cause, your family, or your next decentralized application suite. Send currencies worldwide on the same chain, or across blockchains with ease. Even convert currencies to others on the network without an exchange by sending to yourself and converting along the way.

This testnet includes following capabilities, which to our knowledge are not available on any other decentralized platform.

Self sovereign, revocable, recoverable identities (currently on mainnet) with zero-knowledge privacy support (VerusID) - Enables permissionless registration of friendly name strong identities and funds addresses that are simultaneously fully self-sovereign, revocable, and recoverable.

Staking-capable time locking and theft prevention (Verus Vault) - Enables identities to be locked, preventing any funds under their control from being spent while locked, but still allowing seamless staking of funds.
 
Multi-currency, user created, decentralized tokens and merge-mineable, interoperable blockchains without programming - Enables any user with an ID to create their own token currency or even full fledged, multi-currency, ID-issuing 50% POW/50% POS, 51% hash attack resistant blockchain that can send and receive from the Verus chain which launched it.

Consensus integrated DeFi liquidity pools and fractional currency baskets - Enables any ID owner to define Verus DeFi fractional basket currencies with one or more asset currencies backing the liquidity pool at a fractional percentage ranging from 5% to 100%.

Blockchain-based, crowdfunding currency launches with minimum participation or automatic refunds, including for dual launches (blockchain and bridge) - Enables you to set required minimum levels of worldwide participation in your preferred currencies on chain. If by the start time of your currency, minimums are not met, all participants will automatically get their pre-conversions (minus network fees) refunded.

Simultaneous blockchain and blockchain liquidity pool launches - Enables the launch of a world class, worldwide, merge-mineable blockchain along with a fully decentralized or centralized “bridge” converter liquidity pool as part of defining a new blockchain.

An interoperable, multichain network for new use cases and unlimited scale - Allows for the creation of an unlimited number of interoperable blockchains in the Verus network.

Merge mining of up to 22 blockchains simultaneously - Lets you multiply your hashpower by up to 22x by mining multiple chains at the same time, on the same hashpower.

Blockchain fee pools and anti-front running - Addresses MEV and more elegantly solves the EIP1559 problem with a block reward independent economy.
 
NOTE: THIS IS A CRITICAL RELEASE FOR MAINNET AND ALSO INCLUDES TESTNET. ALL NEW FEATURES ABOVE BESIDES VerusID ARE TESTNET ONLY
 
CONGRATULATIONS TO THE ENTIRE COMMUNITY!!
GUI releases for all platforms: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.7.3-2
CLI releases for all platforms: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.7.3-2

[1714895348]

1714895348

[1714895348]

1714895348

[1714895348]

1714895348

[VerusCoin]

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

[Oink70]

Verus Monthly Recap
The first edition (August) of Verus Monthly Recap is out now!

https://medium.com/@meyse/august-2021-verus-monthly-recap-4241c7c80b8a

[VerusCommunity]

September 2021 — Verus Monthly Recap

The latest Verus updates on development, community, ecosystem and more.

https://medium.com/veruscoin/september-2021-verus-monthly-recap-9f0961624d0a

[VerusCommunity]

From Mikeout in Discord

"People owe it to themselves to check this out. @𝙊𝙞𝙣𝙠 sorry for the double post, this has to be an exception 🙂 ! https://luckpool.net/profile/identity/mike.vrsc "

[VerusCoin]

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:

Code:

~/.Komodo/vrsctest
~/.verustest

- Mac OS:

Code:

~/Library/Application Support/Komodo/vrsctest
~/Library/Application\ Support/VerusTest

- Windows 10:

Code:

%AppData%\Roaming\Komodo\vrsctest
%AppData%\Roaming\VerusTest

or

Code:

%AppData%\Komodo\vrsctest
%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

[terwenlee]

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]

[dudezmobi.vrsc]

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]

Check your verusID vault anywhere in the world! https://www.vaultalert.net/

[dudezmobi.vrsc]

Read up this medium article guys.

https://medium.com/veruscoin/community-currencies-a-case-study-to-explore-new-technical-possibilities-ede897433b55

[dudezmobi.vrsc]

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


[The Sceptical Chymist]

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.

[crackfoo]

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_

[dudezmobi.vrsc]

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

[dudezmobi.vrsc]

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)

[dudezmobi.vrsc]

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

[dudezmobi.vrsc]

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

[lmmjvsd]

good project, looking forward to test the new features

[dudezmobi.vrsc]

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

[dudezmobi.vrsc]

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

[dudezmobi.vrsc]

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