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

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.

Announcing Verus Mobile v1.0.8, released on Android Play and iOS App stores!

Make sure to get your free, self-sovereign VerusID, sponsored by Valu/Arketyp and the ValuVerse while you can!

New Feature Highlights
VerusID provisioning and registration under application control with easy onboarding and
VerusPay universal invoices received by the vendor in any selected currency and payable through conversions from any selected source!

Now that v1.0.8 is available, mods will open public access to the ⁠valuverse channel just after tomorrow's meeting, where everyone who gets approved on Discord can register one free, on-chain VerusID with a [name].valuid@ name of your choice (first come, first serve). This is not just a company owned ID, it is an actual blockchain asset registered courtesy of Valu & @Consilience for onboarding to the ValuVerse. Some long time contributors will get earlier access to the channel, as this is a company actually sponsoring these self-sovereign IDs for everyone. Unlike some app account, your new VerusID will be fully self-sovereign, permanently owned by you unless you transfer / sell it to someone, and can be used as your VerusID or backup and also your login to the new ValuVerse, metaverse 3D social world. You can login to the ValuVerse with any VerusID, new or pre-existing, that is registered on the Verus blockchain and linked to your Verus Mobile profile. With this easy onboarding, anyone with a phone can join during the promotional period, which is expected to be 1 or 2 months and can end at any time, and drop into the ValuVerse for an engaging, new social experience, soon with commerce and integration with the on-chain marketplace.

Getting your new *.valuid@ VerusID is easy to do. First, make sure to upgrade your Verus Mobile wallet to 1.0.8 in the App or Play store. Then, go the the ⁠valuverse channel, when it is available to you, and enter /getid. You will be shown a QR code, scan that with Verus Mobile's scan, and you will be led through the process of choosing a name, registering, and linking your ID to your mobile profile.

Once you have an ID linked to your mobile profile:
head over to the ValuVerse at this link https://live.valuverse.net/
login with the QR code you see there, and
setup your avatar.

It's that simple!

Announcing Verus v1.2.1 - NON-MANDATORY, RECOMMENDED UPGRADE, CRITICAL FOR CROSS-CHAIN WITNESSES TO UPGRADE BEFORE BLOCK 2930000


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

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

What’s new:
1) Added `expiryheight` option to the `definecurrency` API to facilitate easier multi-signature currency definitions.
2) Minor documentation update for `definecurrency`
3) Fixed queries for prelaunch currencies to return only currencies in active pre-launch.
4) Zero value UTXOs are now skipped when funding a transaction.

There are no protocol or other changes for v1.2.1

Scalability, Decentralization & Security — What Trilemma?

The blockchain trilemma is a classic idea that truly decentralized blockchains need to choose between security or scalability. Verus offers a different perspective and a new approach. Together we will come to the conclusion that the Verus Protocol solves scalability by neither sacrificing decentralization or security, effectively solving the trilemma.

Read up on medium.

https://medium.com/veruscoin/scalability-decentralization-security-what-trilemma-8d2d6869924d

Announcing Verus v1.2.0-2 - MANDATORY UPDATE FOR MAINNET AND TESTNET IN PREPARATION FOR PBaaS CHAIN LAUNCH IT IS IMPORTANT TO BE UPGRADED TO VERSION 1.2.0-2 BEFORE THE ACTIVATION (NOT NECESSARILY DEFINITION) OF A NEW PBaaS CHAIN ON MAINNET!

CLI RELEASE: https://github.com/VerusCoin/VerusCoin/releases/tag/v1.2.0-2

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

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

What’s new?

1) Additional parameter parsing fix for getcurrencyconverters when used from the GUI desktop or upcoming release of Verus Mobile

2) Smooths a very rare conflict case that can occur in a degenerate situation combined with cross-chain PBaaS notarization. If you are not updated and this degenerate case occurs on a launched and active PBaaS chain, you may fork from the network.

3) This release now includes bootstrap capabilities for testnet in addition to the normal bootstrap capabilities for mainnet. There are no protocol or other changes for v1.2.0-2. All systems go, and we are now ready for some upcoming PBaaS launches

So let’s all upgrade and go!

Announcing Verus v1.2.0-1 - NON-MANDATORY UPDATE RECOMMENDED FOR MINERS AND STAKERS ON MAINNET AND TESTNET

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

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

What’s new?
1) Fixes parameter parsing for getcurrencyconverters when used from the GUI desktop or upcoming release of Verus Mobile
2) Fixes a very rare potential seg-fault that can happen in cases of validating and running bridgekeeper
3) Enables an optional `-arbitragecurrencies` parameter for starting the daemon that may be easier to use when starting on Windows and adds both `-arbitragecurrencies` and `-arbitrageaddress` parameters to verusd help

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

Announcing Verus v1.2.0 - MANDATORY FEATURE UPDATE (AUTO-ARBITRAGE FOR MINERS AND STAKERS) FOR MAINNET AND TESTNET UPGRADE TO v1.2.0 OR LATER IS MANDATORY FOR ALL NEW PBAAS CHAIN LAUNCHES AND CONTINUED NETWORK SYNCHRONIZATION BY THE FOLLOWING BLOCK/TIME:

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

MAINNET: Block 2873057, estimated on Wed 10 Jan 2024 18:00:00 UTC TESTNET: Block 350468, estimated on Fri 29 Dec 2023 18:00:00 UTC Happy Holidays from everyone involved in this release to all the Verus Community!

What’s new?

1) A protocol change to enable auto-arbitrage and basic support for auto-arbitrage that uses the on-chain P2P marketplace of limit orders to crowdsource liquidity for Verus DeFi liquidity baskets.

2) Will not allow you to post an offer for an ID that cannot be accepted due to not including all necessary signatures from revocation and recovery authorities or having tokenized ID control (in that case, you must make an offer for the token).

3) Fixes a rare potential segfault that can happen in cases of validating with specific transactions that were once valid and later become invalid.

Auto-arbitrage Feature Discussion As most in the community know, Verus DeFi solves all transactions in any liquidity basket that are mined into one or more blocks simultaneously, ensuring that all conversions get exactly the same fair price as everyone else in the same one or more blocks without enabling miners or stakers to get preferred pricing at the expense of those converting (referred to on all other protocols, none of which solved this issue by a simultaneous solution, as MEV). Verus is the first system to solve MEV in either TradFi or DeFi to our knowledge, being the first actual decentralized finance where all operations are enforced in the L1 consensus layer, not in various programs deployed by and sending rent to centralized app teams or companies.

At the same time, the Verus DeFi protocol still enables people using it to engage in beneficial arbitrage, joining bundles of transactions, not front-running or sandwiching, to keep the conversion rates consistent with other on-chain markets and baskets, markets on PBaaS or external chains, and even off-chain centralized markets.

Typically, arbitraging between any two markets entails some amount of risk to the arbitrager, since it is generally impossible to know that both sides of an arbitrage operation, for example a buy in one market and a sell in another, will actually take place when orders must be placed independently. In most cryptocurrency networks, centralized teams deploy and extract rent from smart contracts that are basically programs running on a shared, decentralized computer and referred to as “DeFi”.

These networks typically enable advanced developers to engage in parasitic MEV and adopt a complex consensus model to reduce or eliminate the risk to such advanced developers by enabling what they call separated, centralized “block building” services, where the MEV exploiters can build entire blocks with all transactions to reduce or eliminate their risk when taking money from the people using those apps by ensuring they can front-run, back-run, or sandwich transactions.

This has created competition among these exploiters where they now sometimes return some of the funds earned from MEV to the users they take it from or liquidity providers, thereby claiming that they “solve” MEV by not taking all of the MEV in all cases.

As we already know, Verus is different and built as a fair, rent-free protocol that is good for users and liquidity providers by preventing this exploitative MEV. With the new auto-arbitrage capability in Verus 1.2.0, Verus miners and stakers can still earn by arbitraging liquidity baskets that may be out of balance, not by front running, back running, or sandwiching transactions, but by joining transaction bundles to be solved simultaneously, helping to bring rates into balance and earning, while helping users AND liquidity providers in the process. In addition to the automated liquidity baskets, Verus also has an on-chain peer-to-peer marketplace where people can make and/or accept limit offers for either VerusIDs or even any currency across the entire ecosystem or sent to the Verus network from Ethereum or other external networks in the future.

When running the auto-arbitrage feature and building a block on any Verus mining or staking node, the Verus daemon itself will look for opportunities to “fill” on-chain offers of one currency for another at a limit price better than the conversion rate of a liquidity basket. If any such offers are found, and if the validator has enough funds in their local wallet to fill such an offer, the daemon will both fill the offer and run the resulting output currency into the liquidity basket being solved, joining all of the other transactions in that simultaneous solve, filling the on-chain limit order, bringing the liquidity basket price closer to the global fair price, and ensuring additional earnings for the miner or staker, if they win that block.

While this is just the beginning of what is possible with more advanced auto-arbitrage and will only choose to leverage the single most profitable on-chain limit order when solving a basket, it proves out a new form of beneficial arbitrage in the Verus DeFi protocol and provides a fully open source, 100% decentralized and rent-free way for validators to earn, while bringing all prices for everyone closer to a globally common, fair price for all assets.

To our knowledge, this is the only system to ever achieve such a fair, dynamic arbitrage model in any version of TradFi, AppFi called “DeFi”, or actual DeFi at the consensus level. There is certainly more that advanced programmers could do with time, effort, and this protocol, but we hope you enjoy and benefit from this world’s first MEV-resistant automated arbitrage capability.

Announcing Verus v1.1.2-3 - NON-MANDATORY FEATURE UPDATE FOR MAINNET AND TESTNET

There are no protocol changes in v1.1.2-3.

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

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

What’s new? v1.1.2-3 includes new capabilities for the getcurrencyconverters command and API that prepares for VerusPay and its QR codes and deep links in Verus Mobile and other clients to become an unlimited scale, permissionless, worldwide universal currency and DeFi payment protocol. V1.1.2-3 also improves accuracy of estimateconversion.

How does it work? In addition to its prior function of finding baskets that contain all currencies in a given list, getcurrencyconverters now alternately accepts a JSON parameter with a “tocurrency” element and one or more “fromcurrency”s (see “help getcurrencyconverters” for details) with optional slippage and pricing limits. It will return all currencies that meet the requirements and which can be used to convert from any of the “from” list to the “to” currency.

Importantly, it will also return the most accurate estimated amount of the source currency needed to get the desired amount of output currency, assuming for this purpose that you are not joined by other conversion transactions. This is not the same as an up-to-the-minute estimate, which includes all pending conversions as well and which estimateconversion does provide, but it can be used as a proof point to ensure vendor acceptance when paying VerusPay invoices that allow conversions.

The new VerusPay QR code and deep link payment protocol, which is being worked on for the next feature release of Verus Mobile, enables a vendor to request that if the payee wants to pay in an alternate currency and convert to the vendor’s requested currency, the conversion must be routed through a converter with no more than a specified slippage.

This ensures that the transaction size for the item or service in question will not have a large impact on any liquidity basket used for converting to the vendor’s payment currency, safeguarding the vendor. It also allows the payee to select a currency source and route for payment that provides the best deal at that moment for them.

The more people simply use this for payments at unlimited scale worldwide in a decentralized way, the more it will also naturally arbitrage baskets across the network as people consistently choose their most favorable route to the payment currency. We believe that when the new feature release of Verus Mobile is out, VerusPay will be the first unlimited scale, universal currency, decentralized, rent-free and permissionless payment and conversion network in the world.

Announcing Verus v1.1.2-2 - RECOMMENDED NON-MANDATORY UPDATE FOR MAINNET MANDATORY FOR TESTNET AND WHEN RUNNING NEW PBAAS CHAINS TO ENABLE ALL PBAAS CURRENCIES TO BE EASILY SENT TO VERUS TESTNET ACTIVATION TIME: Tue 28 Nov 2023 10:40:00 PM PST)

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

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

Why this release?

This fixes an issue discovered on testnet where a PBaaS chain required explicit use of fee currency to send some currencies back to the Verus chain. v1.1.2-2 also extends the estimateconversion and getpendingtransfers API to include all pending transfers in the memory pool that may not yet have been mined into a block.

There are no protocol changes to VRSC or VRSCTEST itself, but v1.1.2-2 should be considered mandatory for running and merge mining a PBaaS chain when any are launched on mainnet or testnet.

Announcing Verus v1.1.2-1 - MANDATORY UPDATE WITH 2 WEEKS NOTICE FOR MAINNET AND ONE DAY NOTICE FOR TESTNET TO ENABLE USE OF Bridge.vETH AS RESERVE IN PBAAS CHAIN CONVERTER LAUNCH MAINNET ACTIVATION HEIGHT: 2824790 (~ Thu 07 Dec 2023 03:51:58 AM UTC) TESTNET ACTIVATION HEIGHT: 302170 (~ Fri 24 Nov 2023 07:54:12 PM UTC)

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

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

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

Why this release? There are blockchain projects planning to launch, including vARRR, that would like to use the Bridge.vETH currency as a reserve in their PBaaS chain converter basket, which launches with the blockchain.

When doing their dry run on testnet, it was determined that due to a unique characteristic of the Bridge.vETH basket, its use prevented proper mining of block #1 of the PBaaS chain, and though it is easily fixed for the PBaaS chain, the same issue will prevent the Verus blockchain from accepting a first notarization of a PBaaS chain that uses the Bridge.vETH currency as one of the reserves in its basket. v1.1.2-1 fixes this issue with a minor protocol modification that handles this reserve in launch properly, enabling coinbase in a first cross-chain notarization from such a blockchain to be properly verified by the mainnet or testnet VRSC chains.

As long as any blockchain converter basket that wishes to launch has a start block after the block heights above on the launch chain, it should launch just fine. If one has already been defined, for example the vARRR chain on testnet, it will be able to be launched and cross notarized after testnet activation of this fix, even if it had a start block before. Please update as soon as possible to enable any new blockchain bridge converter to use the Bridge.vETH currency as a reserve currency.

Announcing Verus v1.1.2 - CRITICAL UPDATE FOR ALL NETWORK VALIDATORS WITH IMPROVEMENTS PREPARING FOR ETHEREUM FEE SCALING, BETTER CONVERTER SELECTION FILTERS, BRIDGEKEEPER DISCONNECTION FIX, AND KMD IMPROVEMENTS SYNCED FROM UPSTREAM v1.1.2 IS BOTH CRITICAL FOR ALL STAKERS AND MINERS, AND IS HIGHLY RECOMMENDED FOR ALL USERS

Updated Bridgekeeper which can be used with the CLI is available at:https://github.com/VerusCoin/Verusbridgekeeper
incase of any errors do a
1. git checkout yard.lock
2. git pulll
3. yard install

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

v1.1.2 has the following improvements:
1) Sync and notarization improvements, as well as a number of places with improved error handling.
2) getcurrencyconverters API is now more selective in choosing converters based on up to the minute liquidity metrics.
3) GUI use of liquidity baskets has been improved both from the getcurrencyconverters improvement, and it has also been upgraded to use the “estimateconversion” API, which Verus Mobile users have found so useful due to more accurate conversion estimations.
4) getcurrencystate has fixed step selection when steps are not specified.
5) Bridgekeeper has more improvements in its handling of network connections to Infura, Alchemy, or Ethereum nodes in both GUI and CLI. The daemon is also more tolerant to configuration errors in the vETH config file.
6) v1.1.2 also prepares for an improvement in fee cost when sending back to Ethereum as traffic increases.