• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

v0.10.17.x Testing

Status
Not open for further replies.
Hmm...Now my wallet has been getting hit with blank type transactions and "Unconfirmed 9.77499906 DRK"

upload_2014-12-4_0-7-32.png


upload_2014-12-4_0-8-40.png


Why do we keep getting these blank transactions? And it seems some of them might be stuck on the block chain again.

Edit: All blank transactions got confirmed.
 
Last edited by a moderator:
some more wallets finished with the input amounts exactly 8 rounds (not exceeding them) and reaching 100 % :

nr 1 :

Darksend Balance : 554
Amount set : 990

nr 2 :

Darksend Balance : 454
Amount set : 990

nr 3 :

Darksend Balance : 744
Amount set : 990

I found no further collateral fees and also no blank transactions (transactions without ''type'')
 
I am really excited about this code and where it is at. I sometimes get frustrated when things on testnet don't go as planned but then I realize I need to step back and realize this is what testnet is for. Figuring out the things we need to and tweaking all the things that needs tweaking. I am excited at how robust the ds+ code base has become after all the people looking it over. Thanks to everyone for all their hardwork testing and hardening the code! May the dark be with you!
 
Nice - darksend is working again and is fast in v101717. No longer getting any blank transactions or strange error messages in v101717. Just a few nuisance items perhaps:

When I am anonymizing 2000 tdrk 4 rounds, I still have a lot of denoms going through 5 or 6 rounds. My completion bar reads 100% completion too early because of this.

In the 32bit windows-qt client starting with early versions of 1017xx and continuing in v101717, anytime a transaction is being created (darksend mixing or just sending funds) the CPU gets pegged and the client becomes unresponsive for maybe 15-20 seconds. This happened sporadically in my v1016xx clients but now it happens every time, even during darksend mixing. I have a decent PC (i5, 8gb) so not a huge problem but folks with crappy machines may have more of an issue with this.
 
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.

crowning said:
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:

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;
...

Edit^2: wallet closed itself again:
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
Click to expand...
 
crowning said:
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.
Click to expand...


I'd just start a fresh. Send your coins to me and ill send them back once you have got a new wallet

myy263emYeyaFTZYSKWDS4sRKPWUezDzfb
 
crowning said:
But that won't solve the problem main-net users could have in the same situation.
Click to expand...

Its a bug from previous test updates, mainnet users shouldn't have this problem. Only testneter's

Edit: Had four denominations in an hour, will post a pic of 8 Rounds.
 
Last edited by a moderator:
v17 working much better for me than recent previous builds. Only issue I've noticed is the progress bar getting to 100% way too soon, but the process carries on and pretty close to your specified amount end up anon'd. Had two 0.1 charges in the course of anon'ing 1700DRK.
 
My 2000/4 denom finished, but exceeded the requested anon funds. Also it seems (and I'm just guessing) that once it finished, pty got stuck.
Sending the funds to the faucet and starting fresh, this was a previous version wallet. deleting the entire testnet3 folder but keeping debug.log just in case requested. A few 5 rounds, but the rest very nice and tidy all 4's, no less.

3DzWTEU.png


qvobjsj.png
 
On another note, left my tMN shell open, and got this message, never seen this happen before.

yidakee@install:~$ conflict with in-memory transaction : COutPoint(ce6cfd56a2de948ecf32e6dd079f788ebeda25f9aa531b980e9e6f43ee50f67f, 0)
conflict with in-memory transaction : COutPoint(4988e4674fe4acbc713a663da0c15150d83979a9950b6b6405292e6d3bebec89, 11)
conflict with in-memory transaction : COutPoint(8c8ef20087b25e525087f59e2e01dc3febb17e194bd0cfaeefc8bf2eec90e560, 1)
Click to expand...

Checked MN status

}
yidakee@install:~$ ./darkcoind masternode debug
masternode started remotely
yidakee@install:~$ conflict with in-memory transaction : COutPoint(d6158f6ffabdf50ebdaa71d050048054ae89798bd12b2fbfe23be3b00c06a85f, 0)
Click to expand...

Which is not true, this is a hot wallet, and got the message straight after
 
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.
 
thelonecrouton said:
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.
Click to expand...

Thats the thing, the daemon did not crash. When I updated, debug said "no problems found" so I "masternode start" locally.

.
 
Oops now I'm getting a bunch of blank transactions and collateral charges. Actually it seems darksend mixing should be completed, I have already reached the target rounds and amount, but it keeps on going with these blank TXs and collateral charges.

upload_2014-12-4_12-42-45.png
 
@10.17.17 mining @3,8MHs + solo CPU and denominating 1500/8
 
Last edited by a moderator:
My wallet completed denom.

I have coins at 8 and 9 rounds.

Also, the denom is 100% but i keep getting ---payment to yourself--- 0.10.
 
My wallet finished up fine, so I sent 1000 back to the faucet, stuck the remaining 700 in a new address, and so far (3 hrs) it hasn't denominated the new 700 lump at all, I just get a periodic 'submitted to mn / waiting in queue' which never gets accepted. Tried restarting the wallet, same behaviour. May just be lack of participants, but it shouldn't need anyone else to denominate?

edit: finally denominated after 4 hrs! :)
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top