• 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 sent InstantX 55 DRK successfully (received and added to receiver's total balance instantly) .. but transaction details from sender still showed this :

v9byp5y.jpg
 
No crashes yet on 17.2 but I don't think IX is working yet, at least not the way it did in Evan's youtube vid.
Ignition75 said:
I got 3 farms rented at about 100 Mh/s each for the next week or so, just give me the connect details and I'll chuck some hashing power at testnet for you guys.
Click to expand...
People do understand that more hash isn't going to speed anything up, right? It's just going to raise the mining diff.
 
thelonecrouton said:
No crashes yet on 17.2 but I don't think IX is working yet, at least not the way it did in Evan's youtube vid.

People do understand that more hash isn't going to speed anything up, right? It's just going to raise the mining diff.
Click to expand...

it will help now while some blocks are 5 min apart until diff goes up and then yeah it'll still be 5min apart tomorrow

diff is at 2.11 now
 
thelonecrouton said:
No crashes yet on 17.2 but I don't think IX is working yet, at least not the way it did in Evan's youtube vid.

People do understand that more hash isn't going to speed anything up, right? It's just going to raise the mining diff.
Click to expand...

Yeah, but its for a week!! This morning moocowmoo had to turn off his rig, and right during denom and testing X, we got almost a half an hour block, and a few subsequent boring ones too. At least people will be able to join and leave with less DWG retarget variance. Block time should be more stable now.
 
if some of you are using -instantxdepth=6 as commandline in yr shortcut or in yr darkcoin.conf because i mention it yesterday it could explain why it waits for 6 masternode confirmations (InstantX will be slower then), perhaps best to use InstantX on testnet with no -instantxdepth=6 right now........
 
Eh, I think IX might be working, manually setting instantxdepth=20 just got me:

Status: 20 confirmations, broadcast through 1 node - within about 20 secs. But only showing 1 confirm at the other end via listtransactions command.

Yep, holy poop, it definitely seems to be working, it's just the receiver only shows 1 confirm regardless of what you set instantxdepth to at the sending end.

IX: :smile::smile::smile::cool:

edit: bugger, 1st 4 tests at varying instantxdepth worked perfectly, now it seems to have stopped working. :(

Also noticed that when the block changes, the green tick in the client beside a succesful IX tx reverts to a clock showing number of block confirms.
 
Last edited by a moderator:
qwizzie said:
if some of you are using -instantxdepth=6 as commandline in yr shortcut or in yr darkcoin.conf because i mention it yesterday it could explain why it waits for 6 masternode confirmations (InstantX will be slower then)
Click to expand...

Uh, pretty sure that's not the case, or at least shouldn't be. IX speed should be invariant with txdepth.
 
yidakee said:
Yeah, but its for a week!! This morning moocowmoo had to turn off his rig, and right during denom and testing X, we got almost a half an hour block, and a few subsequent boring ones too. At least people will be able to join and leave with less DWG retarget variance. Block time should be more stable now.
Click to expand...
I'm going to bed now, that rental should be fine it's been running OK for over a week, any issues [email protected] I'll get that on my phone, will be up for a bit watching TV.

Good luck with the testing!
 
got a successfull InstantX again but still on sender wallet the transaction shows as :

Status: 0/unconfirmed, has not been successfully broadcast yet
or on receiver wallet :
Status: 0/offline, has not been successfully broadcast yet

Date: 29-11-2014 15:00
To: mtRocRZz8AMsSKEM2eusDJHWLcE3f1ryQg
Debit: -1000.00 DRK
Transaction fee: -0.014 DRK
Net amount: -1000.014 DRK
Transaction ID: 2a4f3d3329d77204aaca37766417191d2f6f0ee760fdfc6af071f6b10e45d95e

but the InstantX did work and instantly.

update :

sender wallet -> Status: 4/unconfirmed, broadcast through 1 node
receiver wallet -> Status: 4/unconfirmed

(this is confirmation by POW .. would love to see a more clear Proof of Service confirmation from the start)
 
Last edited by a moderator:
qwizzie said:
got a successfull InstantX again but still on sender wallet the transaction shows as :

Status: 0/unconfirmed, has not been successfully broadcast yet
or on receiver wallet :
Status: 0/offline, has not been successfully broadcast yet

Date: 29-11-2014 15:00
To: mtRocRZz8AMsSKEM2eusDJHWLcE3f1ryQg
Debit: -1000.00 DRK
Transaction fee: -0.014 DRK
Net amount: -1000.014 DRK
Transaction ID: 2a4f3d3329d77204aaca37766417191d2f6f0ee760fdfc6af071f6b10e45d95e

but the InstantX did work and instantly.

update :

sender wallet -> Status: 4/unconfirmed, broadcast through 1 node
receiver wallet -> Status: 4/unconfirmed
Click to expand...

That's a fail I think. Relaunch your wallet with --instantxdepth=17 or something and you'll see it work properly. You get a green tick with the txdepth visible on mouse-hover straight away.

When it stops working for me after a few go's, relaunching the wallet (with the instantxdepth switch set) seems to get it functioning correctly again. There's a much longer pause between hitting send and the sent notification popup (about 5-10 secs) as it acquires the tx lock. Then it'll show up as confirmed 1 on the receive side a few seconds later, before the block changes.
 
Last edited by a moderator:
Debug logs are being spammed with this: (About four times a second)

debug.log said:
2014-11-29 14:33:12 ProcessMessageInstantX::txlreq
2014-11-29 14:33:12 ProcessMessageInstantX::txlreq - Already Have Transaction Lock Request: 178.62.6.122:19999 /Satoshi:0.10.17.2/ : accepted 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:33:12 ProcessMessageInstantX::txlreq
2014-11-29 14:33:12 ProcessMessageInstantX::txlreq - Already Have Transaction Lock Request: 178.73.223.87:19999 /Satoshi:0.10.17.2/ : accepted 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:33:12 ProcessMessageInstantX::txlreq
2014-11-29 14:33:12 ProcessMessageInstantX::txlreq - Already Have Transaction Lock Request: 104.131.45.75:19999 /Satoshi:0.10.17.2/ : accepted 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:33:13 ProcessMessageInstantX::txlreq
2014-11-29 14:33:13 ProcessMessageInstantX::txlreq - Already Have Transaction Lock Request: 178.73.223.87:19999 /Satoshi:0.10.17.2/ : accepted 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:33:13 ProcessMessageInstantX::txlreq
2014-11-29 14:33:13 ProcessMessageInstantX::txlreq - Already Have Transaction Lock Request: 178.62.6.122:19999 /Satoshi:0.10.17.2/ : accepted 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
Click to expand...
 
Few minutes ago I had IX successfully received and spendable without POW conf. While observing my wallet balance my 22 coins has been deducted from confirmed to unconfirmed :what:.
In this time no block has been found

edit: awaiting block atm
 
InstantX only works if whoever receives it gets it confirmed and spendable. Otherwise it doesn´t make sense. It seems that D+ solves the cosmetic bug and doesn't waint for 1x block to be resolved.

Anyone can confirm an absolutely not-D+ tx is confirmed InstantX without 1x blocks being solved?

(went out for lunch. Whoever sent me 19.9995 tDRK, sorry, was out)
 
Lets try again then. Def not darksend

14:47:18

Status: 0/unconfirmed, has not been successfully broadcast yetDate: 29/11/2014 14:47To: Yidakee ITX mnxWCg8AYtuV5CbQs2LpUnwF6u73Hu9NN4Debit: -10.00 DRKTransaction fee: -0.10000011 DRKNet amount: -10.10000011 DRKTransaction ID: 350328a3084d361041d27c0efe25f6e9f9c984ac301e2a4df109127e77dac043
 
14:51:19 Def not darksent this time!

Status: 0/unconfirmed, has not been successfully broadcast yetDate: 29/11/2014 14:50To: Yidakee ITX mnxWCg8AYtuV5CbQs2LpUnwF6u73Hu9NN4Debit: -10.00 DRKNet amount: -10.00 DRKTransaction ID: f0d7dc41bcd719499ce9c2ca781da02bbf98109cdfadc242a401aa53f6871b99
 
stonehedge said:
Scratch that! That was accidentally darksent!
Click to expand...

So bloody fast didn't even have time to check on the block explorer. Went to check my wallet, already 1 PoW confirm and spendable!

InstantX works! I'm still not convinced thought, that non-D+ tx confirm before next block is found. Otherwise its just cosmetic

Again please!!

EDIT:

Evan, is that you attacking the network? My debug is going bananas!

4-11-29 14:56:24 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:24 ProcessMessageInstantX::txlreq - Transaction Lock Request: 80.240.135.83:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq
2014-11-29 14:56:25 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq - Transaction Lock Request: 80.240.135.83:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq
2014-11-29 14:56:25 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq - Transaction Lock Request: 50.254.73.147:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq
2014-11-29 14:56:25 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq - Transaction Lock Request: 80.240.135.83:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq
2014-11-29 14:56:25 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq - Transaction Lock Request: 81.169.177.196:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq
2014-11-29 14:56:25 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq - Transaction Lock Request: 80.240.135.83:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq
2014-11-29 14:56:25 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq - Transaction Lock Request: 50.254.73.147:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq
2014-11-29 14:56:25 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq - Transaction Lock Request: 80.240.135.83:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq
2014-11-29 14:56:25 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq - Transaction Lock Request: 80.240.135.83:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq
2014-11-29 14:56:25 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq - Transaction Lock Request: 50.254.73.147:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq
2014-11-29 14:56:25 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:25 ProcessMessageInstantX::txlreq - Transaction Lock Request: 80.240.135.83:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq
2014-11-29 14:56:26 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq - Transaction Lock Request: 81.169.177.196:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq
2014-11-29 14:56:26 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq - Transaction Lock Request: 80.240.135.83:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq
2014-11-29 14:56:26 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq - Transaction Lock Request: 50.254.73.147:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:26 Submitted to masternode, waiting in queue .
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq
2014-11-29 14:56:26 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq - Transaction Lock Request: 80.240.135.83:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq
2014-11-29 14:56:26 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq - Transaction Lock Request: 80.240.135.83:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:26 connection timeout
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq
2014-11-29 14:56:26 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq - Transaction Lock Request: 80.240.135.83:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq
2014-11-29 14:56:26 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq - Transaction Lock Request: 81.169.177.196:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq
2014-11-29 14:56:26 InstantX::DoConsensusVote - Not masternode
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq - Transaction Lock Request: 50.254.73.147:19999 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 14:56:26 ProcessMessageInstantX::txlreq
2014-11-29 14:56:26 InstantX::DoConsensusVote - Not masternode
2014-11-2
Click to expand...
 
i think right now InstantX works intermittently, sometimes it gets broadcasted to masternodes and will work instantly .. other times it will not get broadcast to masternodes
and will then be confirmed through POW or doesnt get transmitted to the target wallet at all :

Status: 0/offline, has not been successfully broadcast yet
Date: 29-11-2014 15:57
To: n1dg362PjKjhDhcQzy9KAfxnMZyyAyTpfg
Debit: -750.00 DRK
Transaction fee: -0.008
DRKNet amount: -750.008 DRK
Transaction ID: 629e82dc029d7991465fcbe2a0e16e1ae9d7c378183ff2cdad3c003dcc9bef0d
 
Status
Not open for further replies.
Back
Top