v0.10.17.x Testing

Status
Not open for further replies.
MrMime said:
Got it, no instant confirm yet though.
Click to expand...
Just now:
Status: 1/unconfirmed, broadcast through 1 nodeDate: 11/29/2014 12:10To: mz8ayM31cwpAzFRr2SPk2LTAayWu71reygDebit: -10.00 DRKTransaction fee: -0.001 DRKNet amount: -10.001 DRKTransaction ID: 3cb779aad06570610414333ab1b81aa900696fb8bc926fa31b74749f38d4dddf
 
moli said:
Just now:
Status: 1/unconfirmed, broadcast through 1 nodeDate: 11/29/2014 12:10To: mz8ayM31cwpAzFRr2SPk2LTAayWu71reygDebit: -10.00 DRKTransaction fee: -0.001 DRKNet amount: -10.001 DRKTransaction ID: 3cb779aad06570610414333ab1b81aa900696fb8bc926fa31b74749f38d4dddf
Click to expand...
Sweet, I see it too.
 
moli said:
Just now:
Status: 1/unconfirmed, broadcast through 1 nodeDate: 11/29/2014 12:10To: mz8ayM31cwpAzFRr2SPk2LTAayWu71reygDebit: -10.00 DRKTransaction fee: -0.001 DRKNet amount: -10.001 DRKTransaction ID: 3cb779aad06570610414333ab1b81aa900696fb8bc926fa31b74749f38d4dddf
Click to expand...
That's not an IX. IX's show 1/confirmed at the receive end and txdepth/confirmed at the send end. Still trying to capture a successful one, grrr.
 
thelonecrouton said:
That's not an IX. IX's show 1/confirmed at the receive end and txdepth/confirmed at the send end. Still trying to capture a successful one, grrr.
Click to expand...
Showed up in confirmed total balance about 30 seconds later. Shows unconfirmed in my transactions tab though.
 
My qt wallet just stopped. Last lines of debug. Win 7

Code: 
2014-11-29 17:50:11 dsi -- tx in CTxIn(COutPoint(350328a3084d361041d27c0efe25f6e9f9c984ac301e2a4df109127e77dac043, 0), scriptSig=)
2014-11-29 17:50:11 dsi -- tx in CTxIn(COutPoint(74d7455923b03ae8f894cc78fd49da8477feaa32e6c9de96915d3c47d00aeb2b, 0), scriptSig=)
2014-11-29 18:06:26 socket not sending
2014-11-29 18:06:26 CDarkSendPool::ChargeFees -- found uncooperative node (didn't send transaction). Found offence.
2014-11-29 18:06:26 CDarkSendPool::ChargeFees -- found uncooperative node (didn't send transaction). Found offence.
2014-11-29 18:06:26 socket inactivity timeout
2014-11-29 18:06:26 CDarkSendPool::UpdateState() == 3 | 3
2014-11-29 18:06:26 socket not sending
2014-11-29 18:06:26 disconnecting node [2001:0:5ef5:79fd:18f1:fbff:57c0:68aa]:57722
2014-11-29 18:06:26 disconnecting node 178.62.6.122:19999
2014-11-29 18:06:26 UPnP Port Mapping successful.
2014-11-29 18:06:26 disconnecting node 191.238.80.67:19999
2014-11-29 18:06:26 maxconnections check 248
2014-11-29 18:06:26 accepted connection 94.23.248.61:38036
2014-11-29 18:06:26 socket send error 10054
2014-11-29 18:06:26 disconnecting node 188.226.223.5:19999
 
linux64 MN just crashed, end of debug.log:
Code: 
.darkcoin/testnet3# tail -f debug.log
2014-11-29 18:20:33 signing privkey 932ZyRKNcwwW7ijevLJGMQEEQJxz8cuSM7nig8P5MYTvoQX9uHq
2014-11-29 18:20:33 signing pubkey2 msK3EXq5V6NHthvYKSQCbcAkSdciaPzAxU
2014-11-29 18:20:33 verify strMessage 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7317750
2014-11-29 18:20:33 verify addr 64.251.69.134:19999
2014-11-29 18:20:33 verify addr 108.61.199.31:19999
2014-11-29 18:20:33 verify addr 18 176.126.241.100:19999
2014-11-29 18:20:33 verify pubkey2 msK3EXq5V6NHthvYKSQCbcAkSdciaPzAxU
2014-11-29 18:20:33 InstantX::DoConsensusVote --- connected, sending vote 191.238.52.72:19999
2014-11-29 18:20:33 ProcessMessageInstantX::txlreq - Transaction Lock Request: 109.201.154.208:21535 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 18:20:33 ProcessMessageInstantX::txlreq
 
This was probably reported here but my client does not seem to respect the "darksend rounds to use" setting. I have it set to 4 rounds but many of my denoms have reached 5 or 6 rounds so far.

Win32-qt client.
 
eduffield
kryptofoo said:
This was probably reported here but my client does not seem to respect the "darksend rounds to use" setting. I have it set to 4 rounds but many of my denoms have reached 5 or 6 rounds so far.

Win32-qt client.
Click to expand...

yeah, i noticed it too .. i mentioned it in here some pages back but i'm not sure it got registered as a bug yet. lets keep an eye on it.
 
kryptofoo said:
This was probably reported here but my client does not seem to respect the "darksend rounds to use" setting. I have it set to 4 rounds but many of my denoms have reached 5 or 6 rounds so far.

Win32-qt client.
Click to expand...
Most of my denoms got 9 rounds instead of 8. Maybe it's a buffer overflow problem? But if Evan wants to increase to more than 8 rounds, I'm okay with it. :cool:
 
The amount of hash being thrown at the p2pool testnet node is actually causing that server to crash/drop/hang/lock. I didn't prepare for anywhere near that much hash on that box. I'm not going to bother scaling to box to handle it but maybe we could dial it back a bit? Or point some of it at Evan's mpos pool. I can't seem to find the info for his pool anywhere anyone remember it?
 
Status
Not open for further replies.
Back
Top