Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
Version 0.4.0g includes all improvements in 0.4.0f and an expiry on stake transactions to allow deletion from wallets later
Version 0.4.0f includes all improvements in 0.4.0e.
In addition, it provides more detail about stake (winner of the contest) and mint (staked reward) transactions in Agama GUI as well as CLI listtransactions. It also introduces safeguards against any possibility of double staking behavior caused by forks and reorgs and the ability to set the maximum number of transparent and private transactions in Agama in settings->App config.
0.4.0e fixes issues and introduces a much cleaner view of staking transactions and minted coinbases in the Agama GUI. The following community reported issues are resolved:
- Coinbase shielding problems to Sapling and sometimes to Sprout private addresses are resolved
- Staking will again default to sending the coinbase to the address that staked the reward unless -pubkey=66charpubkey is set. The public key of an address where you would like the coinbases to go can be determined using "validateaddress" either in the CLI or GUI.
- Agama GUI no longer shows ins and outs or multiple lines for a staking transaction. Instead, it now displays an easy to understand single line for each "stake" transaction and also easily distinguishes between mined and minted coinbases once they are mature.
0.4.0c - released 10/29/2018
All versions of the Verus Coin wallet from 0.4.0 and later have support for Sapling high performance zero knowledge transactions, which will activate on the Verus Coin Network at block 227520. In addition to basic Sapling support, 0.4.0c includes support for Sapling compatible, transparent mobile transactions. For lite mode usage on the Verus Coin or Zcash networks, you will need Verus Enhanced Agama v 0.4.0c.
In addition to Sapling and support for Stake Guard transactions, which all versions 0.4.0 or later have, 0.4.0c also includes a powerful “Cheat Catcher” that can earn money as miners and stakers who use it protect the Verus Coin network by catching stakers who are staking for rewards in a selfish way that does not contribute to converging the network on one blockchain. The new “Cheat Catcher” support requires a Sapling z-address, either passed in to the CLI wallet with the “-cheatcatcher=zaddress” option, or added in the Settings->App config of the enhanced Agama GUI.
Once your cheat catcher address has been set, a full node wallet that is mining OR staking, will also be looking for forks where the same winning coins may be posted on two different forks, signed by the same person. If this is ever discovered, the the mining or staking wallet will create a transaction that has cryptographic evidence of the cheating and submit it for shielding to the cheat catcher’s address. That means that while staking or mining, anyone who has a Sapling cheat catcher address set, may periodically find an additional shielded coinbase or two in their cheat catching address. Earning cheat catching rewards does not new create coins, but actually takes them from cheaters, so DON’T CHEAT :) ! Earning a cheat catching reward can also occur whether or not you earn a block reward and is available equally across the network to all miners and stakers, more dependent on who happens to observe the cheating fork and catches the cheater than on staking or mining power.
Version 0.4.0c also fixes the following issues reported in prior versions:
- Wallet balance can get out of sync with blockchain when staking
- Some non-Latin usernames cause failure to load
- When used to load KMD in GUI Agama, Komodo stops accruing interest after transfer
IF YOUR WALLET IS OUT OF SYNC, YOU CAN RESCAN TO FIX THE PROBLEM.
- Simply add the parameter “-rescan” when starting the daemon.
- Close the application, wait for the GUI to close, then restart the GUI
- When restarting, select “Activate Coin”, not a dropdown shortcut
on the “Activate Coin” screen, select “Verus” and select “Native mode”
- Choose the “daemon param: rescan” option
click “Activate Coin”
- Solves an issue where pool may exceed getblocktemplate's ability to keep up with work queue when network is under stress
- Fix to verus bash script to allow execution from external directories
- Komodo compatibility
Verus Coin 0.4.0 - Release Notes
IF TWO OF YOUR MACHINES STAKE BLOCKS WITH THE SAME COINS, EACH ON A SEPARATE FORK, YOU CAN NOW LOSE YOUR BLOCK REWARD TO A CHEAT-CATCHER.
STAKING IS NOW OFF BY DEFAULT TO PREVENT MULTI-MACHINE STAKING OF THE SAME COINS OR ADDRESSES. YOU CAN EASILY ENABLE STAKING WITH THE “-mint” PARAMETER TO verusd, “setgenerate true 0” WITH “verus” CLI, OR THE STAKING BUTTON IN THE GUI.
ONLY STAKE ANY ADDRESS OR WALLET ON ONE COMPUTER AT A TIME, NOT MORE, UNLESS YOU CAN BE ABSOLUTELY SURE THEY ARE IN SYNC AND ON THE SAME CHAIN AT EVERY BLOCK. YOU CAN STILL MINE ON AS MANY MACHINES AS YOU’D LIKE.
Verus Coin 0.4.0 includes support for Sapling addresses and transactions, including memory usage reduction of near 98% and performance improvements over previous z-transactions typically 40-50x. As with Zcash Sapling upgrade rules, older “Sprout” addresses and “Sapling” addresses may not be mixed in the same transaction. That means if you have Verus Coin that you would like to move from an older Sprout z-address to a Sapling z-address, you must first send it to a transparent address, then to the Sapling z-address. Sapling addresses can be used for shielding coinbase transactions or other functions. Retrieving viewing keys for Sapling addresses, which is not required for normal transactions, is not yet supported, and will be included in the next Sapling technology update.
Crypto-conditions and StakeGuard
Verus-enhanced, Komodo crypto-condition technology, enabling smart transactions and new types of on-chain functionalities. Verus has enhanced the original crypto-condition technology to make integration with standard transactions easier and enable things like StakeGuard, the Verus nothing-at-stake solution. In later releases, the same technology will enable PBaaS, voting, identity capabilities, and more.
In addition to Stake Guard, which supports the nothing at stake solution, this version of Verus includes an early, functional version of the Cheat Catcher, a system that enables every miner or staker to catch stake cheating, when someone stakes two blocks with the same coins on two or more forks. With this version, all known orphaned stake transactions are compared to successful stakes when they mature, and if the orphan was trying to stake the exact same coins but on a different fork and the real fork at the same time, the miner of the block that is 100 blocks later, when that coinbase matures, will mine or stake a spend transaction for that cheat into the block, and send it to a sapling address the miner or staker has set in their wallet. If your wallet catches and spends a cheat transaction the reward for that coinbase will be automatically shielded to your address at the same time as you win the block. The early Cheat Catcher does not broadcast cheating transactions, and it will not catch all possible cheats on the network. It will make it a statistically losing proposition to cheat. This means you should not stake the same addresses on more than one computer at a time. Doing so creates the possibility that you will stake on two forks with the same coins, which puts your earnings at risk. Future cheat catcher implementations will excel at catching cheats on the network.
In the new Verus network protocol that activates at the same time as Sapling, you can now set the parameter -pubkey in the command line wallet, which will redirect both mining AND staking rewards to the public key of an address, which can be obtained from an address with the “validatekey” command.
- Timing improvements for more efficient staking
- Improved support for synchronizing with non-VRSC KMD-family coins