• 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.
****** PLEASE UPDATE TO v10.17.4 *******

- Disabled InstantX

17.x includes fixes to the dead change issue, masternode backwards compatibility, a simplier send coins interface and other improvements. It seems like everything is working really well except for InstantX (which is hit and miss), so I'd really like to make sure this release is solid as it stands and push it out to the network.

After we're sure these improvements work, we'll push out the changes and then jump right back into testing InstantX. For InstantX to work properly I need implement proof-of-service and have the masternode network passively scan itself and remove nodes that aren't online (which is causing most of our issues currently).

So let me know if there's anything else that needs to get fixed before release!

--

Windows 32bit:
https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/windows/darkcoind.exe
https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/windows/darkcoin-qt.exe

Mac OS X:
https://github.com/darkcoinproject/...aster/instantx/mac/darkcoin-0.10.17.4-osx.dmg

Linux 32bit:
https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/linux/32/darkcoin-qt
https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/linux/32/darkcoind

Linux 64bit:
https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/linux/64/darkcoin-qt
https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/linux/64/darkcoind
 
eduffield said:
****** PLEASE UPDATE TO v10.17.4 *******

- Disabled InstantX

17.x includes fixes to the dead change issue, masternode backwards compatibility, a simplier send coins interface and other improvements. It seems like everything is working really well except for InstantX (which is hit and miss), so I'd really like to make sure this release is solid as it stands and push it out to the network.

After we're sure these improvements work, we'll push out the changes and then jump right back into testing InstantX. For InstantX to work properly I need implement proof-of-service and have the masternode network passively scan itself and remove nodes that aren't online (which is causing most of our issues currently).

So let me know if there's anything else that needs to get fixed before release!
Click to expand...

there were some problems with darksend rounds exceeding the number they were set with .. has that been looked into and fixed ?

edit : and thanks for this update, trying it out now.
 
my testnet-masternode (linux-vps) was not running anymore when i wanted to stop it before update. Last line in logs are:
2014-11-29 15:28:25 ProcessMessageInstantX::txlreq
2014-11-29 15:28:25 signing strMessage 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7317750
2014-11-29 15:28:25 signing privkey 92CHrSctWvcZVTRQcRhSfeGU1X5YSKKivbQQvRwhic7jKuDxMbr
2014-11-29 15:28:26 signing pubkey2 n4PHV8KGFCasW3Zdn3dRBcGdCD2qH4tE44
2014-11-29 15:28:26 verify strMessage 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7317750
2014-11-29 15:28:26 verify addr 64.251.69.134:19999
2014-11-29 15:28:26 verify addr 108.61.199.31:19999
2014-11-29 15:28:26 verify addr 24 162.243.63.93:19999
2014-11-29 15:28:26 verify pubkey2 n4PHV8KGFCasW3Zdn3dRBcGdCD2qH4tE44
2014-11-29 15:28:26 ProcessMessageInstantX::txlreq - Transaction Lock Request: 87.164.205.225:46102 /Satoshi:0.10.17.2/ : rejected 8f71e00af6bed95d551a175e6207df773ed5db12a147a7b7fbaa53987f78b6a7
2014-11-29 15:28:26 ProcessMessageInstantX::txlreq
Click to expand...
 
v0.10.17.4, Windows wallet:

whenever I start Darksend mixing debug.log says:

DoAutomaticDenominating : No funds detected in need of denominating (2)

This wallet has around 40000 tDRK and already 99/8 (from version v0.10.16.16) denominated tDRK. I tried to denominate first 31 tDRK, now 543 tDRK.
 
Last edited by a moderator:
eduffield said:
****** PLEASE UPDATE TO v10.17.4 *******

- Disabled InstantX

17.x includes fixes to the dead change issue, masternode backwards compatibility, a simplier send coins interface and other improvements. It seems like everything is working really well except for InstantX (which is hit and miss), so I'd really like to make sure this release is solid as it stands and push it out to the network.

After we're sure these improvements work, we'll push out the changes and then jump right back into testing InstantX. For InstantX to work properly I need implement proof-of-service and have the masternode network passively scan itself and remove nodes that aren't online (which is causing most of our issues currently).

So let me know if there's anything else that needs to get fixed before release!

--

Windows 32bit:
https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/windows/darkcoind.exe
https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/windows/darkcoin-qt.exe

Mac OS X:
https://github.com/darkcoinproject/...aster/instantx/mac/darkcoin-0.10.17.4-osx.dmg

Linux 32bit:
https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/linux/32/darkcoin-qt
https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/linux/32/darkcoind

Linux 64bit:
https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/linux/64/darkcoin-qt
https://github.com/darkcoinproject/darkcoin-binaries/raw/master/instantx/linux/64/darkcoind
Click to expand...

Edit:
Hi Evan, seems like 404 not found in Mac OS X
https://github.com/darkcoinproject/darkcoin-binaries/tree/master/instantx
 
Last edited by a moderator:
win7 qt crashed:
Code: 
2014-11-30 00:01:38 AcceptToMemoryPool: 104.131.45.75:19999 /Satoshi:0.10.17.4/ : accepted 4e9eeb252657ad28328c6ac7b90dc89f9e725bf67c7cbf3516577769c3363e54 (poolsz 2)
2014-11-30 00:01:38 CompletedTransaction -- success
2014-11-30 00:01:38 CDarkSendPool::UpdateState() == 5 | 8
2014-11-30 00:01:38 dssu - state: 3 entriesCount: 0 accepted: -1 error:
2014-11-30 00:01:38 dssu - message doesn't match current darksend session 210702 163241
2014-11-30 00:01:38 dssu - state: 3 entriesCount: 0 accepted: -1 error:
2014-11-30 00:01:38 dssu - message doesn't match current darksend session 210702 163241
2014-11-30 00:01:38 Darksend request complete: Transaction Created Successfully
2014-11-30 00:01:38 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:38    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:39 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:39    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:40 Flushing wallet.dat
2014-11-30 00:01:40 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:40    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:41 Flushed wallet.dat 880ms
2014-11-30 00:01:41 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:41    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:41 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:41    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:42 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:42    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:43 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:43    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:44 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:44    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:44 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:44    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:45 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:45    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:46 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:46    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:47 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:47    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:48 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:48    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:48 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:48    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:49 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:49    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
2014-11-30 00:01:50 updateWallet 8c718e781d07dd45e8a193562a9334f0e870a8c2017f8692e0a92865d93a4eaf 1
2014-11-30 00:01:50    inWallet=1 inModel=1 Index=48-49 showTransaction=1 derivedStatus=1
 
I'm probably not understanding how this is supposed to work. But I have on an Ubuntu machine, a wallet with 1000 held for running a masternode, plus another 1000 that is not going to be denominated (but used for change)
On my windows machine, I have denominated funds, and I tried to send 13.54 drk to the Ubuntu address using 2 X 10 coin denominated coins. But I get the error " Unable to locate enough Darksend denominated funds for this transaction.

Back when I denominated these funds, a while ago... can't remember, I had it set for 8 rounds. It stopped around 6 rounds, and I never tried for more as there was a release. Now, I've re-set the rounds to 3. It may not like the change, or may not use higher denominated funds when you've set it lower? I don't know.

Also, I show 41 masternodes online, and yet, it's been over 15 minutes with no confirmation to anything I did send successfully (the faucet) It shows up but no confirmations.
 
eduffield said:
For InstantX to work properly I need implement proof-of-service and have the masternode network passively scan itself and remove nodes that aren't online (which is causing most of our issues currently).
Click to expand...

Does this mean a true hybrid block proof? Where the MNs and the whiminers both have to have some kind of consensus to validate a block?

Seems like IX operates outside of block height confirmation system to which we're accustomed... I'm not even sure how I'd approach handling that...

You might need a more active MN test policy. Ping/comm a MN before/as trying to use it in the lock pool? It seems like the messaging system can be listened to maliciously... As soon as selected, behave poorly, crap on IX... MN would act normally up until the moment it was actually supposed to do something. No real way to monitor for that passively, hell, even actively... No idea how to head that off.

I guess that's why I'm not Evan. :p
 
Last edited by a moderator:
camosoul said:
Does this mean a true hybrid block proof? Where the MNs and the whiminers both have to have some kind of consensus to validate a block?
Click to expand...

Sounds like MN gets booted if acting "poorly" and/or not acting at all - could be wrong
 
Regardless of all that, what's the bottom line changelog from 0.10.16.16 --> 0.10.17.4 look like? What made it? Why do we care about what made it? I didn't even see an announcement for .3's contents.

Not whining. I just want to get some consolidated points. R&D is always messy. I know. But, we know what the unwashed masses think of anything that's not perfectly shrink wrapped... They have no idea.
 
camosoul said:
Regardless of all that, what's the bottom line changelog from 0.10.16.16 --> 0.10.17.4 look like? What made it? Why do we care about what made it? I didn't even see an announcement for .3's contents.

Not whining. I just want to get some consolidated points. R&D is always messy. I know. But, we know what the unwashed masses think of anything that's not perfectly shrink wrapped... They have no idea.
Click to expand...

Yeah I would like to see a week or so of testing before publishing on main net. Some people may not have even checked in yet to see 10.17 is on testnet the more updates and bugs we find here the fewer times the pool police will need to try and get everyone to update.
 
Miner237 said:
Yeah I would like to see a week or so of testing before publishing on main net. Some people may not have even checked in yet to see 10.17 is on testnet the more updates and bugs we find here the fewer times the pool police will need to try and get everyone to update.
Click to expand...
Evan was pretty clear that he was waiting to see how it goes, I don't think 17.4 is pushing to main net right away.

But do we even know what's in it? It's a testament to testnet and Evan that things move so fast, but even in confirmed releases, we can't deny that documentation leaves much to be desired...

I'm just trying to get us out in front of that one before it's too late. Again. Still. ;-)
 
Status
Not open for further replies.
Back
Top