Releases: VerusCoin/Verus-Desktop
v0.9.5-2
Announcing v0.9.5-2, RECOMMENDED UPDATE FOR MAINNET - CRITICAL FOR CONTINUED TESTNET USE
YOU MUST BE UPDATED TO v0.9.5 OR LATER BY BLOCK 2291830, AT APPROXIMATELY 11:00 PM UTC, SATURDAY, NOVEMBER 19th, 2022 TO RELIABLY STAY SYNCHRONIZED TO THE VERUS MAINNET. WHILE THERE MAY BE A MAINNET PBAAS UPGRADE BEFORE THAT DATE, WE RECOMMEND THAT IF YOU HAVE NOT UPGRADED YET, THAT YOU DO SO NOW.
As with all v0.9.5-* releases, this release updates the Komodo notaries to season 6, with an activation height of 2291830, at approximately 11:00 PM UTC, Saturday, November 19th, 2022.
What’s New
For mainnet, this release labels spendable transactions for the getaddressutxos RPC API, which is used by Verus Mobile. This update is critical for users that have not upgraded to v0.9.5+ before block 2291830.
For testnet, v0.9.5-2 introduces minor notarization fixes that will be important for those intending to launch and witness PBaaS chains.
Ethereum Bridge
Although its deployment has been delayed, there are no technical blockers, and we still expect the Ethereum bridge to be brought back up on the new Verus testnet within the next day or two. When it is up, you can access the Verus <-> Ethereum testnet bridge here: https://ethtest.verus.services/, and use your metamask to convert or send cross-chain to the Verus network from Ethereum's Goerli. To use these features you will need to get some Goerli Ethereum, either from a faucet or via the Verus testnet liquidity baskets on Verus.
The rest of these release notes are the same as the prior release. We encourage you to drop by the pbaas-development channel, help the community prepare for the imminent mainnet release of the PBaaS upgrade and start building your vision today!
Verus PBaaS and DeFi RC5 - BUG BOUNTIES
At this time, we are not aware of any bugs or errors in the DeFi, ID, or PBaaS cross chain protocols on this version of testnet. We do not anticipate any changes to the PBaaS protocol before mainnet release, and we hope you will join us on testnet trying out all of the incredible capabilities and looking for any potential, remaining issues that can possibly be found before mainnet release. While we don’t expect it to be easy to find bugs in the protocol, The Verus Coin Foundation is offering a bounty of at least 500 VRSC (possibly more for security related reports) for the first 10 people (7 still unclaimed) who are first to report any actual protocol bug before mainnet release, meaning failure of a properly executed command or API on a functioning VRSCTEST or PBaaS chain to function as intended. If anyone is first to find and describe the exploit for an exploitable security hole in any part of the protocol, the bounty will be a minimum of 1,000 VRSC, and for a serious potential security issue, 10,000 $VRSC.
Testnet Reset
To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
- Linux:
~/.komodo/vrsctest
,~/.verustest
- Mac OS:
~/Library/Application Support/Komodo/vrsctest
,~/Library/Application\ Support/VerusTest
- Windows 10:
%AppData%\Roaming\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
or%AppData%\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
Additional Verus Capabilities
- On-chain Launches of Token, Centralized Currency, and Liquidity Basket AMMs
- On-chain Launches and Merge Mining of Independent, Connected, Interoperable Blockchains without Programming
- On-chain Self Sovereign, Provable Identities, NFTs, and Individual or Organizational Profiles
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 bas...
v0.9.5-1
Announcing v0.9.5-1, CRITICAL UPDATE FOR MAINNET MANDATORY FOR CONTINUED TESTNET USE
As with the last release, this release updates the Komodo notaries to season 6, with an activation height of 2291830, at approximately 11:00 PM UTC, Saturday, November 19th, 2022. YOU MUST BE UPDATED TO v0.9.5 OR LATER BY THEN TO RELIABLY STAY SYNCHRONIZED TO THE VERUS MAINNET. WHILE THERE MAY BE A MAINNET PBAAS UPGRADE BEFORE THAT DATE, WE RECOMMEND THAT IF YOU HAVE NOT UPGRADED YET, THAT YOU DO SO NOW.
Please make sure that if you do choose to wait for the possibility of a mainnet PBaaS upgrade before this activation that you do upgrade to the latest release before Saturday, November 19th.
What’s New
For mainnet, this release has no material changes over v0.9.5, but is still considered critical, as mainnet users should be upgraded to v0.9.5+ before block 2291830.
For testnet, v0.9.5-1 fixes an issue discovered on testnet where duplicate ID exports blocked cross-chain processing temporarily and also introduces a protocol improvement designed to make the Verus anti-MEV DeFi protocol even more resistant than what we believe was already the leading algorithm to multi-block attempts at MEV. The protocol change makes the following adjustments:
Conversions and cross-chain transfers still roll-up into exports that are collected from one or more blocks of transfer transactions, but to determine when a block is the last of the prior export or first in the next requires a random bit pulled from later blocks.
The last miner or staker to complete a block of an export retroactively receives 10% of all fees from processing that export, including all conversions, once the rollup is processed as an import. This reward used to go to the miner or staker who processes the export, which is no longer the case.
Import transactions can now include up to n/2 arbitrage transactions, where n is the number of reserves in a liquidity basket currency.
These changes together serve to disincentivize any miner or staker from attempting to exclude a large set of transactions from a block and front run all of them, as they will have an even chance of having all of those excluded transactions put back in with their transaction, turning potential gain into potential loss. They would be better off saving their working capital to arbitrage imports by joining transactions, bringing them close to market, and earning money without risk of loss. In addition, if they do end up putting more value of transactions in a block that caps the export rollup, they will reliably earn meaningful rewards without risk of loss in that way as well.
Ethereum Bridge
Although its deployment has been delayed, we expect the Ethereum bridge to be brought back up on the new Verus testnet within the next day or two. When it is up, you can access the Verus <-> Ethereum testnet bridge here: https://ethtest.verus.services, and use your metamask to convert or send cross-chain to the Verus network from Ethereum's Goerli. To use these features you will need to get some Goerli Ethereum, either from a faucet or via the Verus testnet liquidity baskets on Verus.
The rest of these release notes are the same as the prior release. We encourage you to drop by the #pbaas-development channel, help the community prepare for mainnet release in the next couple weeks and start building your vision today!
Verus PBaaS and DeFi RC5 - BUG BOUNTIES
At this time, we are not aware of any bugs or errors in the DeFi, ID, or PBaaS cross chain protocols on this version of testnet. We do not anticipate any changes to the PBaaS protocol before mainnet release, and we hope you will join us on testnet trying out all of the incredible capabilities and looking for any potential, remaining issues that can possibly be found before mainnet release. While we don’t expect it to be easy to find bugs in the protocol, The Verus Coin Foundation is offering a bounty of at least 500 VRSC (possibly more for security related reports) for the first 10 people (7 still unclaimed) who are first to report any actual protocol bug before mainnet release, meaning failure of a properly executed command or API on a functioning VRSCTEST or PBaaS chain to function as intended. If anyone is first to find and describe the exploit for an exploitable security hole in any part of the protocol, the bounty will be a minimum of 1,000 VRSC, and for a serious potential security issue, 10,000 $VRSC.
Testnet Reset
To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
- Linux:
~/.komodo/vrsctest
,~/.verustest
- Mac OS:
~/Library/Application Support/Komodo/vrsctest
,~/Library/Application\ Support/VerusTest
- Windows 10:
%AppData%\Roaming\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
or%AppData%\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
Additional Verus Capabilities
- On-chain Launches of Token, Centralized Currency, and Liquidity Basket AMMs
- On-chain Launches and Merge Mining of Independent, Connected, Interoperable Blockchains without Programming
- On-chain Self Sovereign, Provable Identities, NFTs, and Individual or Organizational Profiles
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 id...
v0.9.5
Announcing v0.9.5, CRITICAL UPDATE FOR MAINNET AND TESTNET
This release updates the Komodo notaries to season 6, with an activation height of 2291830, at approximately 11:00 PM UTC, Saturday, November 19th, 2022. You must be updated to v0.9.5 or later by that time to reliably stay synchronized to the Verus mainnet. We are also working to get a mandatory update release during these next couple weeks, which will have the Verus PBaaS mainnet upgrade finalized as well. If you would prefer to wait for the PBaaS mainnet upgrade and upgrade once, we cannot guarantee that the PBaaS mainnet release will be available in the next couple weeks, but we are working to make that a reasonable choice as well. Please make sure that if you do choose to wait to upgrade that you do upgrade to the latest release before Saturday, November 19th.
New Signature Capabilities on Mainnet & Testnet
In addition to continued support for all of the signmessage
, signdata
, and signfile
APIs, as well as their verify* counterparts, v0.9.5 introduces 2 new APIs and CLI commands, signdata
and verifysignature
, that encompass all of the capabilities of previous signing and verification APIs and add new capabilities for advanced signatures and verification. These new advanced capabilities were designed for community work by @allbits, designing a more powerful and flexible framework for NFTs and ID-bound legal rights and agreements. In addition to digital signing of documents or information using an ID, the new APIs enable easily binding together multiple sources of content, documents, identities, and VDXF keys together into one verifiable signature and then being able to verify that signature, including all of its specific bindings.
Verus PBaaS and DeFi RC5 - BUG BOUNTIES
At this time, we are not aware of any bugs or errors in the DeFi, ID, or PBaaS cross chain protocols on this version of testnet. We do not anticipate any changes to the PBaaS protocol before mainnet release, and we hope you will join us on testnet trying out all of the incredible capabilities and looking for any potential, remaining issues that can possibly be found before mainnet release. While we don’t expect it to be easy to find bugs in the protocol, The Verus Coin Foundation is offering a bounty of at least 500 VRSC (possibly more for security related reports) for the first 10 people who are first to report any actual protocol bug before mainnet release, meaning failure of a properly executed command or API on a functioning VRSCTEST or PBaaS chain to function as intended. If anyone is first to find and describe the exploit for an exploitable security hole in any part of the protocol, the bounty will be a minimum of 1,000 VRSC, and for a serious potential security issue, 10,000 $VRSC.
Emoji IDs and 🎃Chain
In the spirit of this release day, we have taken advantage of VerusIDs and currency emoji support and created a new, merge mineable PBaaS chain, 🎃. It has been said that those who merge mine 🎃chain at midnight will disappear into the crypto-metaverse, never to be seen again, become VerusID avatars, and be forever doomed to being bought and sold on the VRSCTEST marketplace for all eternity (or until the next testnet reset). YOU HAVE BEEN WARNED!
We expect the Ethereum bridge to be brought back up on the new Verus testnet within the next day or two. When it is up, you can access the Verus <-> Ethereum testnet bridge here: https://ethtest.verus.services, and use your metamask to convert or send cross-chain to the Verus network from Ethereum's Goerli. To use these features you will need to get some Goerli Ethereum, either from a faucet or via the Verus testnet liquidity baskets on Verus.
The rest of these release notes are the same as the prior release. We encourage you to drop by the #pbaas-development channel, help the community prepare for mainnet release in the next couple weeks and start building your vision today!
Testnet Reset
To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
- Linux:
~/.komodo/vrsctest
,~/.verustest
- Mac OS:
~/Library/Application Support/Komodo/vrsctest
,~/Library/Application\ Support/VerusTest
- Windows 10:
%AppData%\Roaming\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
or%AppData%\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
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.
verus -chain=vrsctest 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
# verus -chain=vrsctest registernamecommitment name controladdress referral parent sourceoffunds
verus -chain=vrsctest 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
# verus -chain=vrsctest registeridentity '{ID registration with name commitment}' returntx feeoffer sourceoffunds
verus -chain=vrsctest 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
Additional Verus Capabilities
- On-chain Launches of Token, Centralized Currency, and Liquidity Basket AMMs
- On-chain Launches and Merge Mining of Independent, Connected, Interoperable Blockchains without Programming
- On-chain Self Sovereign, Provable Identities, NFTs, and Individual or Organizational Profiles
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.
Exporting an ID to a PBaaS chain
verus -chain=VRSCTEST 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-sig...
v0.9.4-5
Announcing v0.9.4-5, RECOMMENDED FOR MAINNET AND TESTNET
This release fixes an RPC API issue on mainnet and testnet that can cause a daemon fault when the getaddressmempool API is used. This fault while running is only caused by non-typical API, insight explorer, or CLI use, but if it does happen, may result in the need to rescan or resync your wallet. We know of no one on mainnet affected by this issue. We recommend that all users upgrade.
This release also includes a new capability for testnet, which was pioneered by CHIPS developer @biz, who worked to modify and test the Verus PoP algorithm to support 10 second block times, which the CHIPS chain uses to enable its game application focus. These new parameters will enable the CHIPS blockchain to move to being an interoperable, merge mineable PBaaS chain with a 10 second blocktime when PBaaS goes live on mainnet. To learn how to test the new CHIPS test chain on testnet, visit the #pbaas-development channel, as the support in v0.9.4-5 is not as complete as it will be in the next and hopefully final testnet reset. In that next version, blocktime and the pow averaging window for any PBaaS chain’s PoP consensus will be able to be configured between 10 seconds and 2 minutes in addition to its notarization frequency as part of the chain definition, enabling a greater variety of PBaaS use cases, transaction throughput, and application capabilities.
As a reminder, you can access the Verus <-> Ethereum testnet bridge here: https://ethtest.verus.services , using your metamask, converting or sending cross chain through the Verus network from Ethereum's Goerli. To use these features you will need to get some Goerli Ethereum, either from a faucet or via the Verus testnet liquidity baskets on Verus.
The rest of these release notes are the same as the prior release. We encourage you to drop by the #pbaas-development channel, help the community prepare for mainnet and start building your vision today!
Known issues:
- Verus Desktop will only write a conf file for veth if the bridgekeeper is toggled on. If the configuration cog is used before trying to turn on bridgekeeper, a veth conf file will not be created and won't be saved. If you do not get a confirmation that your bridgekeeper settings got saved, try turning on the bridgekeeper first to create a conf file, and then try again.
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.
verus -chain=vrsctest definecurrency '{"name":"ID","options":2080,"preallocations":[{"ControlTokenRecipient@":0.00000001}],"maxpreconversion":[0]}'
Testnet Reset
To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
- Linux:
~/.komodo/vrsctest
,~/.verustest
- Mac OS:
~/Library/Application Support/Komodo/vrsctest
,~/Library/Application\ Support/VerusTest
- Windows 10:
%AppData%\Roaming\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
or%AppData%\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
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
# verus -chain=vrsctest registernamecommitment name controladdress referral parent sourceoffunds
verus -chain=vrsctest 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
# verus -chain=vrsctest registeridentity '{ID registration with name commitment}' returntx feeoffer sourceoffunds
verus -chain=vrsctest 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
Additional Verus Capabilities
- On-chain Launches of Token, Centralized Currency, and Liquidity Basket AMMs
- On-chain Launches and Merge Mining of Independent, Connected, Interoperable Blockchains without Programming
- On-chain Self Sovereign, Provable Identities, NFTs, and Individual or Organizational Profiles
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.
Exporting an ID to a PBaaS chain
verus -chain=VRSCTEST 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>
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 ca...
v0.9.4-4
Announcing v0.9.4-4, UNCHANGED FOR MAINNET -- RECOMMENDED FOR CONTINUED TESTNET USE, MANDATORY FOR CONTINUED TESTNET MERGE OR BRIDGE MINING
This release has no material mainnet changes.
This release primarily upgrades the ETH bridge and also fixes a PBaaS cross-chain notarization issue that made miners and stakers consider themselves ineligible to enter cross-chain notarizations. There are no actual protocol changes.
The ETH bridge upgrade introduces the ability to enter notarizations between Ethereum Goerli and VRSCTEST using bridgekeeper without an Ethereum private key in your conf file. This will enable you to still mine and potentially earn by agreeing or disagreeing with notarizations mined into the Verus blockchain, without needing to make transactions on or spend Ethereum for fees. This should also work with a free Infura account.
As a reminder, you can access the Verus <-> Ethereum testnet bridge here: https://ethtest.verus.services , using your metamask, converting or sending cross chain through the Verus network from Ethereum's Goerli. To use these features you will need to get some Goerli Ethereum, either from a faucet or via the Verus testnet liquidity baskets on Verus.
The rest of these release notes are the same as the prior release. Drop by the #pbaas-development channel to help us prepare for mainnet and start building your vision today!
Known issues:
- Verus Desktop will only write a conf file for veth if the bridgekeeper is toggled on. If the configuration cog is used before trying to turn on bridgekeeper, a veth conf file will not be created and won't be saved. If you do not get a confirmation that your bridgekeeper settings got saved, try turning on the bridgekeeper first to create a conf file, and then try again.
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.
verus -chain=vrsctest definecurrency '{"name":"ID","options":2080,"preallocations":[{"ControlTokenRecipient@":0.00000001}],"maxpreconversion":[0]}'
Testnet Reset
To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
- Linux:
~/.komodo/vrsctest
,~/.verustest
- Mac OS:
~/Library/Application Support/Komodo/vrsctest
,~/Library/Application\ Support/VerusTest
- Windows 10:
%AppData%\Roaming\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
or%AppData%\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
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
# verus -chain=vrsctest registernamecommitment name controladdress referral parent sourceoffunds
verus -chain=vrsctest 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
# verus -chain=vrsctest registeridentity '{ID registration with name commitment}' returntx feeoffer sourceoffunds
verus -chain=vrsctest 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
Additional Verus Capabilities
- On-chain Launches of Token, Centralized Currency, and Liquidity Basket AMMs
- On-chain Launches and Merge Mining of Independent, Connected, Interoperable Blockchains without Programming
- On-chain Self Sovereign, Provable Identities, NFTs, and Individual or Organizational Profiles
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.
Exporting an ID to a PBaaS chain
verus -chain=VRSCTEST 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>
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 Des...
v0.9.4-3
Announcing v0.9.4-3, UNCHANGED FOR MAINNET -- MANDATORY FOR CONTINUED TESTNET USE
This release has no material mainnet changes.
This release upgrades the testnet protocol to fix an issue with the Ethereum bridge and VRSCTEST mining and staking. Please update to v0.9.4-3 to continue mining and staking on testnet and the Ethereum bridge. This version also fixes an issue discovered when defining Ethereum NFT mapped tokens, which are not yet supported in the released Ethereum contracts, but are updated no in the daemon and ready to use when the contracts are upgraded, hopefully in the next few days.
NFT mapped tokens will allow you to define an Ethereum NFT as the token that controls revoke and recover for an ID. Similar to how you can define a token for tokenized ID control, an NFT mapped token, when defined, refers by contract and tokenid to a specific NFT on the Ethereum blockchain. Once defined as the currency for a specific ID or sub-ID and linked to the Ethereum NFT, that NFT will be able to be sent over from the Ethereum blockchain as a satoshi of that currency, sent to any address or ID on the Verus blockchain, exchanged trustlessly on the Verus on-chain P2P marketplace, and used to revoke and recover the ID which defined the token. Once the contracts are updated, you will be able to mint NFTs on Ethereum’s Goerli testnet, and endow your Ethereum NFTs with all of the power of your specially named VerusID. This new technology allows you to protect your NFTs with VerusID’s revoke and recover technology, bind your NFT to the pseudonymous ID you use to log into applications, use it to extend and publish much more than just the NFT, and generally take your Ethereum NFTs to the next level!
Known issues:
- Verus Desktop will only write a conf file for veth if the bridgekeeper is toggled on. If the configuration cog is used before trying to turn on bridgekeeper, a veth conf file will not be created and won't be saved. If you do not get a confirmation that your bridgekeeper settings got saved, try turning on the bridgekeeper first to create a conf file, and then try again.
The rest of these release notes are the same as the prior release. Drop by the #pbaas-development channel to help us prepare for mainnet and start building your vision today!
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.
verus -chain=vrsctest definecurrency '{"name":"ID","options":2080,"preallocations":[{"ControlTokenRecipient@":0.00000001}],"maxpreconversion":[0]}'
Testnet Reset
To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
- Linux:
~/.Komodo/vrsctest
,~/.verustest
- Mac OS:
~/Library/Application Support/Komodo/vrsctest
,~/Library/Application\ Support/VerusTest
- Windows 10:
%AppData%\Roaming\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
or%AppData%\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
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
# verus -chain=vrsctest registernamecommitment name controladdress referral parent sourceoffunds
verus -chain=vrsctest 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
# verus -chain=vrsctest registeridentity '{ID registration with name commitment}' returntx feeoffer sourceoffunds
verus -chain=vrsctest 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
Additional Verus Capabilities
- On-chain Launches of Token, Centralized Currency, and Liquidity Basket AMMs
- On-chain Launches and Merge Mining of Independent, Connected, Interoperable Blockchains without Programming
- On-chain Self Sovereign, Provable Identities, NFTs, and Individual or Organizational Profiles
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.
Exporting an ID to a PBaaS chain
verus -chain=VRSCTEST 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>
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...
v0.9.4-2
Announcing v0.9.4-2, UNCHANGED FOR MAINNET -- MANDATORY FOR TESTNET USE
This release has no material mainnet changes.
THE NEW ETHEREUM BRIDGE IS EXPECTED TO BE DEFINED WITHIN THE NEXT 24 HOURS AND FOR THE BRIDGE LIQUIDITY BASKET TO LAUNCH SHORTLY AFTER DEFINITION. IF YOU LEAVE A PRIOR VERSION NODE RUNNING UNTIL AFTER THE VETH BRIDGE IS DEFINED, YOU MAY FORK AWAY DUE TO CHANGES IN THIS RELEASE AND THEN NEED TO RESYNC TO TESTNET FROM SCRATCH TO CONTINUE.
For testnet, this is RC4 of the Verus PBaaS protocol, which includes some Ethereum bridge related fixes and a merge mining API change. With the API change, all merge mining nodes must upgrade to the new protocol to be compatible with each other and participate in cross-chain notarization rewards.
After the Ethereum bridge has been defined, you will be able to send currencies over to Verus testnet from Ethereum’s Goerli network and also participate in the launch of the Ethereum bridge liquidity basket with VETH, USDC, or VRSCTEST by using sendcurrency
with “preconvert”:true
on the command line or through the GUI. We recommend that you get some Goerli ETH using this facet or others (https://goerli-faucet.mudit.blog/), which will make your experience of all Verus PBaaS can offer a bit more well rounded when the Ethereum bridge is available once again.
Once the Goerli Ethereum liquidity basket (Bridge.vETH) activates on testnet, which is a 100% backed basket composed of 1/3rd each of Verus, Ethereum, and USDC (all testnet tokens), you can use it from Metamask on Goerli, from the Verus CLI or GUI on the vrsctest chain, or from CLI/GUI on other PBaaS chains to provide liquidity while holding Bridge.vETH, a 100% backed basket of three currencies of balanced relative value, or to pass through and convert currencies between Verus, Ethereum, USDC, and Bridge.vETH.
The Brige.vETH currency also coordinates with the vETH@ gateway and enables registering *.veth@
IDs for $5 worth of Bridge.vETH, based on its internal USDC conversion price at the time of registration. When you register *.veth@
IDs, 0.02 VRSCTEST goes to miners and stakers, and $5 worth of Bridge.vETH is burned, reducing the total supply of Bridge.vETH for everyone without reducing reserves, and contributing to the relative value, “real yield” of Bridge.vETH, relative to its three reserve currencies. This is the way that all decentralized, fractional currencies which enable ID registration accept registration fees, equally benefiting all fractional currency holders/liquidity providers when IDs are registered, while providing Verus miners and stakers the identity import fee of 0.02 VRSC.
*.veth@
IDs have the ability, along with root vrsctest IDs, to make 1:1 ERC20 mapped currencies on Ethereum. They can also be used to create Tokenized ID control tokens (see notes for v0.9.4-1), as all types of IDs can, but if they are used to do that, they will have used their currency creation ability for that rather than an ERC20 mapped currency.
Known issues:
- Verus Desktop will only write a conf file for veth if the bridgekeeper is toggled on. If the configuration cog is used before trying to turn on bridgekeeper, a veth conf file will not be created and won't be saved. If you do not get a confirmation that your bridgekeeper settings got saved, try turning on the bridgekeeper first to create a conf file, and then try again.
The rest of these release notes are the same as the prior release. Drop by #pbaas-development to start building your vision on Verus and help prepare PBaaS for mainnet!
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.
verus -chain=vrsctest definecurrency '{"name":"ID","options":2080,"preallocations":[{"ControlTokenRecipient@":0.00000001}],"maxpreconversion":[0]}'
Testnet Reset
To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
- Linux:
~/.Komodo/vrsctest
,~/.verustest
- Mac OS:
~/Library/Application Support/Komodo/vrsctest
,~/Library/Application\ Support/VerusTest
- Windows 10:
%AppData%\Roaming\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
or%AppData%\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
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
# verus -chain=vrsctest registernamecommitment name controladdress referral parent sourceoffunds
verus -chain=vrsctest 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
# verus -chain=vrsctest registeridentity '{ID registration with name commitment}' returntx feeoffer sourceoffunds
verus -chain=vrsctest 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
Additional Verus Capabilities
- On-chain Launches of Token, Centralized Currency, and Liquidity Basket AMMs
- On-chain Launches and Merge Mining of Independent, Connected, Interoperable Blockchains without Programming
- On-chain Self Sovereign, Provable Identities, NFTs, and Individual or Organizational Profiles
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.
Exporting an ID to a PBaaS chain
verus -chain=VRSCTEST 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 nece...
v0.9.4-1
Announcing v0.9.4-1 with the world’s first self-sovereign, tokenized ID control technology, RECOMMENDED FOR MAINNET -- MANDATORY FOR TESTNET USE
This release has no material mainnet changes.
For testnet, this is RC3 of the PBaaS protocol and is required to follow the main testnet chain. RC3 has some significant and important API additions, including the ability for any ID at all, even sub-IDs, to generate a single token as its currency. That token then enables whoever holds it to have another level of revoke/recover power over the ID, in addition to the normal revocation and recovery authorities, which also still work. This technology is now available in the pre-existing APIs, updateidentity (for changing revocation / recovery authorities), revokeidentity, and recoveryidentity. Please see help for details.
In addition, we have continued to harden the protocol and fixed issues with cross-chain currency definition import/export and the new ability to burn reserves into a liquidity basket that were reported in the current testnet.
The rest of these release notes are the same as the prior release. Drop by pbaas-development to start building your vision on Verus while helping get PBaaS ready for mainnet!
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.
verus -chain=vrsctest definecurrency '{"name":"ID","options":2080,"preallocations":[{"ControlTokenRecipient@":0.00000001}],"maxpreconversion":[0]}'
Testnet Reset
To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
- Linux:
~/.Komodo/vrsctest
,~/.verustest
- Mac OS:
~/Library/Application Support/Komodo/vrsctest
,~/Library/Application\ Support/VerusTest
- Windows 10:
%AppData%\Roaming\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
or%AppData%\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
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
# verus -chain=vrsctest registernamecommitment name controladdress referral parent sourceoffunds
verus -chain=vrsctest 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
# verus -chain=vrsctest registeridentity '{ID registration with name commitment}' returntx feeoffer sourceoffunds
verus -chain=vrsctest 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
Additional Verus Capabilities
- On-chain Launches of Token, Centralized Currency, and Liquidity Basket AMMs
- On-chain Launches and Merge Mining of Independent, Connected, Interoperable Blockchains without Programming
- On-chain Self Sovereign, Provable Identities, NFTs, and Individual or Organizational Profiles
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.
Exporting an ID to a PBaaS chain
verus -chain=VRSCTEST 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>
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 loc...
v0.9.4
Announcing v0.9.4, HIGHLY RECOMMENDED FOR MAINNET -- MANDATORY FOR TESTNET USE
This release fixes a mainnet issue that may, in rare cases, cause a node to deadlock.
It also adds the following new features to mainnet:
- Auto TLS encrypted connections between nodes on mainnet and testnet, no action needed, but you can require that all connections be encrypted by starting the daemon with “-tlsenforcement”.
- A new “-idindex” flag that enables 3 new APIs to lookup identities by their primary addresses or revocation and recovery addresses,
getidentitywithaddress
,getidentitywithrevocation
, andgetidentitywithrecovery
.
Generally improved multithreading within the daemon. - These improvements allow anyone to now write applications to easily graph or display public relationships between identities, transparent addresses, and transactions without compromising the privacy of private addresses, messages, or transactions between identities using name@:private endpoints, z-addresses or communicating via off-chain channels.
For testnet, this is RC2 of the PBaaS protocol and has some significant and important advances and changes. In addition to a great deal of progress hardening for mainnet, v0.9.4 introduces the following new features to the PBaaS testnet:
-
All features above for mainnet
-
NFT mapped tokens and tokenized ID control - In v0.9.4, as with v0.9.3, you can use root identities to create any kind of currencies, *.veth IDs to create Ethereum mapped currencies, and what is new in v0.9.4 is that you can now use any type of ID or sub-ID to create a new kind of currency that will always have a 1 Satoshi supply and enable anyone holding it to have power over the ID that issued it. This type of currency is called tokenized ID control and can be treated like a super NFT over all copies of the source ID on all chains that were exported to other chains after the currency was created. Once the Ethereum contracts are upgraded with this capability, *.veth or IDs with root names on the Verus blockchain can be used to create Ethereum NFT mapped currencies, which enable a Cryptopunk, Ethrock, or whatever other NFT you’d like to not only be sent to Verus, held on a revocable/recoverable ID, and also permanently upleveled with ID powers, being cryptographically bound as an ID’s permanent control token that can be sent to any chain or to Ethereum and back.
This unique Verus-only technology and VerusIDs enable new models of complex, atomic and fully decentralized transactions. By using exported IDs across any number of networks and an ID control token, ownership of an unlimited array of assets across an unlimited number of networks can for the first time ever, have ownership transferred in one transaction. -
While NFT mapped tokens are supported on the RC2 PBaaS protocol, they have not yet been implemented in the Ethereum contracts. You will not be able to send NFTs from Ethereum to Verus or PBaaS chains until that work is complete, which we do not expect to take a great deal of time.
-
Liquidity currencies now support new methods to burn currency with the following results:
burnweight
- available to centralized currencies only and enables burning the primary currency to raise the reserve ratio weights of all reserves.burn
for reserve currencies - in prior releases, burn was only used for primary currencies and would reduce the supply of a currency relative to its reserves, increasing the on-chain value of the primary currency. In v0.9.4, you can now also “burn” reserve currencies in a liquidity basket currency, which simply donates that amount of reserve into the currency’s reserves without taking any new supply in exchange. This is available to decentralized or centralized currencies.
-
Bridgekeeper is now available for permissionless bridge notarization and selectable in the GUI on the mining page. For CLI, we will make a Node application available for testing in the next few days.
-
RC1 cross-chain witness and notarization protocol enhanced in RC2 as follows:
- In RC2, any notarization to be confirmed must be first posted publicly to allow for potential to prove invalidity, and then later confirmed. In the prior protocol, a witnessed notarization could be posted to a chain and accepted when first seen. Upon analysis and discussion with @allbits and others, we realized that the attack vector of even stolen notary/witness keys combined with an in-secret 51% combined hash/stake attack could be prevented if we changed the protocol to first require posting the ready to finalize data and allow notaries who recognize that there is a signature on chain for something they don’t agree with (likely stolen key), to simply revoke their identity, which will prevent that notarization from ever being confirmed. This same security feature is supported between all PBaaS chains and has been implemented in the Ethereum contracts for witnesses as well. This new protocol also provides for other types of evidence to prevent finalization, such as proof that there exists a more powerful (most power rule) tip than one witnessed. Enabling decentralized, cross-chain most power rules are an advance in cross-chain protocols that over time will strongly protect censorship resistance qualities of any multichain protocol.
- The above technology required changes to generalize evidence types between chains, enabling cryptographic enforcement that all notarizations are ultimately determined by miners and stakers and finalized by witnesses who must follow most power (stake+work) rules based on the protocol. Witnesses cannot finalize a chain tip unless alternating miners and stakers have posted 3 consecutive, agreeing, progressing cross-chain notarizations, without intervening disagreement, trading off more certain cross-chain transaction latency for on that depends on miners and stakers, meaning maximum decentralization and a high cost to DoS attack cross-chain, approaching impossible over any significant length of time. This approach makes the incentivized merge mining and bridge mining opportunities, as well as miner/staker participation, automatically part of and also critical to the cross-chain protocol. In v0.9.4, all users on the network may mine the Ethereum bridge via the bridgekeeper tool on the mining page in the GUI.
- With this new protocol, all PBaaS chains on testnet will consider witnessed / finalized tips final and will not unwind past those witness points or follow a chain that disagrees with a known finalized tip. When this protocol goes live on mainnet, and for any PBaaS chain whose community opts to use the Komodo notary service, Komodo notarizations will continue to ensure a stable chain tip, but no matter what other notarizations are present, PBaaS chains will always follow their proof of power protocol and lock to their witnessed tips as well.
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.
verus -chain=vrsctest definecurrency '{"name":"ID","options":2080,"preallocations":[{"ControlTokenRecipient@":0.00000001}],"maxpreconversion":[0]}'
The rest of these release notes are the same as the prior release. Drop by pbaas-development to start building your vision on Verus while helping get PBaaS ready for mainnet!
Testnet Reset
To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
- Linux:
~/.Komodo/vrsctest
,~/.verustest
- Mac OS:
~/Library/Application Support/Komodo/vrsctest
,~/Library/Application\ Support/VerusTest
- Windows 10:
%AppData%\Roaming\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
or%AppData%\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
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
# verus -chain=vrsctest registernamecommitment name controladdress referral parent sourceoffunds
verus -chain=vrsctest 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
# verus -chain=vrsctest registeridentity '{ID registration with name commitment}' returntx feeoffer sourceoffunds
verus -chain=vrsctest 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
Additional Verus Capabilities
- On-chain Launches of Token, Centralized Curren...
v0.9.3
Announcing v0.9.3, NON-MANDATORY FOR MAINNET -- MANDATORY FOR TESTNET USE
This release fixes one issue on mainnet where a node using -connect=”networkaddress” may still attempt to connect to other nodes.
This update includes the first protocol release candidate for mainnet PBaaS, VerusID protocol upgrades, and Verus DeFi. In addition to some functional fixes and full web site support for mapped currencies and simple commands for mapping Verus currencies to any ERC20 currencies on Ethereum with provable, auditable 1:1 mapping and cross chain send/receive. In addition this new protocol upgrade changes some parameters of the Verus Proof of Power consensus algorithm, enabling smoother starts, restarts, and general operation of PBaaS chains, regardless of their native currency supply or emission schedule. As these consensus parameter changes would require either a testnet fork, which would not be relevant for the mainnet upgrade or a reset, accessing the v0.9.3 testnet requires that you reset your local testnet by deleting the vrsctest and pbaas data folders from the locations described below.
As part of this release, we will be launching the new Ethereum bridge and enable full use of Ethereum mapped currencies on the Goerli Ethereum testnet (note that we were previously using Rinkeby). This makes it easy for any currency definition to become a fully decentralized, auditable stable coin, simply by mapping to DAI, USDT, USDC, or another stable coin on Ethereum. In addition, the new website for Metamask support and use from Ethereum now displays all mapped currency options, even those added when someone exports a currency definition to Ethereum, either as a mapped currency or for using any Verus or PBaaS currency as an ERC20.
This release also resolves an issue with setting max preconversion amounts on currency launches and addresses a number of minor protocol issues found as a result of the active community testing support we are seeing on testnet.
v0.9.3 RESETS TESTNET AND ADDRESSES ALL KNOWN ISSUES FOUND DURING TESTING ON THE NETWORK. FROM HERE, WE HOPE ALL COMMUNITY MEMBERS WILL JOIN IN TRYING OUT ALL FEATURES OF TESTNET TO HELP ENSURE THAT THE FINAL MAINNET RELEASE, WHICH WE ARE WORKING TOWARDS AS SOON AS IT IS CONSIDERED READY AND HARDENED, WILL BE BOTH SMOOTH AND WORLD-CHANGING.
IF YOU HAVE ALREADY USED TESTNET WITH VERSIONS PRIOR TO v0.9.2, MAKE SURE TO DELETE AND CLEAR ANY EXISTING TESTNET DATA FOLDERS AS DESCRIBED BELOW.
GUI changes:
-
Added support for refund address for sends to different systems, in case after a two-step, convert and subsequent system crossing, there are not enough fees, due to slippage and liquidity, to make the crossing, according to the fees and rules of the destination system
-
Improved recognition and display of offline electrum servers for lite mode
-
Added reminder to backup native wallets for first use of native mode
-
Minor UI improvements
-
It is worth noting that the Zcash NU5 upgrade has broken compatibility with the Electrum servers that Verus Desktop and other 3rd party wallets were using for lite mode Zcash support. You can still export your Zcash seed and use it in Verus Desktop after importing it to Zcash native mode. You can also import the exported key to other Zcash supporting wallets. We do not consider it a priority to address this issue relative to enabling PBaaS on Verus mainnet, but assuming some level of interest and assistance from the Zcash community, we will opportunistically support lite mode again.
Platform Support
- Debian 9 (Stretch) is no longer supported
PROTOCOL RELEASE CANDIDATE RC1
With v0.9.3, The Verus PBaaS protocol, including networking, public blockchains as a service (PBaaS), VerusID extensions, and Verus DeFi, is considered release candidate RC1 for the coming mainnet upgrade. The core developer focus now remains on protocol hardening and enabling usage first, followed by user experience upgrades and supporting infrastructure such as identity and login support for lite mode, mobile and web extension wallets as well as merge mining for pool servers.
NEW PBAAS CAPABILITIES
All PBaaS capabilities, including for application development, are available now on the new Verus testnet. Now would be a good time for development capable projects hoping to get a head start on using Verus’s transformative technologies to do a deep dive on the Verus testnet. These new capabilities in v0.9.3, as well as all those we are familiar with, available nowhere else, will be on mainnet SOON(™):
All fractional and centralized {“proofprotocol”:2} currencies can now issue as a decentralized operation, or with centralized currencies, sell, IDs using their own currency as the payment currency, with options for price, referrals, permission from the currency identity required, which means the transaction must be created or co-signed by the currency identity, or even referrals required, which means that an identity registration must have a referral and co-signature of a referring ID that is either the currency ID or another ID from that currency namespace.
For fully decentralized fractional currencies, ID registration is paid for by burning the specific fractional currency, reducing the supply, and raising the on-chain value of the primary currency relative to its reserves by reducing the current on-chain supply for everyone.
The minimum price of ID registration for fractional currencies can be set in either the fractional currency itself, or in one of its reserves, for example USDC or DAI.
More than the minimum price can be paid for ID registration, which may also include VDXF key and contract bindings to allow for multiple types of content or IP licensing in a single ID namespace.
Each currency, either centralized and/or fractional, can have multiple levels of referral support (limit of 5 levels), meaning that the ID registration fee will be reduced when referred and part of it will be divided evenly among past referrers. The remaining amount of the ID registration fee will be burned for decentralized currencies, or be sent to the currency ID for centralized currencies.
While Native IDs, those registered directly from a blockchain as the name parent, will be able to launch currencies on that blockchain, and if on Verus, actual independent blockchains, IDs issued by fractional or centralized currencies cannot launch currencies, but will still be valuable as revocation and recovery IDs for all other VerusIDs as well as for personalized on-chain and cross-chain addresses with all identity and NFT features, for proofs, for brands, contract binding, on-chain marketplace trading, or login, and will have the ability to cross-prove common ownership with other IDs as well.
The exception to non-native IDs creating currencies, is that *.veth gateway IDs will be available for decentralized registration from the Ethereum bridge converter and will be able to create Ethereum mapped currencies. Registration of .veth IDs will be priced at 100 USD worth of ETH to prevent misuse and support bridge liquidity, with all fees besides the 1 VRSC import fee, which goes into the mining and staking fee pool going to the bridge converter liquidity basket.
All of these features are currently enabled on the v0.9.2 new testnet. Stay connected on the #pbaas-development channel and participate in the launch at no actual cost as a testnet liquidity provider and get some nice testnet IDs, launch your own currencies, or start your exclusive ID-restricted club, governance group, or business.
Testnet Reset
To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
- Linux:
~/.Komodo/vrsctest
,~/.verustest
- Mac OS:
~/Library/Application Support/Komodo/vrsctest
,~/Library/Application\ Support/VerusTest
- Windows 10:
%AppData%\Roaming\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
or%AppData%\Komodo\vrsctest\
,%AppData%\Roaming\VerusTest
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
# verus -chain=vrsctest registernamecommitment name controladdress referral parent sourceoffunds
verus -chain=vrsctest 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
# verus -chain=vrsctest registeridentity '{ID registration with name commitment}' returntx feeoffer sourceoffunds
verus -chain=vrsctest 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 `...