# Dd-19: V0.6.1 (11/25/16) V0.6.1 is an emergency fix for a hard forking issue. Everyone on v0.6.0 MUST upgrade ASAP. The commit message and link are as follows: multi Restore correct upstream majority version code. (PR#490) Following is the DD 18 release notes from completions sake: This development dispatch covers work completed since the Decred v0.5.0 release on October 10, 2016. Since then, developers have merged 43 pull requests into 8 repositories (see below for more detailed changes). Here are direct links to the Windows installers for Paymetheus: Paymetheus v0.6.1 64-bit Paymetheus v0.6.1 32-bit Installer: https://github.com/decred/decred-release/releases/tag/v0.6.1 Binaries: https://github.com/decred/decred-binaries/releases/tag/v0.6.1 This release contains bug fixes and improvements for dcrd and dcrwallet. A new block test framework has been added to simplify adding new tests. 380 new block tests have been added with it. Several RPC improvements have been made. A number of voting related fixed and improvements have been made to support future voting changes. dcrwallet now processes transactions atomically. gominer and copay are unchanged. Paymetheus is unchanged but should be updated for the updated dcrd and dcrwallet dependancies. dcrrpcclient Add SetBalanceToMaintain (PR#35) Add ExistsExpiredTickets to dcrrpcclient (PR#36) Add methods to use the new version and getheaders RPCs. (PR#37) Setticketsvotebits (PR#39) Updates for dcrd JSON-RPC websocket API changes. (PR#40) Credits: @chappjc, @ay-p, @jrick dcrwallet Add expired to getstakeinfo command (PR#360) Update dependencies, including 3rd party ones. (PR#361) Update the wallet to begin allowing extended votebits setting (PR#362) Fully update PoolTickets when using AddTicket rpc (PR#365) RFP-10 milestone 3 (PR#369) Bump for v0.6.0 (PR#373) Correctly handle both p2sh and p2pkh addrs in wstakemgr. (PR#376) Process transactions atomically with connected blocks. (PR#372) Remove Wallet.ChainSynced/SetChainSynced APIs. (PR#378) Credits: @ay-p, @jrick, @ceejep, @chappjc, @jcv dcrd Output of --help/-h should go to os.Stdout rather than os.Stderr (PR#386) Fix the dumpblockchain function (PR#405) Use correct function to fetch blocks from the blockchain for RPC (PR#407) Remove unused files (PR#408) Prevent high memory usage when turning txindex on first time (PR#412) Add a block pruner that only prunes occassionally (PR#415) dcrctl: fix output in --terminal mode (PR#416) Add existsexpiredtickets to rpcserver (PR#418) Replace some unnecessary dcrutil.Tx usage with wire.MsgTx. (PR#419) Add voting version parsing function (PR#420) Add dcrjson decode func for concatenated hex hashes. (PR#421) Add new setticketsvotebits command (PR#422) Add func to decode string hashes to a passed destination. (PR#425) Add getheaders JSON-RPC extension command. (PR#426) Add EncodeConcatenatedHashes with test. (PR#432) dcrctl: Set width to max in --terminal (PR#436) blockchain: Add block validation infrastructure (PR#437) Bump for v0.6.0 (PR#438) Update 3rd party deps in glide (PR#439) Add StakeVersion to header. (PR#441) Use same notification for mined transactions and blocks. (PR#434) Update dcrrpcclient for dcrctl. (PR#445) update checkpoints (PR#446) Notify only relevant stake txs, not all. (PR#447) multi: Restore correct upstream majority version code. (PR#490 Credits: @chappjc, @ceejep, @dhill, @ay-p, @jrick, @davecgh, @jcv, @moo1337 dcrticketbuyer Update onBlockConnected to match upcoming change in dcrd (PR#73) Credits: @ay-p Public keys The file cmd/dcrinstall/pubkey.go contains the decred public key which is used to check the signed manifest in the release. You can compare the contents of this file to what you get from a keyserver to confirm that dcrinstaller is using the proper key. Important The Decred installer will only work on Windows 7 and above.
Excellent response time! Pretty much the entire team came together on a Friday night to fix the issue and publish a release within a couple hours of being reported on IRC. Only a few public nodes are still affected. Bravo's primary nodes are updated, and no votes were missed on account of our policy of maintaining backup nodes on a rolling update schedule. BTW, dcrspy is updated to support the new onBlockConnected notification function signature. See the pre-release version.
Which reminds me, "missed" currently includes "expired", but I think this may be up for debate. That is, should missed exclude expired?
Now that we have the expired count, I would like to see the value removed from the missed count. To me, missed should mean something was wrong with the network or my voting node, causing it to miss votes.
Hi, I tried to update my nodes to 0.6.1 yesterday but then all shares were rejected - have you changed anything in getwork since 0.5.1?
@feeleep are you running something you built from the latest master or the v0.6.1 release (either the binaries we released or built from that tag or branch)?
dcrctl -u ktirio -P --wallet getbalance i put that but i can not see my balance here what i received why? Error creating a default config file: open C:\Users\NIK\AppData\Local\Dcrd\dcrd.conf: The system cannot find the file specified. 16
Syncing time of blocks has become worse out. Unlike it was till the previous update. (Replaced binaries)
I tried yesterday, the computer was not doing anything else, but the figure impressed me still. 0601_syncedFrom0_to_85408_in_23min Just WOW ! Big compliments !
Updated to 0.6.1 and my old settings no longer auto purchase tickets. I can still buy tickets manually. Anyone else have this problem? Tried restarting the wallet and server but no change. Still trying out various things that might be wrong at my end (user error)...
https://github.com/decred/dcrwallet/issues/377 dcrwallet will not purchase tickets until it has the funds to purchase the number of tickets specified by ticketbuyfreq=.
Thanks for info! I have it set to 10, mystery solved. Otherwise this release is a great improvement over 0.4(?) which I was running previously.
Good job! Thanks! BTW, should i reload blocks DB and/or recreate my wallet from seed after upgrade from 0.6.0 to 0.6.1 ?
hi - i am using your binaries. Maybe something was changed in RPC calls? I did not have time to check the difference but will try to do it in next few days. EDIT: I checked the output and I noticed that version number is now 02 and there are some values in extradata part. From my end everything looks fine (I do not do any hardcoded part) but maybe mining soft is not ready for these changes?
@feeleep Can you retry with 0.7.0? If that has issues too, then there is likely something wrong with whatever stratum software you're using since solo mining is working fine.