Announcing Verus v1.2.2 - CRITICAL UPGRADE FOR MAINNET AND 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.
General VerusId, Verus DeFI, and Public Blockchains as a Service (PBAAS) Capabilities
- On-chain Self Sovereign, Provable Identities, NFTs, and Individual or Organizational Profiles
- On-chain Launches of Token, Centralized Currency, and Liquidity Basket AMMs
- On-chain Launches and Merge Mining of Independent, Connected, Interoperable Blockchains without Programming
Verus ID and NFT Marketplace
Buy and sell VerusIDs on-chain, advertising your offer directly to the owner of an ID or NFT, or posting the sale of your NFT on the worldwide blockchain for all the world to see. Execute transactions in a completely decentralized way. Pay or offer to pay from a transparent or zero-knowledge private address, still auditable by you. Accept payment to either as well, and best of all, execute your transactions directly, peer-to-peer without any intermediary necessary. Don’t worry the on-chain model still makes room for owners to select and share proceeds with value added agents, marketing organizations, or other participants in a new economy of provable digital ownership. It’s the next step in the evolution of VerusID, the most powerful self-sovereign identity and secure storage model for funds in the digital world.
Verus Vault
With Verus Vault you can now protect funds on a VerusID, even from theft of a private key! If you lock your VerusID with Vault you cannot spend funds from that identity at all until it is again unlocked. While locked, you can still stake those same funds on the Verus network and earn by doing so. Of course, you can also still receive funds.
IT IS IMPORTANT TO NOTE THAT ENABLING REVOCATION, RECOVERY, AND ALL VERUS VAULT CAPABILITIES REQUIRE YOU TO HAVE ONE PRIMARY IDENTITY, AND AT LEAST ONE REVOCATION/RECOVERY ID CONFIGURED.
A locked VerusID can always be revoked and recovered by its revocation and recovery authority identities, which circumvents the lock. At the same time, anyone with only the primary keys, even a multisig of primary keys must first unlock, then wait for the predetermined unlock time before they can spend or access funds. This gives you, or maybe a company that specializes in watching the blockchain to whom you've assigned the revocation ID to revoke and recover whenever an unauthorized unlock occurs. That means that like a bank, setting a 24 hour unlock delay on your locked IDs actually provides the first decentralized solution to the infamous 5 dollar wrench attack.
In addition to a new level of blockchain protection and decentralized funds recovery, Verus Vault provides the same security for your IDs and NFTs as well as time locks for other purposes, such as vesting schedules, trusts, and inheritance. With Verus Vault, you can now protect and recover your funds, preserving all your assets and generational blockchain wealth from common forms of crypto loss or theft, no bank required.
New Verus Multicurrency, Multichain, DeFi Enabled Testnet
With an easy GUI for basic operations or command line for more advanced functions. Without any programming, you can now create new identities, currencies, liquidity pools, and blockchains for your business, your government, your projects, a worthy cause, your family, or your next decentralized application suite. Send currencies worldwide on the same chain, or across blockchains with ease. Even convert currencies to others on the network without an exchange by sending to yourself and converting along the way.
The new Verus testnet is a full-featured, intrinsically decentralized multi-chain blockchain platform with an unlimited number of identities, currencies, liquidity pools, and blockchains. It is accessible from the released versions of Verus Desktop and Verus CLI wallets, and it is the beginning of a new age in crypto. There are so many things you can do with Verus that you cannot with any other cryptocurrency platform, and you can try them all today.
As Verus PBaaS offers completely new capabilities that go beyond today’s decentralized platforms in many fundamental ways, the worldwide Verus community put its energy into creation, rather than convincing everyone that its capabilities are possible. Members across the Verus worldwide community have worked hard to make this all possible, and we are more than excited that you can now experience it firsthand. If you have an interest in the future of crypto, you owe it to yourself to learn about Verus, an unlimited scale, decentralized future with truth and privacy for all.
The Verus testnet, available in the Verus Desktop or cli wallets as the VRSCTEST coin, has the following capabilities, which to our knowledge are unique in crypto today.
Self sovereign, revocable, recoverable identities (currently on mainnet) VerusID
- Enables permissionless registration of friendly name strong identities and funds addresses that are simultaneously fully self-sovereign, revocable, and recoverable.
Staking-capable time locking and theft prevention (Verus Vault)
- Enables identities to be locked, preventing any funds under their control from being spent while locked, but still allowing seamless staking of funds. When locked, a user specifies an unlock delay, typically long enough to notice when someone who might have compromised a user’s keys would have to unlock the ID before spending. The only way to circumvent the unlock delay is to revoke and recover an ID. Users may also choose to create and use fresh private keys when unlocking an ID as well. This enables virtually theft proof workflow and a solution to inheritance, trusts, vesting schedules, the 5$ wrench attack, and identity theft. IDs may be used as friendly name cryptocurrency addresses for all currencies on all Verus PBaaS blockchains in the Verus network. The VerusID protocol is a protocol, which can also be implemented on non-Verus systems.
Multi-currency, user created, decentralized tokens and merge-mineable, interoperable blockchains without programming
- Enables any user with an ID to create their own token currency or even full fledged, multi-currency, ID-issuing 50% POW/50% POS, 51% hash attack resistant blockchain that can send and receive from the Verus chain which launched it. All PBaaS chains run from the same daemon, and projects may choose to join the worldwide Verus community in improving the daemon. In doing so, they will start with a complete, multi-currency, ID-capable blockchain with DeFi capabilities that is merge-mineable and stakeable with other blockchains in the Verus network.
Consensus integrated DeFi liquidity pools and fractional currency baskets
- Any ID owner may define Verus DeFi fractional basket currencies with one or more asset currencies backing the liquidity pool at a fractional percentage ranging from 5% to 100% backing. The Verus DeFi protocol ensures that all currency conversions that use a particular liquidity pool and are mined into one block are solved and priced simultaneously, addressing the problems of miner extracted value (MEV) and front-running, while providing fee-based DeFi integrated incentives to miners and stakers, ensuring smooth consensus operation and fee conversion capabilities by integrating DeFi liquidity pools directly into the consensus and cross-chain bridge protocols.
Simultaneous blockchain and blockchain liquidity pool launches
- Launch of a world class, worldwide, merge-mineable blockchain along with a fully decentralized or centralized “bridge” converter liquidity pool as part of defining a new blockchain. Bridge converter currencies have the same flexibility as other fractional 100% asset backed or partially asset backed currencies, but is bound to the launch of the new blockchain, runs on the new blockchain, and all fees generated via cross chain fee conversions or general use of the liquidity pool are earned on the new blockchain with no rent going back to the Verus blockchain, only seamless connectivity.
Blockchain-based, crowdfunding currency launches with minimum participation or automatic refunds, including for dual launches (blockchain and bridge)
- Set required minimum levels of worldwide participation in your preferred currencies on chain. If by the start time of your blockchain, minimums are not met, all participants will automatically get a refund of all of their pre-conversions, less the network fees. The launch options also provide for maximum participation in one or more currencies, pre-launch discounts, price neutral pre-allocations to select IDs that increase the fractional reserve ratio to issue currencies, similarly price neutral carve-outs of proceeds, and pre-launch discounts for early participants. Using VerusIDs, launches can also include vesting schedules in the pre-allocations as well.
An interoperable, multichain network for new use cases and unlimited scale**
- The Verus multi-currency, multi-chain network allows the creation of an unlimited number of interoperable blockchains in the Verus network. Notary IDs, specified at chain definition, provide decentralized blockchain-specific bridge confirmation, enabling public blockchains available to the world for merge mining and staking, as well as private, internal blockchains, which are easy to setup with easy bridging of public currencies into an organization and onto their internal private network and back, with all features and currencies of the public chain but none of the access. There is no limit on the number of blockchains that may continuously operate and interoperate on the Verus network. While there is some overhead for cross notarization, the model for the Verus blockchain network is fractal, enabling an unlimited number of simultaneously operating, interoperable blockchains.
Locking and Unlocking IDs
- Time Lock:
The unlockatblock parameter defines the unlock height of the identity.
run setidentitytimelock "id@" '{"unlockatblock": <Unlock block height>}'
- Time Delay:
The setunlockdelay parameter defines how many blocks to delay an ID's unlock when the flags are set back to an unlocked state.
run setidentitytimelock "id@" '{"setunlockdelay": <Unlock block delay>}'
- Revoking an identity will clear its locked status, regardless of time delay or unlock height.
- A locked identity cannot revoke itself.
Conversion Queries
The getcurrencyconverters API retrieves all currencies that have at least 1000 VRSC in reserve, are greater than 10% VRSC reserve ratio, and have all listed currencies as reserves
- E.g. BTC ETH:
run getcurrencyconverters btc eth
Will return all currencies that have btc/eth markets at or above the liquidity threshold.
Sending and Converting Currency
Warning: All testnet coins/currencies have no value and will disappear whenever VRSCTEST is reset
The sendcurrency API can be used to send and convert funds.
- Sending VRSCTEST from a single address (bob@) to a single recipient (alice@):
run sendcurrency "bob@" '[{"currency":"vrsctest","address":"alice@","amount":10}]'
- Sending VRSCTEST from all private wallet funds to two recipients with friendly-name z-addresses (alice@:private and bob@:private):
run sendcurrency "*Z" '[{"currency":"vrsctest","address":"alice@:private","amount":10},{"currency":"VRSCTEST","address":"bob@:private","amount":10}]'
- Converting VRSCTEST to a fractional basket currency, VRSC-BTC using IDs as a funding source:
run sendcurrency "*i" '[{"address":"bob@","amount":10, "convertto":"VRSC-BTC"}]'
- Converting VRSCTEST to another reserve, BTC through a fractional currency, VRSC-BTC:
run sendcurrency "*" '[{"address":"bob@","amount":10, "convertto":"BTC","via":"VRSC-BTC"}]'
- Preconverting to new currency, NEWCOIN, before it is active:
run sendcurrency "*" '[{"address":"alice@","amount":10, "convertto":"NEWCOIN", "preconvert":true, "refundto":"alice@"}]'
- Sending VRSCTEST cross-chain to PBaaSChain:
run sendcurrency "*" '[{"address":"RXLYm4J6qi7yam9zXtkEkRwbvCrnWKGZuv","amount":10, "exportto":"Bridge.PBaaSChain"}]'
- Converting VRSCTEST cross-chain to PBaaSChain:
run sendcurrency "*" '[{"address":"RXLYm4J6qi7yam9zXtkEkRwbvCrnWKGZuv","amount":10, "convertto":"PBaaSChain","exportto":"Bridge.PBaaSChain","via":"Bridge.PBaaSChain"}]'
- Converting PBaaSChain to VRSCTEST:
verus -chain=PBaaSChain sendcurrency "*" '[{"address":"RXLYm4J6qi7yam9zXtkEkRwbvCrnWKGZuv","amount":10, "convertto":"VRSCTEST","exportto":"VRSCTEST","via":"Bridge.PBaaSChain"}]'
Defining a Currency
Currency Options
OPTION_FRACTIONAL = 1 // allows reserve conversion using base calculations when set
OPTION_ID_ISSUANCE = 2 // clear is permissionless, if set, IDs may only be created by controlling ID
OPTION_ID_STAKING = 4 // all IDs on chain stake equally, rather than value-based staking
OPTION_ID_REFERRALS = 8 // if set, this chain supports referrals
OPTION_ID_REFERRALREQUIRED = 16 // if set, this chain requires referrals
OPTION_TOKEN = 32 // if set, this is a token, not a native currency
OPTION_SINGLECURRENCY = 64 // for PBaaS chains or gateways to potentially restrict to single currency
OPTION_GATEWAY = 128 // if set, this routes external currencies
OPTION_PBAAS = 256 // this is a PBaaS chain definition
OPTION_GATEWAY_CONVERTER = 512 // this means that for a specific PBaaS gateway, this is the default converter and will publish prices
OPTION_GATEWAY_NAMECONTROLLER = 1024 // when not set on a gateway, top level ID and currency registration happen on launch chain
OPTION_NFT_TOKEN = 2048 // single satoshi NFT token, tokenizes control over the root ID
To create a currency of a specific name, you need an ID of the same name. The controller of this ID is the only one who can create a currency of that name, and they can only do so once.
So, let's hypothetically assume I have 3 IDs, one named gold@, one named mycoin@, and one named mike@. I would like to have one currency, gold@,
that I somehow launch in a way that maps it in a way that can be widely trusted to a specific, auditable store of gold.
I also would like to launch a token called mycoin@, which is something like a Kickstarter, where a business, "my", offers to attribute the coins some utility or product value if the purchase exceeds a certain level.
First, I could define the currency "gold" as follows:
run definecurrency '{"name":"gold","options":32,"currencies":["vrsctest"],"conversions":[0.01],"minpreconversion":[1000],"preallocations":[{"mike@":50000000.00000000}]}'
of course, since this is a test currency, I send myself some to start. The identity of the currency must be funded with at least 10 VRSCTEST before sending the transaction returned from this command to
initiate a currency launch that will start at 50 blocks from when it was made (default), and that must have 1000 VRSCTEST preconverted at 0.01 VRSCTEST per GOLD in order to launch.
all of this happens as part of the mining process, since mining the blocks that launch a currency earn the 0.025% conversion fees of participation
in the launch, converting VRSCTEST to GOLD. I could send the following command before the block where GOLD token launches.
After it launches, the only way at present to create new tokens is with a centralized issuance option. To convert VRSCTEST to GOLD, you could issue the command:
run sendcurrency "*" '[{"address":"mike@","convertto":"gold","preconvert":1,"amount":100}]'
that would effectively park my conversion until the token launches, at which point, I will either find 0.975 GOLD in my wallet, or I will have my VRSCTEST back.
Assuming it launches, and I later want to create mycoin, which can be converted to with either GOLD or VRSCTEST, I can create mycoin with:
run definecurrency '{"name":"mycoin","options":33, "proofprotocol":2,"currencies":["vrsctest", "gold"],"minpreconversion":[10000,5.1298]}, "initialsupply":20000'
In "mycoin", I set proofprotocol to 2, which is PROOF_CHAINID. That means that the controller of the chain ID can mint new coins as follows:
run sendcurrency "mycoin@" '[{"address":"mike@","currency":"mycoin","mintnew":1,"amount":10000}]'
Defining a PBaaS blockchain
{
"name": "PBaaSChain",
"options": 264,
"currencies": [
"VRSCTEST"
],
"conversions": [
1
],
"eras": [
{
"reward": 1200000000,
"decay": 0,
"halving": 0,
"eraend": 0
}
],
"notaries": [
"Notary1@",
"Notary2@",
"Notary3@"
],
"minnotariesconfirm": 2,
"nodes": [
{
"networkaddress": "111.111.111.111:10000",
"nodeidentity": "Node1@"
},
{
"networkaddress": "111.111.111.112:10000",
"nodeidentity": "Node2@"
}
],
"gatewayconvertername": "Bridge",
"gatewayconverterissuance": 1000000
}The bridge definition has overridable defaults
{
"currencies": [
"VRSCTEST",
"PBaaSChain",
"USD"
],
"initialcontributions": [
380228.12033701,
0,
1000000
],
"initialsupply": 3000000
}Now pass those definitions to definecurrency
run definecurrency '{"name":"PBaaSChain","options":264,"currencies":["VRSCTEST"],"conversions":[1],"eras":[{"reward":1200000000,"decay":0,"halving":0,"eraend":0}],"notaries":["Notary1@","Notary2@","Notary3@"],"minnotariesconfirm":2,"nodes":[{"networkaddress":"111.111.111.111:10000","nodeidentity":"Node1@"},{"networkaddress":"111.111.111.112:10000","nodeidentity":"Node2@"}],"gatewayconvertername":"Bridge","gatewayconverterissuance":1000000}' '{"currencies":["VRSCTEST","PBaaSChain","USD"],"initialcontributions":[371747.20398827,0,1000000],"initialsupply":3000000}'Exporting an ID to a PBaaS chain
run sendcurrency "*" '[{"address":"IDNAME@","exportto":"PBaaSChainName","exportid":"true","amount":100,"currency":"vrsctest"}]'
Signing transactions from multi-signature IDs (testnet and mainnet)
Create transaction, get raw transaction data:
verus sendcurrency <multi-signature-ID>@ '[{"address":"<destination_address>","amount":<transaction_amount>}]'
verus z_getoperationstatus <operation_id_returned_by_sendcurrency>
Take the raw hex transaction data provided by z_getoperationstatus to each additional wallet(s) containing the additional signing addresses/IDs:
verus signrawtransaction <raw_hex_transaction>
After the last necessary signature is applied, broadcast on the network using:
verus sendrawtransaction <raw_hex_signed_transaction>
Tokenizing ID control (next generation NFT):
The currency definition have flags OPTION_NFT_TOKEN + OPTION_TOKEN, and a max supply of 1 satoshi that is either pre allocated or pre-converted to. If the token is pre-allocated, then the maximum pre-conversion must be 0.
run definecurrency '{"name":"ID","options":2080,"preallocations":[{"ControlTokenRecipient@":0.00000001}],"maxpreconversion":[0]}'
Creating an identity with a fractional currency as its parent
registernamecommitment now takes two more positional arguments to specify a currency parent and a funding address. Use quotes "" to leave fields blank, the example below specifies a parent currency, vrsc-btc , but no referrer. We're now able to use z_addresses to fund the name commitment and identity registration
# run registernamecommitment name controladdress referral parent sourceoffunds
run registernamecommitment subID RDnf7mH7RQki9b7PqdBD2Er6WXv3DTawGr "" vrsc-btc zs1s2mteau9tcalvk55cnepw3aq7dr6w7f447pqqkxczat3a02208d3ersx60wz9srw3nkd25ppfny
Specify the parent in the identity definition. Enter false for returntx to sign and submit the id registration, 0 for the feeoffer to use the default fee, and the funding identity, transparent address, or z-address
# run registeridentity '{ID registration with name commitment}' returntx feeoffer sourceoffunds
run registeridentity '{"txid": "67635331cbccb7a2cbf408a9e97b3f8986133964e0315a8b9fd237a5fd95ac8f","namereservation": { "version": 1, "name": "ID", "parent": "i84mndBk2Znydpgm9T9pTjVvBnHkhErzLt", "salt": "b7070f2ca7495e49c85ab41b5a368150e2c217be6d08cc4102a1b682cddb6f01", "referral": ""},"identity":{"primaryaddresses":["RDnf7mH7RQki9b7PqdBD2Er6WXv3DTawGr"],"minimumsignatures":1,"name":"ID","parent":"vrsc-btc@"}}' false 0 zs1s2mteau9tcalvk55cnepw3aq7dr6w7f447pqqkxczat3a02208d3ersx60wz9srw3nkd25ppfny
If a currency's ID issuance require permission from the currency's identity then it must sign the name commitment and identity registration. Either use the parent identity to fund those transactions, or receive a raw transaction to give the identity owner to sign by setting returntx to true
Limitations in multi-currency to be aware of:
-
(GUI and CLI) You will not be able to make a currency from an ID that has a properly encoded i-address as its actual name, not its calculated ID. Generally, the advice is “don’t do that”. Using an i-address when referring to a currency will only be interpreted as referring to the currency or identity which has that i-address calculated based on its name registration. As a general rule, making an ID with an i-address as its name is not prevented by the protocol, but will cause problems whenever an i-address or name may be used (many cases) and will not be supported for creating currencies. To reduce any potential for user confusion, even though the naming system provides will also be expanding the set of characters that will not be allowed for currency registrations.
-
(GUI) If a currency is supported in the Verus Desktop already, such as BTC or ETH, you will not be able to use those same named currencies as a PBaaS chain. This limitation is considered errata for this testnet release and will not be a limitation before mainnet availability.
Disclaimer
This is experimental and unfinished software. Use at your own risk! No warranty for any kind of damage!
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The enclosed copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
MacOS: https://www.virustotal.com/gui/file/cff1cd433270d61f8b444968a662d740ca854d30f16df0ab8a09caaa41f35de7/detection
Linux-x86-64: https://www.virustotal.com/gui/file/0f031bf0e409d7d3aa9563e9c0a10229e69d716e2ce442f1e94f7cf4c97dd42e/detection
Linux-ARM64: https://www.virustotal.com/gui/file/6d4f2bb47d0938dde0e3f7061c058c075dd6e22e0414a21645b3a6425023db28/detection
Windows: https://www.virustotal.com/gui/file/d587106e2e9df7c8971db00a6bae539c5bfa68e2a298200f179d5f96533617b3/detection
Avast and Kaspersky may flag the software as "not-a-virus" or "PUP". These are warnings that you are installing mining software, which may be installed by a third party to exploit your PC.
To find out more about the false positives, review the following resources:
https://blog.malwarebytes.com/detections/pup-optional-bitcoinminer/
https://www.kaspersky.com/blog/not-a-virus/18015/
Verifying Downloads
A txt file containing the signer, standard sha256 file checksum, and signature, is included for each download. These packages have been signed with the identity "Verus Coin Foundation Releases@".
- Extract downloaded archive
- Verify signature for the extracted app or installer using the extracted textfile.