I am on the latest wallet, windows-amd64-20160309-01 All of my ticket purchases are being denied. There is a transaction that says is trying to be double spent. on ky transaction: 820ea40bda90bddabf4a035a6efa72d952f3816a4df1d91a3dc39b76b173c61a Here is the message in the wallet: 16:04:24 2016-03-16 [WRN] WLLT: Failed to send raw transaction: -22: TX rejected : transaction 34360c310f9b92104dac170f15bba7ff14f92ef56d1dba2f3d6f47d026f952bb t ried to double spend coins from transaction 820ea40bda90bddabf4a035a6efa72d952f3816a4df1d91a3dc39b76b173c61a 16:04:24 2016-03-16 [WRN] WLLT: A chainSvr error was returned attempting to purc hase a ticket; ticket purchases aborted. I have tried to restart the wallet and the same thing happens. Now all ticket purchases are aborted. Any help and I hope I have this in the correct section.
we've fixed this issue and it will be included in the next release 0.0.8 if you reimport from seed you will no longer see this problem.
Thanks for the quick reply. I can wait it out for the next release. I still have my seed node but don't wont to risk an error on my end.
@ay-p I've been having this issue too. I just reimported from seed and let the wallet sync up, but my balance didn't sync up correctly. I'm using a hot and cold wallet for POS. Before reimporting balance (default 0 all) is around 185. After reimporting with seed and full sync to latest block, my default 0 all balance only shows around 21. I reverted to the old database. Any idea why the balance didn't sync correctly?
OK weird. I just checked, and even though I am getting the double spend error, I somehow bought a ticket...
Creating a wallet using the seed will not work at all, i did it several times without any luck. Yes it doesn't show corrected stats and balance too.
23:48:37 2016-03-16 [INF] WLLT: Connecting block ------OMISSIS-----, height 10977 23:48:37 2016-03-16 [WRN] WLLT: Failed to send raw transaction: -22: TX rejected : transaction ------OMISSIS----- t ried to double spend coins from transaction ------OMISSIS----- 23:48:37 2016-03-16 [WRN] WLLT: A chainSvr error was returned attempting to purc hase a ticket; ticket purchases aborted. 23:59:01 2016-03-16 [INF] WLLT: Connecting block ------OMISSIS-----, height 10978 23:59:01 2016-03-16 [WRN] WLLT: Failed to send raw transaction: -22: TX rejected : transaction ------OMISSIS----- t ried to double spend coins from transaction ------OMISSIS----- 23:59:01 2016-03-16 [WRN] WLLT: A chainSvr error was returned attempting to purc hase a ticket; ticket purchases aborted. 23:59:10 2016-03-16 [INF] WLLT: Connecting block ------OMISSIS-----, height 10979 23:59:10 2016-03-16 [WRN] WLLT: Failed to send raw transaction: -22: TX rejected : transaction ------OMISSIS----- t ried to double spend coins from transaction ------OMISSIS----- 23:59:10 2016-03-16 [WRN] WLLT: A chainSvr error was returned attempting to purc hase a ticket; ticket purchases aborted.
Are you running two wallets or have you deleted and re-created your wallet from the seed, by any chance?
https://github.com/decred/decred-release/releases/tag/v0.0.8 Give this new release a try. May have to recreate from seed. Let me know how it goes.
An important part of the release pertains to address scanning, so I will be rebuilding from seed. Then, consolidate 999999.
I just updated to 0.0.8 and I also have problems with consolidating the inputs. When I do i get the following error: -22: TX rejected: tried to spend zero value output from input a-----PRIVATE----5, idx 2 I haven't rebuilded from the seed since the wallet then is offline and cannot vote, but will this fix the dust problem ?
Yes, I had the same error, and had to rebuild from seed. Then consolidate worked. Just be ready for a large transaction and significant fees, but apparently this is the only way to deal with it presently.
It all depends on the kB of the transaction, which depends on the number of UTXO inputs. I've done two big consolidates on testnet, and the fees were high. Not great if you do this often. There does not seem to be a good solution to this problem. https://github.com/decred/dcrwallet/pull/104#issuecomment-195771808
Try again. First allow dcrd to completely sync BEFORE restoring your wallet. See my post here: https://forum.decred.org/threads/how-to-rebuild-resync-wallet-successfully.1338/