Topic: [ANN] Verus (VRSC) - zk-SNARK privacy, CPU-mining, 50/50 POW/POS, fair launch - page 2. (Read 49636 times)

verus at consensus

https://www.youtube.com/watch?v=HDasZ_tZYaU

https://www.youtube.com/watch?v=3a7N2xx1DXg&list=LL

Announcing Verus v1.2.3-2 - CRITICAL UPGRADE FOR NETWORK STABILITY HIGHLY RECOMMENDED ALL USERS, ESPECIALLY BLOCK PRODUCERS AND WITNESSES.


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

Yesterday, we identified and investigated a minor fork. This process exposed a rare race condition which had been latent but was triggered by an unusual combination of events in the network. v1.2.3-2 addresses this and all similar potential issues. While it's unlikely to reoccur, we consider it a critical upgrade that eliminates the possibility entirely.

GUI only: The VRSC and VRSCTEST chains will only launch with fastload enabled. A Verus Desktop version that provides users the option to enable or disable fastload will be released soon. There are no protocol or other changes for v1.2.3-2

verus dapp

https://verus.io/papers/Building_dApps_at_Any_Scale.pdf

Announcing Verus v1.2.3-1 - Optional upgrade with fastload option

IT IS IMPORTANT TO UPGRADE TO AT LEAST v1.2.3 BEFORE ACTIVATION IN ORDER TO CONTINUE SYNCHRONIZING TO THE CHAIN BY THE FOLLOWING BLOCKS: Verus mainnet: 3093850 (Sun Jun 16 08:54:44 PM UTC) vARRR mainnet: 107590 (Tue Jun 18 10:49:13 PM UTC) Testnet: immediately IF YOU DO NOT UPGRADE TO v1.2.3 OR LATER AND HAVE NOT CHANGED THE DEFAULT ORACLE, A NOTIFICATION THAT WILL PAUSE YOUR NODE AND ALLOW YOU TO UPGRADE AND RESUME WITHOUT NEEDING A BOOTSTRAP WHEN YOU ARE ABLE

What’s new
* Added the -fastload startup option to disable memory compression, resulting in faster daemon launch times at the expense of significantly higher memory use.
* GUI only: The VRSC and VRSCTEST chains will only launch with fastload enabled so this version can be skipped in favor of v1.2.3 if the memory efficiency is preferred. An option to enable or disable fastload will be included in a future Verus Desktop release.

There are no protocol or other changes for v1.2.3-1

CLI RELEASE: https://github.com/VerusCoin/VerusCoin/releases/tag/v1.2.3-1

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

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

Announcing Verus v1.2.3

CLI RELEASE: https://github.com/VerusCoin/VerusCoin/releases/tag/v1.2.3

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

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

MANDATORY UPDATE FOR MAINNET VERUS, vARRR, AND TESTNET - MASSIVE RAM USAGE (> 2GB) REDUCTION AND BASKET UNBLOCK IT IS IMPORTANT TO UPGRADE TO v1.2.3 BEFORE ACTIVATION IN ORDER TO CONTINUE SYNCHRONIZING TO THE CHAIN BY THE FOLLOWING BLOCKS: Verus mainnet: 3093850 (just over 2 days from now) vARRR mainnet: 107590 (just over 4 days from now) Testnet: immediately THIS IS AN URGENT AND MANDATORY UPDATE, REQUIRED TO RESTART PROCESSING OF THE “SWITCH” BASKET CURRENCY IF YOU DO NOT UPGRADE IN TIME AND HAVE NOT CHANGED THE DEFAULT ORACLE, WE WILL ACTIVATE A NOTIFICATION THAT WILL PAUSE YOUR NODE AND ALLOW YOU TO UPGRADE AND RESUME WITHOUT NEEDING A BOOTSTRAP WHEN YOU ARE ABLE

What’s new?

1) v1.2.3 contains a massive optimization to the use of RAM for storing chain data and implements a real time compression technique called RLE, or run length encoding, on objects in memory to reduce RAM usage by over 2GB on Verus mainnet. This change will give more headroom on node machines that may have been struggling with growing RAM requirements and enable people to run more blockchains on a single node machine. (a lot slower speed of loading)

2) v1.2.3 addresses stalled processing of the Switch basket currency that has occurred on mainnet. This release addresses the issue at activation and ensures that the same thing won’t happen in the future. There are no other protocol changes for v1.2.3. Please update as soon as you are able to do so.

https://verusmarkets.com/

Excited to announce the launch of verusmarkets.com
! Stay updated with the latest prices & news on the #Verus
$VRSC
#Blockchain
. Verus #DeFi
offers unique capabilities with its innovative multichain Currencies and Currency Baskets. Truly Decentralized conversions for all assets (including RWA & DePIN) for everyone. Anyone can launch a currency, basket of currencies or Public Blockchain as a Service (PBaaS) on Verus using simple commands. A Developers playground awaits. Crypto enthusiasts can provide liquidity, create and/or hold a diverse portfolio of their favorite assets or Arbitrage their way to success. Entrepreneurs can start a business and instantly access rent-free unlimited-scale public infrastructure ready for #web3‌‌
#Dapp
's. Limited only by your imagination, everyone's welcome. Verus Technology will be on full display at #Consenus2024
(booth 1245). Dev's and Community members will be there to showcase the power of the Verus protocol and answer all your questions.

From a medium article: https://medium.com/veruscoin/consensus-2024-verus-showcases-fully-completed-pbaas-blockchain-technology-0dba30607369

The L0/1 Verus Protocol Solves Major Issues with Ethereum and Other VM-centric Networks

Developing dApps with Verus is much more straightforward than building to a VM-based application model and results in inherently more capable, secure and scalable solutions. The Verus Protocol solves issues with gas fees, enables unlimited scale, is not vulnerable to smart contract hacks and bugs, addresses MEV at the protocol level, provides an identity model (VerusID) that applications can leverage and profit from, includes provable cross-chain and multichain support, does away with insecure and phishing-prone wallet approval mechanisms, and does not require expensive Solidity developers for applications, unless they must also have an Ethereum component to them.

All these issues are solved with the L0/1 Verus Protocol. Verus does not use smart contracts — it uses smart transactions. Verus smart transactions [read more] are much easier to use (no programming needed) in practice to achieve most capabilities, if not all, compared to VM-protocols that use smart contracts. Yet Verus is still fully interoperable with Ethereum through the non-custodial, trustless and decentralized Verus-Ethereum Bridge with liquidity pool currency [more on the Bridge].
Showcasing Verus App-Development Opportunities at Consensus 2024

Get ready for a new era of decentralized application development. Unlike today’s complex smart contract applications, requiring VM-based smart contracts that talk to user facing applications through server-side APIs and phishing-prone web-interfaces using public key hashes or rented names as identity, the Verus network is a Layer 1 (L1) and Layer 0 (L0) protocol with composable and powerful multi-chain core primitives, including identities, currencies, MEV-resistant liquidity baskets, updateable, even transferable ID-bound databases that can comprise NFTs and real world assets, all on a 100% fully decentralized, unlimited scale backbone, secured by the 50% proof-of-stake / 50% proof-of-work, 51% hash attack resistant Verus Proof of Power (PoP) consensus and accessible securely from mobile clients or cloud-based web-applications.

Build applications in your favorite framework for clients and access the Verus network either through QR-codes and deep-links to a client-side wallet under user control or talk directly to data-indexed, blockchain nodes, capable of providing fast access to an unlimited number of user identities and their unlimited Verus Data Exchange Format (VDXF) indexable key-value database providing provable, optionally private, worldwide resolvable data at unlimited scale over an unlimited number of blockchains. All of this power, including inherent eCommerce and markets of all types are usable by applications, and unlike yesterday’s Internet, application-owned data stays under application control, while user-owned data remains under user control and subject to voluntary, provable disclosure, protected by zero knowledge privacy, as it should always have been.

Write applications your way, your client frameworks, your languages, with links and RPC calls to the decentralized Internet of Value. Connect through one or more blockchains. Use, create, sell, and provision your application’s permanent IDs for secure login, KYC, commerce, and provable data at scale, all on the rent-free, credibly neutral and fully decentralized Internet of Value.

Builders of applications, organizations, and businesses can use the Verus Protocol to provision IDs, manage and interact with users and user state at any scale, launch currencies (e.g. tokens, liquidity baskets [see docs]), even fully interoperable, independent, customizable worldwide blockchains with their own economics and fee structure, while sharing mining and economic power across the entire Verus Protocol network of unlimited PBaaS chains. All currencies, whether native currencies of a new blockchain, easily created and minted tokens, or MEV-resistant liquidity baskets are easy to launch and access with the protocol on Verus or any connected PBaaS chain. All of them, from the moment they are launched can be exported to Ethereum as ERC20s [see docs] or ERC721 currencies or any chain across the Verus ecosystem. All currencies on the network, including tokens, cross-chain currencies, and even liquidity baskets and their supplies are secured by miners and stakers according to protocol rules. On other blockchain networks, this level of security is applied to single native currencies, on Verus, all currencies on a chain are primitives known to and accounted for by the protocol, eliminating entire classes of smart contract risks that result when every contract reinvents a new way to account for its currency but has no systemic control.

With Verus, currencies are compatible with ERC20s. Verus applications can leverage, but do not require Solidity developers or VM-based programming. Additionally all ERC-20s can be permissionlessly bridged over from Ethereum to Verus [see docs], giving users and application builders the freedom to switch seamlessly between the Verus and Ethereum networks.

All currencies on the Verus network (also the ones bridged over from Ethereum) can be used with Verus DeFi, another primitive inherent to the protocol. Verus DeFi enables liquidity baskets of up to 10 underlying reserve currencies and can serve as a unique, self-balancing, MEV-resistant portfolio, a permissionless or permissioned ID registrar where fees go to the LPs of the basket, or an easy way to send from any reserve currency or the basket currency itself to any other without worrying about block builder reordering or MEV, as all conversions of a liquidity basket in any direction that are processed within one or more blocks are always solved simultaneously, no front and not back. Every conversion gets the same price in each direction with no spread and an ultra low fee (max. 0.05%), again, all part of the L1 consensus.

Whether you plan to build eCommerce enabled supply chains, massively scalable ownership-based games, real world asset eCommerce enabled networks, voting systems, identity management networks, communication networks, financial networks, 3D metaverses with identities, brands, and ownership or just about any application for a better Web3 on the Internet of Value, you’ll be left behind if you don’t deep dive on Verus first.

Join us in the next crypto revolution. Verus, with truth and privacy for all!

Come to the Verus booth on May 29–31 at Consensus 2024. The worldwide community is happy to get you started with a free VerusID, the easy to use Verus Mobile or any of the wide range of protocol features.
Amazing Verus Community

The Verus community united to facilitate participation at Consensus 2024 by generously contributing VRSC, ETH, DAI, MKR, Bridge.vETH and BTC. A heartfelt thank you to all the contributors! ❤️

The Verus community used the funds to secure a two-block booth at Consensus, along with other facilities that we can not disclose yet.

Numerous members of the Verus community are participating in Consensus 2024, and we invite you to be a part of it too! Let’s create a significant presence and showcase to the world the wide range of capabilities of Verus. We’re excited and believe that it will be an excellent opportunity for the growth and exposure of the Verus ecosystem!

From verus team

We have reports of a minor fork of 11 MH on the network that is not being notarized to Ethereum and will not cause any problem on the decentralized connection, but could potentially cause issues for centralized services that may have gotten onto that fork. Please check your nodes or native wallets and confirm that you are on the same network as the explorer. We are continuing to look into the issue, but we do not see any forks yet on servers that have not reported.

After investigation, we have determined that although, just after the announcement of v1.2.2-5, they were notified via github, according to their required process, many (or most) of the KMD notaries did not upgrade to v1.2.2-5, nor did they communicate or request additional time to do so. As a result, we did not extend the upgrade block height with an oracle notification. Shortly after the upgrade activated, the KMD notaries began notarizing a fork caused by them being unable to follow the network upgrade and also being connected to a small amount of hash + at least 3 million VRSC of staking power, also not upgraded. As a result, they began notarizing a very small fork that could have been followed by an updated node, if that updated node was connected to a subnetwork consisting of only the Komodo notaries and older versions mining and staking. Fortunately, the Verus protocol will not follow the Komodo notaries if they disagree with the VIP notarizations made by the most powerful chain into ETH, ensuring that they can add value if consistent, but that the ETH connection always tracks the most powerful & witnessed chain in any potential situation that might create a fork. Once the v1.2.2-4 KMD notary nodes saw the post upgrade blocks, they would have rejected those blocks and banned the nodes sending them, creating an isolated network, which they continued to notarize. From our current analysis, there is no harm done to the Verus network, and there were a minimal number of nodes that ended up following the fork. We have obtained access to the fork and stopped it with an Oracle update, ensuring that anyone who was not intentionally trying to ignore oracle updates on that fork can not be harmed by any potential activity. At this time, the Verus network is completely fine and being finalized by Verus VIP against the Ethereum network. While it is possible for the Komodo notaries to fix their situation by upgrading, the network is fine whether they do or not.

Announcing Verus v1.2.2-5

UPDATE MAINNET NODES BY:
– VERUS MAINNET BEFORE BLOCK 3050000
– vARRR MAINNET BEFORE vARRR BLOCK 67000, SAME AS PRIOR RELEASE
NEW PBaaS CHAINS SHOULD LAUNCH USING v1.2.2-5 OR LATER
CRITICAL UPDATE ASAP FOR ALL VALIDATORS

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

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


During the launch of Kaiju, a transaction was accepted by the network that requested a conversion from a currency not in the Kaiju basket to Kaiju. In the checks where it was accepted, it was marked for refund, and although we saw it before launch, we expected it to proceed normally and refund.

When the Kaiju launch block came, an additional check for that case that was present on import considered it an error, and instead of allowing it to pass, refused to consider that import valid, blocking completion of the launch protocol. When v1.2.2-5 represents the majority of the network validators and activates, validators will stop preventing that import from being processed, Kaiju launch protocol will complete, the offending transfer will be refunded, and the Kaiju basket will then operate as usual. Please update as soon as possible to clear the way for normal operation of Kaiju or any future currency launch, preventing any such issue in the future on all chains.

Announcing Verus Mobile v1.0.12 - MANDATORY UPDATE FOR THOSE WANTING TO CONVERT OR SEND DAI CROSS-CHAIN FROM ETHEREUM TO VERUS DAI ETH-VRSC Transactions:

Android App is available on the play store at: https://play.google.com/store/apps/details?id=org.autonomoussoftwarefoundation.verusmobile.android&hl=en&gl=US

iOS App Available on the Apple App Store (version 1.0.12 still pending): https://apps.apple.com/us/app/verus-mobile/id6447361908

Github Builds for Android: https://github.com/VerusCoin/Verus-Mobile/releases


The last 2 versions of Verus Mobile had an issue where it would often underestimate the GAS required for sending DAI to Verus. This usually leads to DAI transfers via mobile from the Ethereum network sent across the Etherum-Verus bridge to be rejected, while the ETH network still burns up the calculated fee.

This is due to an ETH requirement that the fee provided actually must exceed the fee that will be used. This update fixes that issue by increasing the calculated estimate to an amount above that which will actually be used. Do not send DAI across the Verus-Ethereum bridge with Verus Mobile (you can use the bridge website instead) until you upgrade, or you risk losing the ETH fee and having your transaction reverted.

End to current TestFlight App (Verus Wallet): Due to Apple App Store policy, the TestFlight version of Verus Mobile (called Verus Wallet) will no longer be updated (beyond 1.0.11). If you have any keys controlled by this wallet, make sure to back them up or move them to a release of Verus Mobile or another wallet before the current version expires. A new TestFlight version of the app will be released in the coming future, but it will be considered a different app by iOS and data will not be transferred. It is recommended that you import your iOS TestFlight app data into the App Store version for now and use the App Store app instead.

The App Store app remains unaffected by this and is kept up to date. This also means in order to send DAI across the bridge, please use the Apple App Store app. Android builds remain unaffected.


New Interface and Conversion Suggestions: As of 1.0.11, some of you may have noticed a slightly different interface on the wallet overview pages for currencies. This should increase performance with multiple wallet cards, and increase usability. Also, suggested paths for conversion on PBaaS chains, like vARRR, should be accurate now and show all possible options.




Announcing Verus v1.2.2-4 - MANDATORY UPDATE FOR vARRR MAINNET SUPPORT BEFORE vARRR BLOCK 67000 (in approximately 1 month) OR EARLIER IF DECIDED BY THE vARRR COMMUNITY. NEW PBaaS CHAINS SHOULD LAUNCH USING v1.2.2-4

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

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

MANDATORY UPDATE FOR CONTINUED VERUS TESTNET USAGE

CRITICAL UPDATE FOR VERUS MINING AND STAKING NODES

A small number of recently exported VerusIDs from Verus to vARRR exposed an issue that is not a security issue but has a potential unintended consequence for some users. Due to the way that VerusID locks and unlocks work, VerusIDs that have been locked, then unlocked, then exported to vARRR from Verus may end up locked on vARRR until a block height very far in the future that is the block where it actually unlocked on Verus. This happened to 3 IDs that were exported.

v1.2.2-4 will check in the sendcurrency command when a VerusID is exported to another chain if the timelock is set as an absolute timelock (specific to chain), or if the timelock is non-zero on an unlocked ID. If so, sendcurrency will throw an error along with a specific command needed to zero the value before exporting the ID.

At block 67000 on vARRR, v1.2.2-4 and all PBaaS chains will begin clearing this condition as part of importing an ID. After that time, someone in the community may make pull request to remove the warning and failure on sendcurrency, which will no longer have a potential unintended consequence.

v1.2.2-4 Fixes an issue with Verus Desktop on Windows, which could sometimes result in the Verus daemon seeming to be closed when it was not. We believe this may have resulted in the need for some Windows users to bootstrap, even when Windows Update hadn’t directly rebooted their system.

v1.2.2-4 Enables adding VRSC as a vARRR currency or vARRR as a Verus currency in Verus Desktop and has UI improvements for defi functions

I've been watching VRSC for quite a while now but have rarely visited this thread.  The only thing I see here are frequent announcements about wallet upgrades and this new Pure thing that sounds very complicated....just like the functions of Veruscoin itself.  Since it seems like nobody else is commenting here, I have to wonder if anyone is actually using any of these unique functions or if they're basically a solution to a problem that doesn't exist.  If I had to guess, it'd be the latter.

Aside from that, I'm kind of surprised this coin hasn't caught on more so than it has since you can mine it with a friggin' toaster if there were a circuit board inside it.  I've seen neat videos of Android mining farms and such, and aside from the fact that there are thousands of altcoins on the market I don't know what's holding it back.

Announcing Verus v1.2.2-3 - MANDATORY UPDATE FOR vARRR MAINNET, HIGHLY RECOMMENDED FOR ALL SERVICE NODE OPERATORS AND VERUS MAINNET

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

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

vARRR NODES MUST UPGRADE TO v1.2.2-3 BY HEIGHT 18250 ON vARRR TO REMAIN PROPERLY CONNECTED TO THE MAIN vARRR NETWORK AS CROSS-CHAIN TRAFFIC FROM VRSC->vARRR IS THEN CLEARED BY CONSENSUS. FUTURE PBaaS CHAINS SHOULD USE v1.2.2-3 OR LATER TO LAUNCH.

THE vARRR COMMUNITY MAY ALSO CHOOSE TO INITIATE EARLY ACTIVATION BY ORACLE IF PEOPLE UPGRADE QUICKLY AND THEY WOULD LIKE TO DO SO

v1.2.2-3 also includes a new default for RPC commands on all chains related to adding files to on-chain data. In the default case, signdata, sendcurrency, and updateidentity will not allow encryption of files from disk unless the daemon was started with -enablefileencryption=1. In addition, if the daemon is started with -enablefileencryption=0, files will not be able to be even hashed for use with the signdata API.

v1.2.2-3 fixes a failure to create a transaction for the “makeoffer” command if the funds destination is a z-address and there is no memo present.

Announcing Verus v1.2.2-2 - MANDATORY UPDATE FOR MAINNET UPGRADE TO v1.2.2-2 OR LATER ON VERUS MAINNET BEFORE BLOCK 3000000 (approximately Wed 10 Apr 2024 4 PM UTC, Wed 10 Apr 2024 9 AM PDT) TO REMAIN PROPERLY CONNECTED TO THE VERUS BLOCKCHAIN AS vARRR CONNECTS FOR CROSS-CHAIN OPERATION WITH VERUS ALL BLOCK MINERS AND STAKERS SHOULD UPGRADE ASAP TO INITIATE A PREPARATORY SOFT FORK AND ENSURE THE SMOOTHEST OVERALL NETWORK UPGRADE POSSIBLE

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

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

vARRR is running smoothly, and all distributions from launch were quickly and properly completed by the chain. It is notarizing properly on its own chain, able to launch its own currencies and able to work with all the currencies already imported from Verus in block 1 to the vARRR chain. As everyone using it has probably noticed, there is still an issue.

A few years ago, a decision was made to incorporate VerusIDs with their attached data into block one instead of without their data, which is the standard procedure for normal VerusID exports. This was done to allow initial oracle behavior to affect block 1, if necessary, which it has never been. This process involves transferring the VerusIDs through JSON during the creation and also the PBaaS chain’s validation of block 1. In this specific launch, one of those VerusIDs contained an unusual VDXF object.

Additionally, there was an issue with the JSON output of this particular type of VDXF object; it deserialized slightly differently than it serialized. Consequently, a VerusID included in the coinbase of vARRR block 1 had slightly different data than the corresponding data on the Verus chain. This discrepancy means that when Verus adheres to the cross-chain protocol for validating the first notarization back to Verus, it rejects vARRR block one due to the data mismatch. This is the same rejection that would safeguard against any kind of change to the specified behavior or distributions. Verus will reject cross-notarization until the Verus network as a whole makes an exception for vARRR, and v1.2.2-2 includes that exception.

Of course, in preparing this release, we also addressed each fundamental point of learning, from deciding not to retain ID data on launch IDs to fixing the JSON serialization of the VDXF object in question. Since the Verus PBaaS networks are networks of people, we need to give some amount of reasonable time, commensurate with the time importance of the change required for everyone to upgrade their nodes and have solid consensus. As a community, we have tools, like decentralized oracles and other network capabilities, which we will employ to allow for a straightforward, non-bootstrap upgrade process, even for those who are unable to upgrade before activation. All that said, WE DO NEED MAXIMUM PARTICIPATION. We have a supportive, large community, and we hope all block validators and most network nodes in general upgrade as soon as possible to help activate a preparatory soft-fork, locking in the vARRR chain for acceptance when the full upgrade activates at block 3,000,000. There are no other changes in v1.2.2-2 besides a resolution for the cross-notarization from vARRR to initiate smooth, and fully functional cross-chain protocols.

Until then, please support the vARRR network and community by merge-mining and continuing to cross-notarize onto the vARRR chain, strengthening its security and keeping it ready to connect when we reach block 3,000,000. Once that block is reached, cross-chain transactions on CLI, desktop, and mobile should proceed as expected, and all funds currently sent and waiting for notarization should arrive.

Another update! Verus v1.2.2-2.
This is a nice active project.

Announcing Verus v1.2.2-1 - MANDATORY UPDATE FOR MAINNET AND TO PARTICIPATE IN vARRR LAUNCH UPGRADE TO v1.2.2-1 OR LATER ON VERUS MAINNET BEFORE BLOCK 3019000 (about 3 weeks from now) TO REMAIN PROPERLY CONNECTED TO THE VERUS BLOCKCHAIN AS FUTURE LAUNCHES TAKE PLACE UPGRADE IMMEDIATELY TO PARTICIPATE IN THE vARRR HISTORICAL FIRST PBaaS CHAIN LAUNCH ON THE VERUS NETWORK. v1.2.2-1

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

(testnet specific releases to follow)

This build enables successful launch of the vARRR blockchain and merge mining / staking along with Verus on mainnet. By enabling the inaugural PBaaS chain launch, this release paves the way for any organization, project, or application to launch their own blockchain on the unlimited scale, multichain Verus network. Based on the activation of launch improvements, we do recommend that new token or chain launches wait for block 3019000 to launch their currencies on the Verus network. The issue in v1.2.2 that prevented acceptance of vARRR’s first block was one launch validation check that was taking the correct path only for testnet and was not caught in all the years of testing. The block was being made correctly, but would inevitably fail validation. This has been addressed as well as a few small improvements made.

We also found some launch behavior that was undesired, but not critical to the final outcome. We would prefer it to be improved in future launches from the Verus blockchain. The related changes will take effect at block 1 of the vARRR blockchain and block 3019000 of Verus mainnet. This version also includes better lite node change support for mobile, addressed in a previous announcement, coverage of some estimateconversion usage that would previously fail and some minor sync issues for any PBaaS mainnet that could make sync slower in some network edge cases.

As of this announcement, the master source trees are fully up to date for building by those who self-build. As soon as you are running v1.2.2-1, you will be able to start merge mining and eventually staking vARRR, maybe even get the first block, and participate in the first PBaaS chain launch from Verus mainnet!

Announcing Verus v1.2.2 - CRITICAL UPGRADE FOR MAINNET AND TESTNET

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

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

v1.2.2 will no longer connect to the existing testnet, as we are starting a new one with an Ethereum bridge to Sepolia, which will also be more similar to mainnet in its currencies. There will be an announcement when the new testnet is available, hopefully within the next 24 hours.

This update includes the new Verus Storage API. Additionally, v1.2.2 fixes an issue discovered with version 1.2.1-1, which introduced a problem that can cause a node to behave as if it was not yet fully in sync, even though it may be up to date with the chain tip. For this reason, we consider v1.2.2 critical for all users. Please update as soon as possible. The new Verus Storage capabilities introduced in 1.2.2 bring z-address privacy technology to data, enabling each of us to regain control over our identity and content. In doing so, Verus Storage introduces a better way for both humanity and AI to store, access, and relate to information.

With Verus Storage, every PBaaS chain immediately offers a fee-based storage capability for indexed data on the blockchain. Every PBaaS blockchain will have its specific price for storage, ultimately controlled by miners and stakers and defaulting to about 0.01 of the native coin for permanent storage of 1KB of data. All stored data is encrypted by default, and if no encryption is specified, that simply means the decryption keys will be published on-chain.

This first version of Verus Storage is great for small to medium size data that you believe is worth storing permanently, as it’s limited to a maximum on-chain size of 999,999 bytes. Verus Storage is incredibly versatile, and can be used for VerusID PFPs, HTML content, license agreements, documents. Personally, I will feel comfortable using it for my own data, and even encrypted key storage. Any information you put on-chain is always available to you anywhere you go, as long as you have an internet connection and your 24-word seed phrase. All data stored is either sent as part of a private transaction or added to an ID you control, using the “data'' option.

Encryption is done using the well known ChaCha20-Poly1305 (https://en.wikipedia.org/wiki/ChaCha20-Poly1305) encryption algorithm, with key exchange using Sapling private target addresses and random keys that can be recreated by the viewing key of the target private address. All data is encrypted. Even “public”, published data with no private address target is encrypted to a randomly generated and discarded Sapling address, and the necessary viewing key is then stored along with an indexed link into the publishing VerusID. Since each separate object in a collection of data is encrypted with a different key, all of which may be recreated with a single viewing key, the API enables sharing access to each individual item without ever requiring the master viewing key of the collection itself to be shared.

Verus Storage is built using the existing, extensive functionality of the Verus network, and thus comes into effect as of 1.2.2 with no protocol change or fork. Block producers that upgrade will immediately start accepting data transactions into blocks, which are protocol compliant. That means that after upgrading, data can easily be attached to both private transaction messages and VerusIDs on any PBaaS chain and easily linked cross-chain as well, making it easy to create private/semi-private/public chat groups, share multiple forms of data, and post data publicly or privately on any PBaaS blockchain. Applications can use this new capability to store application data and expose its features in whatever way is best for their users.

Data can be easily stored and accessed across all PBaaS blockchains, even in parallel (ie. data sharding) by those with the keys to do so, introducing a market for permanent storage at scale that every PBaaS chain can compete in or price themselves out of, depending on network, project and community goals. Verus Storage capabilities lay a foundation for PBaaS chain projects with economics designed around advanced storage capabilities, applications and markets.

While the initial target usage is for small to medium sized data at scale, the Verus PBaaS protocol does not have any inherent scale limit across a network of chains, and over time, this protocol, or its evolution, could be used to store and access all of humanity’s digital, privacy-enabled, self-sovereign data over archaeological time scales. As a chain grows, along with its storage requirements, nodes that offer full data access services to any application clients across many chains will likely start offering users or applications access to VerusD-RPC APIs and many chains of data at prices that, due to permissionless competition and provable results, should stabilize to cover a reasonable margin over costs of serving the data. Since offering these kinds of services can also be a provably user rated, peer to peer low cost and high availability content delivery network at scale, we may expect indefinite high availability of stored data, independent of any company or organization, and self-sustaining storage and delivery economics. As this capability is used and evolves, VerusIDs, along with payments and authentication that they enable can be easily used for bandwidth-based micro-payments at a fair cost for node operators, users, and application providers.

Verus PBaaS storage provides permanent, encrypted data storage with high availability and selectively disclosed data collections on any PBaaS blockchain. The blockchain archive will always contain any data that was stored using this API, now and in the future, without requiring rent or a corporate host, and is built on an economic model that supports its continued availability, even as storage technologies evolve.

For now, we expect the encrypted storage capabilities to be used for minting collections, surprise reveals, VerusID profiles, private KYC services, private messages, contracts, and real world asset bindings. With the unlimited scale of a multi-chain PBaaS internet, PBaaS data storage has the potential to provide permanent, self-sovereign, and private data storage for all.





         

Pirate Chain on Verus!!!!!!!!!
Announcing the launch of the vARRR Mainnet, marking a significant milestone in advancing the Pirate & Verus ecosystem. With the introduction of the Bridge.vARRR currency, we're opening up exciting new avenues for seamless cross-chain interactions.

https://medium.com/veruscoin/introducing-pure-the-currency-100-backed-by-verus-bitcoin-d07033be15ac

Introducing Pure — The Currency 100% Backed by Verus & Bitcoin
Pure is a decentralized currency fully backed by Verus (VRSC) & Bitcoin (tBTC). Hold Pure to be exposed to both Verus and Bitcoin while accruing fees from conversions. Or use it to convert from tBTC to VRSC and vice versa.

Pure launch block: 2,975,703 (Sunday 24 March, 2024).
✅ Start preconverting to Pure now for an 8 day period. Read further to learn how.
❓ tBTC is BTC on the Ethereum network. Threshold.network supplies a decentralized bridge for users to bridge BTC to Ethereum. tBTC is also bridged to Verus.
⌨️ Join the Verus Discord and type in /pure to see how much is in the reserves, the Pure supply & its protocol prices.

What is Pure?

Pure is a decentralized currency launched on the Verus blockchain. It is fully backed by its reserves: Verus (VRSC) and Bitcoin (tBTC), with a reserve ratio of 50/50%.

The currency is called Pure because it aligns with the true ideals of decentralization and transparency:

    Bitcoin and Verus are fully decentralized and controlled by its nodes and block producers. No single entity or company controls them. They are not a business — they are rent-free protocols.
    Bitcoin and Verus had fair launches. No ICO, no premine and no developer fees or taxes.
    Bitcoin and Verus have a limited supply.
    Bitcoin and Verus are censorship-resistant.

Hold Pure to be exposed to two decentralized cryptocurrencies upholding true cypherpunk values.

Another benefit of holding Pure is that the currency accrues conversion fees. When users convert from Pure to VRSC or tBTC (or vice versa) they pay a conversion fee of 0.025%. When users convert between VRSC and tBTC they pay a conversion fee of 0.05%.

Half of those conversion fees (50%) stay in the Pure reserves, increasing the value of Pure since no new Pure is minted. The conversions are MEV-resistant and verified by the miners and stakers of the protocol. Learn more about Verus DeFi.

Conversions between VRSC and tBTC are only possible after the preconversion period has ended on Sunday 24 March, 2024. From now on you can only add VRSC and tBTC into the reserves of Pure.

Users can also create subIDs which cost 0.00021 tBTC.vETH (in Pure). These costs are burned reducing Pure in circulation. Learn more about VerusID and what you can do with it here. If users create an identity with your subID as referral, they pay 2/3 less — you get 1/3 and 1/3 is discounted.
What is the preconversion period?

The preconversion period is an 8 day period in which users can fund the reserves of Pure with VRSC and tBTC. Depending on how much they added they will get their fair share of the 20,000 Pure after the 8day period.

The initial supply of Pure is 20,000. After the initial supply has been distributed by the protocol, the supply is dynamic. When users convert from VRSC or tBTC into Pure, Pure is minted. When people convert from Pure back to VRSC or tBTC, the Pure is burned.
What is tBTC, how do I get it & bridge it to Verus?

tBTC is BTC on the Ethereum network. The decentralized bridge between Bitcoin and Ethereum is supplied by the Threshold Network.

    Existing solutions that bridge Bitcoin to Ethereum require users to send their Bitcoin to an intermediary, in exchange for an ERC-20 token that represents the original asset. This centralized model requires you to trust a third party and is susceptible to censorship, threatening the premise of Bitcoin as sovereign, secure, permissionless digital asset.

    The second generation of tBTC is a truly decentralized (and scalable) bridge between Bitcoin and Ethereum. It provides Bitcoin holders secure and open access to the broader DeFi ecosystem. tBTC v2 allows you to unlock your Bitcoin’s value to borrow and lend, mint stablecoins, provide liquidity, and much more.

Get tBTC on Kraken, Uniswap, Curve & others. Or mint it yourself

tBTC token address: https://etherscan.io/token/0x18084fba666a33d37592fa2633fd49a74dd93a88

You can send tBTC to your MetaMask wallet or Verus Mobile first, and later you have to bridge it to the Verus blockchain. Bridging is done through the non-custodial Verus-Ethereum Bridge
Adding tBTC ERC-20 to Verus Mobile

Here is a guide to add the tBTC ERC-20 to Verus Mobile:

    Press the plus-button bottom-right corner
    Press “Add ERC-20 Token”
    Select checkmark to “Find using mapped PBaaS currency”, and fill in “tbtc.veth”, then press Continue
    Press OK when a warning screen pops up.

You have added the tBTC ERC-20 in Verus Mobile and are now ready to receive it.
Bridging tBTC to the Verus blockchain

You have to bridge the ERC-20 tBTC over to the Verus blockchain with the bridge website or with Verus Mobile to participate in the preconversion period.

🔔 It costs a considerable amount to bridge over to Verus. The Ethereum blockchain is quite congested and transactions are expensive because of it. Bridging costs estimation: when ETH is @ $3900 and the gas is at 60 gwei, you pay around $150 to bridge tBTC over to Verus. It can take up to 60 minutes before the tBTC arrives on the Verus blockchain.

Let’s start how to bridge with MetaMask and the Verus-Ethereum Bridge website: https://eth.verusbridge.io/

    Connect MetaMask with this website: https://eth.verusbridge.io/
    Address: where you want the tBTC to end up on the Verus blockchain
    Token: select “[tBTC v2] as tBTC.vETH”
    Destination: select “[tBTC v2] as tBTC.vETH on VRSC”
    Choose the amount you want to bridge over
    If you use Verus Desktop don’t forget to add tBTC.vETH in the “Multiverse”-tab!

You can also bridge with Verus Mobile.

First let’s add tBTC.vETH to your Verus Mobile wallet:

    Press the plus-button bottom-right corner
    Press “Add PBaaS currency”
    Enter “tbtc.veth” and press continue
    Press “ADD”

Now let’s bridge the tBTC ERC-20 over to the Verus blockchain.

    Press tBTC v2
    Press “Send” and then “Convert or cross-chain”
    Press “Send off-chain”
    As the recipient address fill in a Verus address you own (R- or i-address, or VerusID)
    Fill in the amount you want to send
    Then as “Select network to send to” choose Verus
    Then as “Select currency to receive as” choose tBTC.vETH

Now you can safely bridge the tBTC over.

So now that you’ve bridged tBTC over to Verus either on Verus Mobile or Verus Desktop, it’s time to preconvert.
How do I preconvert to Pure?

When you preconvert you put tBTC.vETH or VRSC in the reserves of Pure. After the 8 day preconversion period you receive an amount of the 20,000 Pure, distributed by the protocol.

You can preconvert with Verus Desktop and Verus Mobile.
Preconvert with Verus Desktop

On Verus Desktop click the “Convert Currencies”-button and then go to the “Advanced”-tab.

    Choose amount to send (tBTC.vETH or VRSC)
    “From Currency”: fill in tBTC.vETH or VRSC
    “To Currency”: fill in Pure
    “Destination Address”: fill in a R-/i-address or VerusID where you want to receive Pure
    Check the box: “Send as pre-convert”
    “Refund Address”: Sometimes a currency has a minimum or maximum amount to preconvert before it launches. For example, when the minimum preconversion amount is not met, and thus the currency not launched, you will receive your funds back. In this case there isn’t a minimum or maximum but you still need to fill it in. Can be the same as your Destination Address.
    Now click “Convert Currencies”, and that’s it! You have now added a currency into the reserves of Pure and have to wait until Pure is out of the preconversion period.

Preconvert with Verus Mobile

    Press tBTC.vETH or VRSC
    Press “Send” and then “Convert or cross-chain”
    Press “Preconvert”
    As the recipient address fill in a Verus address you own (R- or i-address, or VerusID)
    Fill in the amount you want to preconvert
    Then as “Select currency to preconvert to” choose Pure
    The network to send to is Verus
    Now press “Send” and confirm, and that’s it! You have now added a currency into the reserves of Pure and have to wait until Pure is out of the preconversion period.

Now that you have preconverted tBTC or VRSC into the reserves of Pure, all you have to do is wait for the preconversion period to be over. When that time has come you will receive Pure in your wallet.

Once you have received Pure into your wallet you can always convert it back to VRSC or tBTC.
Join the crypto revolution with Verus & Pure

Pure is a unique currency backed fully by VRSC and tBTC, launched on the Verus Protocol. Join the Verus Discord and explore what Verus has to offer!

    Verus solves scalability by neither sacrificing decentralization or security
    The Verus-Ethereum Bridge is non-custodial & trustless
    Launch currencies (like Pure!) without any coding needed
    Launch fully interoperable, independent and customizable PBaaS-blockchains
    VerusID: self-sovereign identities
    Verus DeFi: simple, low-cost, MEV-resistant and without any middleman
    Verus is the protocol for builders: join the community at Consensus 2024

And so much more.
Join the community. Learn about the protocol. Use Verus. Get ahead of the game.

http://www.verus.io/discord

https://twitter.com/VerusCoin

http://www.verus.io/

Announcing Verus v1.2.1-1 - NON-MANDATORY, RECOMMENDED UPGRADE, CRITICAL TO USE FOR DEFINING NEW CURRENCIES OR BLOCKCHAINS

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

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

This release resolves an issue preventing a currency's start block from being set past a currency definition's expiry height.
V1.2.1-1 also Improves blockchain sync speed and reduced download traffic during initial block download.

What's New:
1) Improved initial block download speed and traffic.
2) Improved data cleanup on shutdown

In addition, v1.2.1-1 also has some technology preview features for a new data signing with encryption capability. There will be more details on these new features in an upcoming release when they are more complete.