v0.10.16 - Onyx v2

[eduffield]

10.16.6 Onyx V2 - All Users

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

 

[BrainShutdown]

Nodes updated! Looking good :smile:

 

[thelonecrouton]

1st of my MNs updated to 16.6, looking fine, appeared in MN list immediately both local and remote, not a CPU/RAM hog. :smile:

 

[GilAlexander]

Updated, have 33 masternodes in list now.

 

[akhavr]

Stil can see none on neither of my nodes/wallets

 

[fernando]

Updated MNs. Everything seems fine, except for one that doesn't seem to be propagating to the others or local client. I'll wait in case it is normal. I have around 40 masternodes in all lists.

 

[David]

Updated three MNs. One shows other masternodes on the network; the other two don't. Going to wait and see if it's a propagation delay.

EDIT: Propagated to a second masternode. Still waiting on my third. So I'm thinking it's fine!

 

[thelonecrouton]

Stil can see none on neither of my nodes/wallets

Stopping and restarting darkcoind sorted things out for me. I was stuck on 1 in the list. Make sure you're fully synced too.

 

[akhavr]

Stopping and restarting darkcoind sorted things out for me. I was stuck on 1 in the list. Make sure you're fully synced too.

"blocks" : 169634,

now

Restarted darkcoind two times already (during upgrade)

 

[GilAlexander]

Have empty masternode list on both of my windows clients. Linux client looks good. Height is 169637.

 

[maky]

Upgraded to v10.16.5 early morning (and it works fine)
Upgraded to v10.16.6 now (and it works fine too)

 

[djcrypto]

Updated to 10.16.6
Glad I waited a day lol

 

[thelonecrouton]

If our great and wise and beloved leaders could post a quick example of how to get start-many set up it would be greatly appreciated, pretty pretty please. :kiss:

 

[paperThin]

I noticed Even mentioned something about "Darksend request incomplete. Last darksend was too recent". That it would not happen often, but it could still come up under some circumstances and when you first start up.

I am trying to "Mix" and I am getting this "Darksend request incomplete. Last darksend was too recent". Anyone else seeing this continuously? (I have not used my wallet for about a week before opening it today.)

 

[thefrog]

Seems to be running fine now.
EU node: http://eu.p2pool.sk:7903
US node: http://us.p2pool.sk:7903

 

[qwizzie]

I noticed Even mentioned something about "Darksend request incomplete. Last darksend was too recent". That it would not happen often, but it could still come up under some circumstances and when you first start up.

I am trying to "Mix" and I am getting this "Darksend request incomplete. Last darksend was too recent". Anyone else seeing this continuously? (I have not used my wallet for about a week before opening it today.)

i would wait with mixing untill the network has stabilised somewhat.... in a few days the network will be a lot more stabile and up to date.

 

[oaxaca]

I assume that there is still a need for "liquidity providers". Can we get new fangled binaries?

 

[oblox]

I assume that there is still a need for "liquidity providers". Can we get new fangled binaries?

Already included:

v16 supports the --liquidityprovider parameter and start-many command

 

[oaxaca]

Already included:

I missed that, thx.

 

[paperThin]

i would wait with mixing untill the network has stabilised somewhat.... in a few days the network will be a lot more stabile and up to date.

Thanks Quizzie... I will wait a little... I thought the warning was strange, saying "too recent". It seems like it should say something else if the network has not stabilized like... "nodes not found" or "no matching transactions to mix" etc. I will wait a bit, but I am anxious to try out this new hot rod!