search

dashpay / dash

Dash - Reinventing Cryptocurrency
https://www.dash.org
MIT License
1.49k stars 1.2k forks source link

Privatesend bad math #815

Closed Comodore125 closed 8 years ago

Comodore125 commented 8 years ago

2016-05-27

According to coin control all is right. Before, I had mixed for more rounds and changed it just for 2000/2

UdjinM6 commented 8 years ago

I don't get it. Where is it "bad" exactly?

Comodore125 commented 8 years ago

Denominated inputs have 2 of 2 round on average. But it says different things. I even checked coin control.

UdjinM6 commented 8 years ago

hmm... I don't see how this could be possible... Pls sort coin control list by Rounds and see if there are any inputs with rounds less than 2 (ignore n/a).

Comodore125 commented 8 years ago

they are not. that is why I opened an issue.

UdjinM6 commented 8 years ago

hmm.. maybe there are some stuck unconfirmed?

Comodore125 commented 8 years ago

In the wallet, there are three conflicted PrivateSend Denominate. They are from the time before 70200 protocol. I just used recovery (n 1) and wallet is closing for many minutes while it does not uses CPU resources or HDD resources in that time. I am killing the process now.

bertlebbert commented 8 years ago

@Comodore125 I also had unconfirmed in a mixing wallet (70200 protocol) and had to 'kill process' after trying to use Repair options. When restarting the wallet, I added -zapwallettxes=1 to its shortcut and that worked (cleared those pesky 'unconfirmed').

Comodore125 commented 8 years ago

I got this even when I start with that -zapwallettxes=1 in powershell

thelazier commented 8 years ago

Please try with the latest one for windows from https://dashpay.atlassian.net/builds/browse/DASHW-DEV-494/artifact possibly add -reindex and -zapwallettxes=1 should help.

Comodore125 commented 8 years ago

All is wel now. I just dont get why zapwallettxes=1 turned on in wallet corrupted the wallet software?