v0.10.16 - Onyx v2

jiggytom said:
Are you saying Darksend transactions are traceable? Is it a bug or something else?
Click to expand...
I'm going to be doing another test after work. Evan said it was able to be found because it was initiated before all his updates although the whole starting balance was shifted to a new address around release 16.4-16.5 iirc when the exclusion of fees took place. But even then, it's also important to realize that it wasn't a first guess. It was only after multiple guesses and confirmations that it wasn't the right address that it was determined.
 
Last edited by a moderator:
oblox said:
I'm going to be doing another test after work. Evan said it was able to be found because it was initiated before all his updates although the whole starting balance was shifted to a new address around release 16.4-16.5 iirc when the exclusion of fees took place.
Click to expand...
Hmmm so try again oblox with new DS tx :) and have fun on new 10.16.16 ver
 
So send to a new address then mix again from scratch? Let's all mix and try on a few transactions, Be interesting doing a speed test with the new version anyway.
 
Last edited by a moderator:
darkwing said:
So send to a new address then mix again from scratch? Let's all mix and try on a few transactions, Be interesting doing a speed test with the new version anyway.
Click to expand...
Correct. I'll be doing 8 rounds again so hopefully there will be some denominations for me in a few hours.
 
do masternodes going inactive around the 1hr 10mark cause a concern? Mine went to 0 status, then disappeared, then came back on..all by itsself. Issue? Gonna try stopping, deleting peers.dat and restarting.

edit...okay it all started up fine. Didn't get the "not capable" this time when trying to masternode start on the remote node. Let's see what happens...
 
Last edited by a moderator:
oblox said:
http://pastebin.com/fQP5cGM5

UdjinM6 eduffield

Any ideas on why I have yet to get any progress? Cleared peers.dat, tried stopping and restarting, closed client and reopened, nadda.
Click to expand...

I'm not very familiar with darksend part of code yet but this looks suspicious:
Code: 
2014-11-20 00:43:14 dssu - state: 3 entriesCount: 0 accepted: -1 error: 
2014-11-20 00:43:14 dssu - message doesn't match current darksend session 734543 0
2014-11-20 00:43:14 dssu - state: 2 entriesCount: 0 accepted: 1 error: 
2014-11-20 00:43:14 CDarkSendPool::UpdateState() == 3 | 2
2014-11-20 00:43:14 CDarkSendPool::StatusUpdate - set sessionID to 0
 
UdjinM6 said:
I'm not very familiar with darksend part of code yet but this looks suspicious:
Code: 
2014-11-20 00:43:14 dssu - state: 3 entriesCount: 0 accepted: -1 error:
2014-11-20 00:43:14 dssu - message doesn't match current darksend session 734543 0
2014-11-20 00:43:14 dssu - state: 2 entriesCount: 0 accepted: 1 error:
2014-11-20 00:43:14 CDarkSendPool::UpdateState() == 3 | 2
2014-11-20 00:43:14 CDarkSendPool::StatusUpdate - set sessionID to 0
Click to expand...
Here's some more (first time I saw an obsolete error):

2014-11-20 01:05:26 Added 349 addresses from 108.61.123.164: 19 tried, 9692 new
2014-11-20 01:05:27 Submitted to masternode, waiting in queue .
2014-11-20 01:05:27 Added 385 addresses from 108.61.123.164: 19 tried, 9699 new
2014-11-20 01:05:27 Added 47 addresses from 108.61.123.164: 19 tried, 9707 new
2014-11-20 01:05:31 received block 00000000000761009e5ca699eb7d2cece0127996621e0feaa988de4177dd6a2a peer=5
2014-11-20 01:05:31 Committing 995 changed transactions to coin database...
2014-11-20 01:05:31 SetBestChain: new best=00000000000761009e5ca699eb7d2cece0127996621e0feaa988de4177dd6a2a height=172542 log2_work=60.479725 tx=661409 date=2014-11-20 01:03:58 progress=0.999999
2014-11-20 01:05:31 Closing masternode connection 107.170.249.98:9999
2014-11-20 01:05:31 disconnecting node 107.170.249.98:9999
2014-11-20 01:05:31 send last getblocks for 00000000000761009e5ca699eb7d2cece0127996621e0feaa988de4177dd6a2a peer=8
2014-11-20 01:05:31 send last getblocks for 00000000000761009e5ca699eb7d2cece0127996621e0feaa988de4177dd6a2a peer=18
2014-11-20 01:05:31 send last getblocks for 00000000000761009e5ca699eb7d2cece0127996621e0feaa988de4177dd6a2a peer=1
2014-11-20 01:05:31 send last getblocks for 00000000000761009e5ca699eb7d2cece0127996621e0feaa988de4177dd6a2a peer=4
2014-11-20 01:05:32 mnw - winning vote CTxIn(COutPoint(62bb47bb939a5f27512688d3062da8119792af457d2aacd821dd6bd434a25417, 1), scriptSig=) Height 172552 bestHeight 172542
2014-11-20 01:05:32 send last getblocks for 00000000000761009e5ca699eb7d2cece0127996621e0feaa988de4177dd6a2a peer=10
2014-11-20 01:05:32 getblocks -1 to 0 limit 500 peer=7
2014-11-20 01:05:32 ProcessSyncCheckpoint: sync-checkpoint at 0000000000052f8a0258d79aae675e6bc956873429e2e8f4ff3c0165e7084df1
2014-11-20 01:05:32 getblocks -1 to 0 limit 500 peer=10
2014-11-20 01:05:37 socket send error 10053
2014-11-20 01:05:37 disconnecting node 46.63.26.63:43536
2014-11-20 01:05:37 dseep - Couldn't find masternode entry CTxIn(COutPoint(afb2f5f629ce195c3c17e8e63a15f8971546c76f727a1991ef0d2b349ce4e970, 0), scriptSig=)
2014-11-20 01:05:37 dseep - Asking source node for missing entry CTxIn(COutPoint(afb2f5f629ce195c3c17e8e63a15f8971546c76f727a1991ef0d2b349ce4e970, 0), scriptSig=)
2014-11-20 01:05:37 dsee - Got NEW masternode entry 108.61.193.91:9999
2014-11-20 01:05:37 dsee - Accepted masternode entry 1004 1004
2014-11-20 01:05:44 Submitted to masternode, waiting in queue ..
2014-11-20 01:05:47 Submitted to masternode, waiting in queue ...
2014-11-20 01:05:48 maxconnections check 117
2014-11-20 01:05:48 accepted connection [2001:0:9d38:6abd:b9:6aa:b81e:8e1a]:63563
2014-11-20 01:05:48 dseep - Couldn't find masternode entry CTxIn(COutPoint(5203ff9e346b2e41a6af6ba45215935f53eb5c4ad5fa8d0cdb7f23460999cbfb, 1), scriptSig=)
2014-11-20 01:05:48 dseep - Asking source node for missing entry CTxIn(COutPoint(5203ff9e346b2e41a6af6ba45215935f53eb5c4ad5fa8d0cdb7f23460999cbfb, 1), scriptSig=)
2014-11-20 01:05:48 partner [2001:0:9d38:6abd:b9:6aa:b81e:8e1a]:63563 using obsolete version 70038; disconnecting
2014-11-20 01:05:48 ProcessMessage(version, 105 bytes) FAILED
2014-11-20 01:05:48 disconnecting node [2001:0:9d38:6abd:b9:6aa:b81e:8e1a]:63563
2014-11-20 01:05:48 dsee - Got NEW masternode entry 108.61.222.216:9999
2014-11-20 01:05:48 dsee - Accepted masternode entry 994 994
2014-11-20 01:05:50 dseep - Couldn't find masternode entry CTxIn(COutPoint(a3ad41ffed9984ca3e486340434adcdd65afcd42155446844a8cdd5dc9c2174f, 1), scriptSig=)
2014-11-20 01:05:50 dseep - Asking source node for missing entry CTxIn(COutPoint(a3ad41ffed9984ca3e486340434adcdd65afcd42155446844a8cdd5dc9c2174f, 1), scriptSig=)
2014-11-20 01:05:50 dseep - Couldn't find masternode entry CTxIn(COutPoint(a3ad41ffed9984ca3e486340434adcdd65afcd42155446844a8cdd5dc9c2174f, 1), scriptSig=)
2014-11-20 01:05:50 dsee - Got NEW masternode entry 108.61.198.83:9999
2014-11-20 01:05:50 dsee - Accepted masternode entry 993 993
2014-11-20 01:05:51 Submitted to masternode, waiting in queue .
2014-11-20 01:06:07 Flushed 9726 addresses to peers.dat 105ms
2014-11-20 01:06:08 Submitted to masternode, waiting in queue ..
2014-11-20 01:06:11 AcceptToMemoryPool: 23.92.53.39:9999 /Satoshi:0.10.16.6/ : accepted 617a727f3e483d39c1228b3d76c6688a51563ba4b4b46be6605150ef6ccdb2e7 (poolsz 3)
2014-11-20 01:06:11 AcceptToMemoryPool: 108.61.123.164:9999 /Satoshi:0.10.16.16/ : accepted 2d9954dd66e7cba76b817c37d21fe5a626ed7b36879da70dd6d22e0ceb43e312 (poolsz 4)
2014-11-20 01:06:11 Submitted to masternode, waiting in queue ...
2014-11-20 01:06:15 Submitted to masternode, waiting in queue .
2014-11-20 01:06:26 Removing inactive masternode 192.99.135.204:9999
2014-11-20 01:06:26 Removing inactive masternode 108.61.193.91:9999
2014-11-20 01:06:26 Removing inactive masternode 108.61.222.216:9999
2014-11-20 01:06:26 Removing inactive masternode 108.61.198.83:9999
2014-11-20 01:06:32 Submitted to masternode, waiting in queue ..
2014-11-20 01:06:33 dseep - Couldn't find masternode entry CTxIn(COutPoint(a3ad41ffed9984ca3e486340434adcdd65afcd42155446844a8cdd5dc9c2174f, 1), scriptSig=)
2014-11-20 01:06:33 dseep - Asking source node for missing entry CTxIn(COutPoint(a3ad41ffed9984ca3e486340434adcdd65afcd42155446844a8cdd5dc9c2174f, 1), scriptSig=)
2014-11-20 01:06:34 dsee - Got NEW masternode entry 108.61.198.83:9999
2014-11-20 01:06:34 dsee - Accepted masternode entry 992 992
2014-11-20 01:06:36 Submitted to masternode, waiting in queue ...
2014-11-20 01:06:38 dseep - Couldn't find masternode entry CTxIn(COutPoint(afb2f5f629ce195c3c17e8e63a15f8971546c76f727a1991ef0d2b349ce4e970, 0), scriptSig=)
2014-11-20 01:06:38 dseep - Asking source node for missing entry CTxIn(COutPoint(afb2f5f629ce195c3c17e8e63a15f8971546c76f727a1991ef0d2b349ce4e970, 0), scriptSig=)
2014-11-20 01:06:38 dsee - Got NEW masternode entry 108.61.193.91:9999
2014-11-20 01:06:38 dsee - Accepted masternode entry 1003 1003
2014-11-20 01:06:39 maxconnections check 117
2014-11-20 01:06:39 accepted connection 104.156.230.164:57260
2014-11-20 01:06:39 partner 104.156.230.164:57260 using obsolete version 70038; disconnecting
2014-11-20 01:06:39 ProcessMessage(version, 108 bytes) FAILED
2014-11-20 01:06:39 disconnecting node 104.156.230.164:57260
2014-11-20 01:06:39 Submitted to masternode, waiting in queue .
2014-11-20 01:06:39 AcceptToMemoryPool: 108.61.199.69:9999 /Satoshi:0.10.16.16/ : accepted 56465913deca815252a8b84da055840a65e57761571df0532c147a900017a919 (poolsz 5)
2014-11-20 01:06:46 dseg - Sending master node entry - 54.68.136.22:9999
2014-11-20 01:06:46 dseg - Sending master node entry - 54.171.242.37:9999
Click to expand...
 
oblox said:
Here's some more (first time I saw an obsolete error):
Click to expand...
Nothing wrong here, wallet simply drops connections from other wallets that run too old version

And it looks like messages from previous post mean that there was a timeout on masternode trying to process some Darksend actions... Not sure why though..
Btw, I'm running mixing on testnet and looks like it works there...

Will try to find out if there an issue but give me more time to dive deep into Darksend code - it's 2K+ lines there related to Darksend only :)
 
UdjinM6 said:
Nothing wrong here, wallet simply drops connections from other wallets that run too old version

And it looks like messages from previous post mean that there was a timeout on masternode trying to process some Darksend actions... Not sure why though..
Btw, I'm running mixing on testnet and looks like it works there...

Will try to find out if there an issue but give me more time to dive deep into Darksend code - it's 2K+ lines there related to Darksend only :)
Click to expand...
I figured that was the case. Strange because the 10.16.15 worked fine and usually had a PTY within minutes of turning Darksend on. I was really looking forward to the faster Darksend that Evan was referring to but so far I am not have any luck. Still bouncing between idle and in queue.
 
You must log in or register to reply here.
Back
Top