• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

v0.10.16 - Onyx v2

eduffield

eduffield

Core Developer
10.16.16 Onyx V2 - All Users

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.16-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.16-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.16.16-linux.tar.gz


10.16.6 : Fixed memory issues
10.16.10 : Fixed remote masternode issues
10.16.11 : Fixed darksend definitions
10.16.12 : Fixed mixing issues
10.16.15 : Reduced collateral charges by 90%
10.16.16 : Mixing should be much faster
 
Last edited by a moderator:
D

David

New member
Just updated, but the command:

./darkcoind masternode list

...shows nothing. Not mine, not anybody elses!
 
D

David

New member
oblox said:
Did you masternode start from local?
Click to expand...

No. Is this one of those updates? I hate it when I have to dig out my cold wallets and do all that crap...why do some updates require that? I never have understood it!

P.S. I now see 3 MNs on the list...none of them are mine though =(
 
mattmct

mattmct

New member
If it's a new protocol does this mean the new clients won't be able to talk to the old? Also will there have to be a new p2pool software version?

Cheers!
 
oblox

oblox

New member
David said:
No. Is this one of those updates? I hate it when I have to dig out my cold wallets and do all that crap...why do some updates require that? I never have understood it!
Click to expand...
Because it has a protocol bump. Anytime the protocol changes, you need to masternode start from local.
 
JGCMiner

JGCMiner

New member
Evan, will you update the liquidity provider to this new version?

With the lower fees it is now more attractive to provide mixing liquidity.
 
spatula

spatula

New member
Foundation Member
I seem to be having issues with my masternodes showing up in the list. When i start from the wallet it says its successful.
 
spatula

spatula

New member
Foundation Member
spatula said:
I seem to be having issues with my masternodes showing up in the list. When i start from the wallet it says its successful.
Click to expand...

Also, to add to this, if a start a masternode, its own IP shows up in the masternode list that I pull from itself or from the local wallet, but is not included on the masternode list of any of my other nodes.
 
DrkMiner

DrkMiner

New member
spatula said:
I seem to be having issues with my masternodes showing up in the list. When i start from the wallet it says its successful.
Click to expand...

Yes, same issue. I'm updating few nodes. After restart they don't show on the list.

grep HotCold .darkcoin/debug.log Doesn't return result.
 
flare

flare

New member
spatula said:
I seem to be having issues with my masternodes showing up in the list. When i start from the wallet it says its successful.
Click to expand...
DrkMiner said:
Yes, same issue. I'm updating few nodes. After restart they don't show on the list.
Click to expand...
Same here: after update and "masternode start" i get no

Code: 
"CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon."

on 50% of my nodes, whereas the starting wallet returns "start successful"
 
oblox

oblox

New member
Yeah, definitely having issues getting MN's to appear in the list even with stopping them. I have initiated the masternode start from local numerous times and they will not get into the list. I have only managed to get a few on the list thus far. Never had issues before.
 
DrkMiner

DrkMiner

New member
Since v16 supports the "start-many command" is there a guide on how to use it?

Would like to consolidate all the wallets into one.

Thanks!
 
flare

flare

New member
Checked back with Evan: The issues with MN startup will level out as network updates. Currently the startup messages (dsee) do not propagated properly through the network. This is due to lots of nodes updating / being outdated :)
 
thelonecrouton

thelonecrouton

New member
Foundation Member
flare said:
Checked back with Evan: The issues with MN starting will level out as network updates. Currently the startup messages (dsee) do not propagated properly through the network. This is due to lot's of nodes updating :)
Click to expand...
Hope so, thought I was getting even dafter... :eek:
 
You must log in or register to reply here.
Top