This development dispatch covers work completed since the Decred v0.0.9 release from April 1st, 2016. Since then, developers have merged 11 pull requests of code into 2 software repositories. During this period, a total of 11 commits occurred in these repositories and represent modifications to the effect of 1,810 lines of code added to and 566 lines removed from the codebase. A series of RFP milestones were achieved and paid for from the development subsidy. Deliverables from the milestones will begin appearing in the Decred ecosystem in the future. These include: Creation of a draft design of two views (68c733b) and subsequently all remaining views with icons for Paymetheus in RFP-1 (c89c056, da7dc15) Completion of wallet documentation, stake mining documentation, and network parameter and introductory explanation documentation for the Decred software in RFP-4 (784985d) Publishing of the source code for improvements to ccminer and the NVIDIA kernel (f940503), improvements to cgminer and the AMD kernel, and fixing high CPU usage when running cgminer (c51f811) Binaries: https://github.com/decred/decred-release/releases/tag/v0.0.10 dcrd Introduced a new utility which can be used to test transactions to determine whether or not they have inputs that trace back to the original c0/dev bring-up funds (100-fcaaa94) Added new JSON handling for wallet commands (accountaddressindex, accountfetchaddresses, accountsyncaddressindex, getwalletinfo), getmasterpubkey now takes an account argument, and a new daemon command livetickets has been added to dump hashes for all live tickets in the live ticket stake database (102-5658c50) Updated versioning (101-1517aaa) Credits: @ceejep, @davecgh, @jcv dcrwallet Added stake txscript types in ListUnspent to ensure they are flagged as spendable (151-976f14e) Fixed an issue that could cause address desyncing and address reuse (158-8c46cb7) Fixed issues that affected synchronization of the address pools on start up. New RPC commands have been added to help simplify and clarify address pool index synchronization (accountaddressindex, accountfetchaddresses, accountsyncaddressindex), getaddressesbyaccount has been corrected so that it now returns only up to the addresses used by the address pool, and walletinfo to check the global state of the wallet (161-fb01141) Fixed an issue where failed transactions due to the namespaces bucket being missing would cause deadlocks (163-29efe24) Fixed an issue where the password was prompted for on a new watching-only wallet start up (164-93eaee4) Updated testing (155-e7ad238), documentation (165-f1d9bd6), and versioning (159-113d1f4) Credits: @ay-p, @ceejep, @jcv
I had problems, so tried first Created from seed, problems solved, new money appeared Seems fine so far. If using 'screen' to run daemons, be aware you have to input a password on the first run: "[INF] DCRW: Please enter the private wallet passphrase. This will complete syncing of the wallet accounts and then leave your wallet unlocked. You may relock wallet after by calling 'walletlock' through the RPC."
A big thanks to all developers for the continuous improvements on Decred code. @ceejep @_ingsoc Is it recommended with v0.0.10, like it was on v0.0.9 to recreate wallet from seed? Also, I see on the first post of Decred in bitcointalk that currently v0.0.8 is marked as stable and v0.0.10 is marked as unstable(like v0.0.9 was before), why is that? I had wrong balance display return in v0.0.8, what are the main known issues with v0.0.9 and v0.0.10? Yes if it's like v0.0.9 when you recreate wallet from seed you have to enter your private passphrase on the first run of dcrwallet at the same command prompt when prompted to so as for the wallet to unlock first and then start syncing.
I never recreated from seed after an update, well maybe once but it's because I noobed the image on my Raspberry Pi and lost everything. Just replaced the binaries, seems to work ok on my side.
Exactly my thoughts. Thanks. I was asking because many advertise recreating from seed with every new version.
Basically is recommended only to update but if you experience any issues with your wallet you can try re-creating it from seed after making a backup. I had a wrong balance return issue with v0.0.8 and it was only fixed by recreating dcrwallet from seed on v0.0.9. I've just ask @ceejep if re-creating wallet from seed is recommended for v0.0.10 to be more sure, it was recommended for those having balance issues on v0.0.8 for the v0.0.9 update. Is there any link for a compiled version of an updated cgminer version with those improvements?
I notice 0.0.8 is still marked as the latest "stable" version. Should I update a solo-PoS node if I'm not having any issues and don't need any of the new features?
It's up to u. And as 0.0.8 is marked as stable u can remain on it and wait for next stable release. And 0.0.10 should have a lot of bugs fixed as compared to 0.0.8
I've finally updated to v0.0.10 as well with no problems. Also some voting issues I had with v0.0.8 and v0.0.9 seems to be fixed with v0.0.10.
After upgrading to version 0.0.10, this happened: No matching records found! Tx: 18:04:54 2016-04-08 [INF] TMGR: Inserting unconfirmed transaction 94279b2fc7266bb240cec14b4d7d6f9d63ca68b22434a2dfac30304d42d30603 18:04:54 2016-04-08 [INF] WLLT: Successfully sent SStx purchase transaction 94279b2fc7266bb240cec14b4d7d6f9d63ca68b22434a2dfac30304d42d30603 19:09:51 2016-04-08 [INF] TMGR: Inserting unconfirmed transaction 9f17f7e609967cb64fa832f1157307133116174bc27bab2ecfcf24f8462a7029 19:09:51 2016-04-08 [INF] WLLT: Successfully sent SStx purchase transaction 9f17f7e609967cb64fa832f1157307133116174bc27bab2ecfcf24f8462a7029 00:02:16 2016-04-09 [INF] TMGR: Inserting unconfirmed transaction f800284e4d4aa98b1f6fd5f0680b607227593c7f2eeccc1a085e2841d98f454b 00:02:16 2016-04-09 [INF] WLLT: Successfully sent SStx purchase transaction f800284e4d4aa98b1f6fd5f0680b607227593c7f2eeccc1a085e2841d98f454b Any solution? Thank's.
@raphaelsoares can you elaborate, are those tx or funds missing? If tx are missing but funds are ok then its because ticket price went to 7 and there were 2000+ ticket buying tx waiting to get into blocks and some were not included. Meanwhile the ticket price increased and those ticket buying tx which were not yet mined were cancelled and funds returned to wallet.
The balances are right, then what happened was exactly as I said, there was a lot of purchase by the price to be low, so they were canceled. Thank you!
I've succesfully imported a seed but wallet stuck on next run with this messages: Code: $ ./decred_0.0.10/dcrwallet 18:45:18 2016-04-09 [INF] DCRW: Version 0.0.10-alpha 18:45:18 2016-04-09 [INF] DCRW: Generating TLS certificates... 18:45:18 2016-04-09 [INF] DCRW: Done generating TLS certificates 18:45:18 2016-04-09 [WRN] DCRW: Cannot open CA file: open /home/ubuntu/.dcrwallet/dcrd.cert: no such file or directory 18:45:18 2016-04-09 [INF] DCRW: Attempting RPC client connection to localhost:9109 18:45:18 2016-04-09 [INF] RPCS: Listening on 127.0.0.1:9110 : 18:45:19 2016-04-09 [INF] WLLT: No recorded transaction history -- needs full rescan 18:45:19 2016-04-09 [INF] WLLT: Opened wallet 18:45:19 2016-04-09 [INF] DCRW: Please enter the private wallet passphrase. This will complete syncing of the wallet accounts and then leave your wallet unlocked. You may relock wallet after by calling 'walletlock' through the RPC. 18:45:51 2016-04-09 [INF] WLLT: The wallet has been unlocked without a time limit I've checked dcrwallet process and near zero CPU load. Dcrd synced. Ubuntu LTS 64-bit on AWS.
Hello Guys I download the wallet from here : http://cryptomining-blog.com/tag/decred-wallet/ Then I go to : C:\Users\myuser\DecredWallet and config the settings - creating wallet name and password. Then I start the wallet and getting that . Is that normaly? Or I am doing something wrong? Thanks you in advanced!
I'm afraid to update to this from 0.0.8. I have no idea how to rebuild from seed if that proves necessary, plus I have a lot of PoS stakes in progress and I'm concerned those will get screwed up.
Updating is not needed now. 0.0.8 is also shown with STABLE tag. 0.0.10 is shown as UNSTABLE. So you don't need to update now. Once a stable build is released you can do the necessary. And if u need help on how to recreate wallet u can message me. I'll be glad to help you out.