- Jun 8, 2014
Same issue here -- seems like the coins are being mixed, but the number of rounds doesn't increase past 1 so denomination goes on forever. Has someone told Evan about this?
Have you tried changing your Darksend rounds to 1 in the settings? Several of us have had hung transactions and used that method to clear thing up... at least until Evan can address the problem.Ok so now it's been FIVE hours since last denominate transaction was created and it is still not confirmed. Where did it go wrong?
Now it says "darkSend Status => ERROR : missing input tx information" and is doing nothing. It tries to use that last transaction to denominate further, but it's not on the blockchain so i guess it just failsTry setting it back to the default 2. Maybe that will restart the denomination process and the coins will unlock.
Until the rounds issue is fixed, I would leave it on 2 until all your inputs in "coin control" show darksend rounds =1 AND no coins are unconfirmed and then switch it back to 1. That process worked for me.Changed it back to 2 rounds and now it seems to be moving again.
If it is not on the blockchain then you may be having the same problem Camo was having on bitcointalk.Now it says "darkSend Status => ERROR : missing input tx information" and is doing nothing. It tries to use that last transaction to denominate further, but it's not on the blockchain so i guess it just fails
Tried it and --salvagewallet returns only 500 drk instead of 623.6.Until the rounds issue is fixed, I would leave it on 2 until all your inputs in "coin control" show darksend rounds =1 AND no coins are unconfirmed and then switch it back to 1. That process worked for me.
If it is not on the blockchain then you may be having the same problem Camo was having on bitcointalk.
I still don´t know how it works. Can someone please explain tom me.Does that mean your MN ( which is updated ) only get payments from pools that also have updated or doesn´t it matter which version they are running as long as your MN is on latest version ?
118735 was paid to a MN still running RC3 because that pool is still running RC3 and 118731 was paid to you instead of the other MN I think because there was some dispute in the voting, this time you got lucky but it can go either way.
It seems this problem was reported a couple times on bitcointalk as well. As I posted on those forums:mine has stopped again. Gets to a new Darksend Denominate transaction and just sits at 0/6 confirmations and nothing happens.
--> http://jira.darkcoin.qa/browse/DRK-141) Darksend rounds > 1 never finishes denomination for a number of users (myself included)
--> http://jira.darkcoin.qa/browse/DRK-52) Handful of users aren't seeing their transactions confirmed and be included in the blockchain -- this results in the coins getting stuck.
I expect Evan to take care of these in the next day or two.
Splawik21, mind leading the "pool police" thread this time? with and updated list of who's confirmed updated and who's not. Then we can all chip in and send word out to the pools.
I don't know if anyone has answered, as I'm trying to catch up with the posts.... However, if you close your wallet and re-open it, I'm sure it'll show the correct balance. Since it's still happening, we should put it down as a bug perhaps?In the interests of science I tried unlocking 80DRK worth of inputs and sending them to one of my MNs but thankfully it wouldn't let me, so hopefully just a cosmetic issue and not a showstopper...
edit:changed DS+ rounds from 2 to 1 and the original 44DRK (it was actually 44. something) are now showing as anonymised but the wallet still thinks it has another 44 -