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

for miketout on discord

Today, I noticed that there was a challenge of a notarization between vARRR and Verus. This was caused by a small reorg on the vARRR chain. As per the protocol, vARRR now needs to prove to the Verus chain that new notarizations are on the correct and most powerful chain for Verus to accept the cross chain notarization. While complete protocol function in challenge cases was tested for years on testnet, we have discovered a check that will treat the protocol differently, depending on the protocol version expected, based on block height. Unfortunately, the block height checked as a threshold is in error, and a vARRR block height is being checked against a Verus block height, which did work in all cases on testnet, but on mainnet is resulting in the proof being rejected. Until this is fixed, which is simple and in progress, but will require a protocol change on Verus, cross chain sends from vARRR to Verus are stalled. The other direction will soon pause as well until this is resolved. We hope to have a version out ASAP with a resolution and a target date for the update to take place. Our current target is a one week upgrade activation with the potential to activate it earlier if the community decides.

Announcing Verus v1.2.3-4 - CRITICAL UPDATE FOR MINERS OR STAKERS ON ALL CHAINS, HIGHLY RECOMMENDED FOR ALL USERS

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

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

Verus v1.2.3-4 addresses an issue that can permit transactions to enter default miner and staker mempools, even if those transactions have underpaid certain expected fees.

This version ensures that miners and stakers will properly enforce the limits for underpaid transactions. It does not have protocol changes.

New CLI command and RPC API in v1.2.3-4 In v1.2.3-4, it is now possible to send an array of conversions, instead of just one, to the estimateconversion CLI command, requesting estimates on multiple different conversions over a single currency basket to be simultaneously solved. This makes it easy for those who might participate in arbitrage or balancing of baskets to determine an estimated set of conversions on a multicurrency basket that would result in a specific rebalancing outcome.

We recommend that miners, stakers, and witnesses update as soon as possible and that everyone else updates when convenient.

This is a PSA. If you use the Testflight "Verus Wallet" on iPhone, it will be removed from Testflight in 3 days from now. If you have any keys in the Testflight Wallet, please take a few moments to save them and/or get them moved over to the main iOS App Store "Verus Mobile" wallet.

Announcing Verus v1.2.3-3 - HIGHLY RECOMMENDED UPDATE FOR MAINNET VERUS, vARRR, AND TESTNET - IMPROVED MERGE-MINING AND MERGE-STAKING PERFORMANCE AND NEW AGGREGATED VOLUME AND BASKET DATA IN RPC & CLI WE HIGHLY RECOMMEND THIS UPDATE FOR ALL BLOCK PRODUCERS, POOLS, EXCHANGES, INFRASTRUCTURE SERVERS, AND WITNESSES

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

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

What’s new in v1.2.3-3?
1) Enables the GUI to select significantly more memory efficient operation or fast loading and remembers the user setting. Defaults to fast loading.
2) Improves the connection between nodes for merge mining or staking, which may result in more efficient merge mining and staking.
3) Supports a new parameter and function on the getcurrencystate command or RPC call. This parameter is the currency to use for calculating volume, and if present, the API can be used to calculate and return volumes between any currencies in a basket calculated in any currency that may also be in the basket, or the basket itself. This should provide all the data aggregation needed, using import information, for people to make these available as basket data feeds to coinpaprika.com or other aggregators and for developers to have an easier time making Verus DeFi APIs, dashboards, or tools.

We recommend this update for everyone and recommend updating as soon as you are able to do so.

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!