• 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.
Just started Darksend on my windows wallet (v0.10.17.12) and got the message "Darksend request incomplete: Last darksend was too recent. Will retry..." within seconds. Here's the debug log:

Code:
2014-12-03 01:48:08 Submiting Darksend for 198.000000 DRK
2014-12-03 01:48:08 DoAutomaticDenominating -- attempt 1 connection to masternode 95.85.1.197:19999
2014-12-03 01:48:08 trying connection 95.85.1.197:19999 lastseen=15249.7days
2014-12-03 01:48:08 connected 95.85.1.197:19999
2014-12-03 01:48:08 send version message: version 70050, blocks=73459, us=98.249.61.234:19999, them=95.85.1.197:19999, peer=17
2014-12-03 01:48:09 keypool added key 1003, size=1001
2014-12-03 01:48:09 keypool reserve 3
2014-12-03 01:48:09 keypool keep 3
2014-12-03 01:48:09 DoAutomaticDenominating --- connected, sending dsa for 15 - denom 15
2014-12-03 01:48:09 trying connection 211.99.224.237:19999 lastseen=0.2days
2014-12-03 01:48:09 Added time data, samples 15, offset -1 (+0 minutes)
2014-12-03 01:48:09 nTimeOffset = -1  (+0 minutes)
2014-12-03 01:48:09 receive version message: /Satoshi:0.10.17.12/: version 70050, blocks=73459, us=98.249.61.234:61054, them=95.85.1.197:19999, peer=17
2014-12-03 01:48:09 send initial getblocks peer=17
2014-12-03 01:48:09 getblocks -1 to 0 limit 500 peer=17
2014-12-03 01:48:09 CDarkSendPool::UpdateState() == 3 | 3
2014-12-03 01:48:09 CDarkSendPool::UpdateState() == 3 | 7
2014-12-03 01:48:09 CDarkSendPool::StatusUpdate - entry not accepted by masternode
2014-12-03 01:48:09 Darksend request incomplete: Last darksend was too recent. Will retry...
2014-12-03 01:48:11 Flushing wallet.dat
2014-12-03 01:48:11 Flushed wallet.dat 187ms
2014-12-03 01:48:14 connection timeout
2014-12-03 01:48:14 trying connection 97.79.231.162:19999 lastseen=0.2days
2014-12-03 01:48:19 connection timeout
2014-12-03 01:48:19 Darksend is idle
 
Just started Darksend on my windows wallet (v0.10.17.12) and got the message "Darksend request incomplete: Last darksend was too recent. Will retry..." within seconds. Here's the debug log:

Code:
2014-12-03 01:48:08 Submiting Darksend for 198.000000 DRK
2014-12-03 01:48:08 DoAutomaticDenominating -- attempt 1 connection to masternode 95.85.1.197:19999
2014-12-03 01:48:08 trying connection 95.85.1.197:19999 lastseen=15249.7days
2014-12-03 01:48:08 connected 95.85.1.197:19999
2014-12-03 01:48:08 send version message: version 70050, blocks=73459, us=98.249.61.234:19999, them=95.85.1.197:19999, peer=17
2014-12-03 01:48:09 keypool added key 1003, size=1001
2014-12-03 01:48:09 keypool reserve 3
2014-12-03 01:48:09 keypool keep 3
2014-12-03 01:48:09 DoAutomaticDenominating --- connected, sending dsa for 15 - denom 15
2014-12-03 01:48:09 trying connection 211.99.224.237:19999 lastseen=0.2days
2014-12-03 01:48:09 Added time data, samples 15, offset -1 (+0 minutes)
2014-12-03 01:48:09 nTimeOffset = -1  (+0 minutes)
2014-12-03 01:48:09 receive version message: /Satoshi:0.10.17.12/: version 70050, blocks=73459, us=98.249.61.234:61054, them=95.85.1.197:19999, peer=17
2014-12-03 01:48:09 send initial getblocks peer=17
2014-12-03 01:48:09 getblocks -1 to 0 limit 500 peer=17
2014-12-03 01:48:09 CDarkSendPool::UpdateState() == 3 | 3
2014-12-03 01:48:09 CDarkSendPool::UpdateState() == 3 | 7
2014-12-03 01:48:09 CDarkSendPool::StatusUpdate - entry not accepted by masternode
2014-12-03 01:48:09 Darksend request incomplete: Last darksend was too recent. Will retry...
2014-12-03 01:48:11 Flushing wallet.dat
2014-12-03 01:48:11 Flushed wallet.dat 187ms
2014-12-03 01:48:14 connection timeout
2014-12-03 01:48:14 trying connection 97.79.231.162:19999 lastseen=0.2days
2014-12-03 01:48:19 connection timeout
2014-12-03 01:48:19 Darksend is idle

That message means that current MN (the one your wallet tried to send new mixing request to) refuses to serve another new DS queue until at least 20% of other MNs serve some DS queues. Wallet will try to find another MN on next attempt automatically after it gets this response.
 
That message means that current MN (the one your wallet tried to send new mixing request to) refuses to serve another new DS queue until at least 20% of other MNs serve some DS queues. Wallet will try to find another MN on next attempt automatically after it gets this response.
So I guess it's not a problem? When does this become a problem? when we get too many of them too often? I guess this is solved now? Thanks :)
 
So I guess it's not a problem? When does this become a problem? when we get too many of them too often? I guess this is solved now? Thanks :)
There are few places where this condition apply but the logic is smth like this (as I understand): MN checks that it doesn't serve too much of network mixing requests (this helps to spread load) while client (and it has similar checks on its side) checks that it doesn't mix too frequent on same MNs (and this helps to keep things private for user).
 
My wallet was rolling along with DS denoms, then suddenly got hit with a collateral PTY 0.1 fee, and then got another DS denom but it hasn't been confirmed for the last 40 minutes... In the debug log it says:

Code:
2014-12-03 03:47:36 Submiting Darksend for 61.000000 DRK
2014-12-03 03:47:36 DoAutomaticDenominating -- Found unconfirmed denominated outputs, will wait till they confirm to continue.

EDIT: This tx showed message in testnet explorer as
"Hash: 3a8e909495e41fc743451c5cea331f9e6221b366a501b3e5dc5f79a880188ad2
Sorry, I don't know about that chain!"

Moocowmoo and Oblox helped me in IRC with -zapwallettxes. Problem solved!
 
Last edited by a moderator:
Was the rounds ever fixed for going into 9 or over from the targeted rounds? Further, any thoughts on making the default 8 rounds instead of 2 since fees are no longer per round?
 
Was the rounds ever fixed for going into 9 or over from the targeted rounds? Further, any thoughts on making the default 8 rounds instead of 2 since fees are no longer per round?
I'm still getting 9 rounds... :)

upload_2014-12-3_0-21-23.png
 
i'm getting transactions without ''type'' and collateral fees on pretty much all running wallets,
have sent 5 debug.logs to Evan with pics of transaction timestamps.

xoVQzcx.jpg
 
Last edited by a moderator:
2000/4 all night, its 10am right now. Up to height but last confirm was at 4:48 am. It seems the QT freezes updating the wallet. Going to zap

tKN1bDw.png


Sure enough, got rid of the other ones, but strange that the 4:57am tx still comes up as 3/6 .. how can this be, its now 10am? (now 4/6)
7a18e8e65b500e349b0f09d131a5aa4107377ab9d3e47e57760b5f241eae8fb0

SXgmvJz.png
 
I also have a bunch of blank tx's and seven 0.10 charges in a row over a three hour period. Debug.log is 9MB+ though.
 
I also have a bunch of blank tx's and seven 0.10 charges in a row over a three hour period. Debug.log is 9MB+ though.
Same here. I also have an "Unconfirmed: 8.79999915 DRK" that would not go away, without any DS Denom or PTY fee stuck on the Transaction screen.

upload_2014-12-3_9-32-44.png
 
Same here. I also have an "Unconfirmed: 8.79999915 DRK" that would not go away, without any DS Denom or PTY fee stuck on the Transaction screen.

View attachment 676
Anything stuck with 0 confirms should be nuked with the zapwallettxs argument if blocks are being found and you aren't getting any additional confirms that the tx is making it into a block.
 
Anything stuck with 0 confirms should be nuked with the zapwallettxs argument if blocks are being found and you aren't getting any additional confirms that the tx is making it into a block.
OH.. Haha... I thought I got no unconfirmed tx's on the transaction screen but just looked at it again and realized I got these:

upload_2014-12-3_9-49-48.png


I just woke up, haven't got any coffee yet.... Time for some delicious coffee!!! :grin:
 
Off topic, but since you are talking coffee, get yourself an aeropress if you haven't already got one. Makes the best damn coffee ever.

I know the creator of the aeropress, good guy. I had a cup out of mine within the last hour.

Really Off Topic - Buy fresh certified organic beans using DRK. PM for details...
 
I know the creator of the aeropress, good guy. I had a cup out of mine within the last hour.

Really Off Topic - Buy fresh certified organic beans using DRK. PM for details...
PM for detail? You need to make a thread in "Merchants" and post the website for this. :smile:
 
PM for detail? You need to make a thread in "Merchants" and post the website for this. :smile:

It's on my to-do list... Way too busy roasting at the moment.

EDIT - setting up a test masternode and test solo mining seemed like a higher priority.
 
Status
Not open for further replies.
Back
Top