BTW, I get lots of "2014-12-03 22:36:07 DoAutomaticDenominating -- Found unconfirmed denominated outputs, will wait till they confirm to continue."
I moved most inputs to a single one to make debugging more easy, and they all have 17 confirms now.
Edit: how can a "payment to yourself" be not final? I would like to understand why the code in "bool IsConfirmed() const" looks like this:
Edit^2: wallet closed itself again:Code:... for (unsigned int i = 0; i < vWorkQueue.size(); i++) { const CMerkleTx* ptx = vWorkQueue[i]; if (!ptx->IsFinal()) return false; if (ptx->GetDepthInMainChain() >= 1) continue; if (!pwallet->IsFromMe(*ptx)) return false; ...
Code:2014-12-03 22:55:43 NotifyTransactionChanged 0470d16d1a12dd3d074b743b34e7d75dc6a6380ad64fb908c8e1ce042ceecf3e status=0 2014-12-03 22:55:43 updateWallet 0470d16d1a12dd3d074b743b34e7d75dc6a6380ad64fb908c8e1ce042ceecf3e 0 2014-12-03 22:55:43 inWallet=1 inModel=0 Index=7-7 showTransaction=0 derivedStatus=0 2014-12-03 22:55:43 Committing 43 changed transactions to coin database... 2014-12-03 22:55:43 SetBestChain: new best=00000000c17a1350f7f130caf39d45c0fffea58bb6fa993a36575b185298bc1c height=73956 log2_work=46.037533 tx=168383 date=2014-12-03 22:55:32 progress=1.000000 2014-12-03 22:55:43 send last getblocks for 00000000c17a1350f7f130caf39d45c0fffea58bb6fa993a36575b185298bc1c peer=8 2014-12-03 22:55:43 send last getblocks for 00000000c17a1350f7f130caf39d45c0fffea58bb6fa993a36575b185298bc1c peer=2 2014-12-03 22:55:43 send last getblocks for 00000000c17a1350f7f130caf39d45c0fffea58bb6fa993a36575b185298bc1c peer=4 2014-12-03 22:55:44 send last getblocks for 00000000c17a1350f7f130caf39d45c0fffea58bb6fa993a36575b185298bc1c peer=1 2014-12-03 22:55:44 getblocks -1 to 0 limit 500 peer=1 2014-12-03 22:55:45 Flushing wallet.dat 2014-12-03 22:55:45 Flushed wallet.dat 18ms 2014-12-03 22:56:12 Submiting Darksend for 659.000000 DRK 2014-12-03 22:56:12 DoAutomaticDenominating -- Found unconfirmed denominated outputs, will wait till they confirm to continue. 2014-12-03 22:57:11 Flushed 56 addresses to peers.dat 5ms 2014-12-03 22:57:13 Submiting Darksend for 659.000000 DRK 2014-12-03 22:57:13 DoAutomaticDenominating -- Found unconfirmed denominated outputs, will wait till they confirm to continue. 2014-12-03 22:57:18 CDarkSendPool::UpdateState() == 3 | 3 2014-12-03 22:58:13 Submiting Darksend for 659.000000 DRK 2014-12-03 22:58:13 DoAutomaticDenominating -- Found unconfirmed denominated outputs, will wait till they confirm to continue. 2014-12-03 22:58:51 addcon thread interrupt 2014-12-03 22:58:51 dumpaddr thread stop 2014-12-03 22:58:51 opencon thread interrupt 2014-12-03 22:58:51 msghand thread interrupt 2014-12-03 22:58:51 net thread interrupt 2014-12-03 22:58:51 Shutdown : In progress... 2014-12-03 22:58:51 Flush(false) 2014-12-03 22:58:51 DBFlush(false) ended 1ms 2014-12-03 22:58:51 StopNode() 2014-12-03 22:58:51 Flushed 56 addresses to peers.dat 7ms 2014-12-03 22:58:51 Committing 32 changed transactions to coin database... 2014-12-03 22:58:51 Flush(true) 2014-12-03 22:58:51 wallet.dat refcount=0 2014-12-03 22:58:51 wallet.dat checkpoint 2014-12-03 22:58:51 wallet.dat detach 2014-12-03 22:58:51 wallet.dat closed 2014-12-03 22:58:51 DBFlush(true) ended 15ms 2014-12-03 22:58:51 Shutdown : done
Wallet run for the complete night without crash, but there's still this "DoAutomaticDenominating -- Found unconfirmed denominated outputs, will wait till they confirm to continue." bug.
In other words, it's not possible to denominate with this wallet for me.
But that won't solve the problem main-net users could have in the same situation.I'd just start a fresh. Send your coins to me and ill send them back once you have got a new wallet
myy263emYeyaFTZYSKWDS4sRKPWUezDzfb
Its a bug from previous test updates, mainnet users shouldn't have this problem. Only testneter'sBut that won't solve the problem main-net users could have in the same situation.
Checked MN status[email protected]:~$ conflict with in-memory transaction : COutPoint(ce6cfd56a2de948ecf32e6dd079f788ebeda25f9aa531b980e9e6f43ee50f67f, 0)
conflict with in-memory transaction : COutPoint(4988e4674fe4acbc713a663da0c15150d83979a9950b6b6405292e6d3bebec89, 11)
conflict with in-memory transaction : COutPoint(8c8ef20087b25e525087f59e2e01dc3febb17e194bd0cfaeefc8bf2eec90e560, 1)
Which is not true, this is a hot wallet, and got the message straight after}
[email protected]:~$ ./darkcoind masternode debug
masternode started remotely
[email protected]:~$ conflict with in-memory transaction : COutPoint(d6158f6ffabdf50ebdaa71d050048054ae89798bd12b2fbfe23be3b00c06a85f, 0)
Thats the thing, the daemon did not crash. When I updated, debug said "no problems found" so I "masternode start" locally.You get the 'masternode started remotely' when it starts itself, not just when you start it yourself from a remote wallet. Other thing I have no idea, I grepped for it but didn't find any such string in the debug.log of mine.
zap it ... --zapwallettxesI also have the 9.74 sitting in unconfirmed in one of my wallets.
There's two "modes" of the darksend pool now,I'm curious why DS is now going over in rounds vs before it wasn't. If it's capped at 8 rounds, we definitely shouldn't be seeing 9's. Likewise, if you specify 4 rounds and end up with 5 or 6s, it's not following your inputs.
EDIT: I do see two more commits today on the instantx branch for stopping and max rounds, although the max rounds set to 2 seems odd, unless this is strictly to test whether people are going over in a shorter period of time before reverting.
Did you find why some 9s were appearing?There's two "modes" of the darksend pool now,
1.) Rounds 0 to 1 - where it allows change and new denominations to be created
2.) Rounds 2 to 8 - where ONLY denominations should go in and come out.
Collateral fees are charged for 1 in 50 sessions, so that seems normal.got my first collateral fee on 1 of 6 wallets .. i'm keeping an eye on the wallets to check for more collateral fees. Sent email to Evan, so far its just 1 collateral fee.