[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[Lebubar]

16.8 showing more signs of life, at least on drk.mn - active duration 33m and last seen 2m ago. Local wallet offline. Will see what happens in another 30 mins.

Yeah, I think v16.8 will fix 90%+ of the clients that can't keep active. Masternodes should also set maxconnections=100+ in their configuration, if v16.8 is the fix that will have an impact as well.

always had
maxconnections=256
in all my conf.

for the moment it's ok. the one with local wallet offline, go unlisted and then appeared listed again...
Will inform later.

Edit. just turned offline local wallet of MN6...

[TanteStefana2]

using 16.8 on both remote and server plus I deleted peers.dat file but I get inbound port not open (but it is!  always has been!) on my local and not capable masternode on my server instead of the usual debug message before you start remote.  what could have changed?  Thanks for any help!

[Lebubar]

using 16.8 on both remote and server plus I deleted peers.dat file but I get inbound port not open (but it is!  always has been!) on my local and not capable masternode on my server instead of the usual debug message before you start remote.  what could have changed?  Thanks for any help!

If I remember you already had this "masternode not capable" when you update to 16.6?
Something happen to your 1000drk? (mixing or something)

[TanteStefana2]

using 16.8 on both remote and server plus I deleted peers.dat file but I get inbound port not open (but it is!  always has been!) on my local and not capable masternode on my server instead of the usual debug message before you start remote.  what could have changed?  Thanks for any help!

If I remember you already had this "masternode not capable" when you update to 16.6?
Something happen to your 1000drk? (mixing or something)

Last time I tried starting the masternode locally with the daemon, but it didn't work.  I switched to QT and it did work.  Right now, I'm trying to start with QT.

Even so, I think something is wrong with my server darkcoind daemons because after a fresh start, they no longer give the old message when I try "masternode debug"  They say right away "not capable masternode"  It's like they close the door on me ;P

Could it have something to do with the ports?  I just checked my local router's firewall and it is open for the computer I use to start the masternodes.  Plus nothing has changed (checked local machine's ip address, still the same.

I appreciate the help, thanks!

[g4q34g4qg47ww]

using 16.8 on both remote and server plus I deleted peers.dat file but I get inbound port not open (but it is!  always has been!) on my local and not capable masternode on my server instead of the usual debug message before you start remote.  what could have changed?  Thanks for any help!

I got this too and it stumped me. Mine started doing this on version 7, will try on 8.

[onetime]

[TanteStefana2]

using 16.8 on both remote and server plus I deleted peers.dat file but I get inbound port not open (but it is!  always has been!) on my local and not capable masternode on my server instead of the usual debug message before you start remote.  what could have changed?  Thanks for any help!

I got this too and it stumped me. Mine started doing this on version 7, will try on 8.

Humm, I just lowered maxconnections to 100 from 256, but no help (per something I read from Evan above...)

I hope Evan hasn't left for the day yet!  LOL

[Lebubar]

using 16.8 on both remote and server plus I deleted peers.dat file but I get inbound port not open (but it is!  always has been!) on my local and not capable masternode on my server instead of the usual debug message before you start remote.  what could have changed?  Thanks for any help!

I got this too and it stumped me. Mine started doing this on version 7, will try on 8.

Humm, I just lowered maxconnections to 100 from 256, but no help (per something I read from Evan above...)

I hope Evan hasn't left for the day yet!  LOL

Personnaly to check if port open I do :
telnet  IP  9999

You should see some hieroglyph.
The message from Evan say to put 100+ (so must be higher than 100)

[g4q34g4qg47ww]

using 16.8 on both remote and server plus I deleted peers.dat file but I get inbound port not open (but it is!  always has been!) on my local and not capable masternode on my server instead of the usual debug message before you start remote.  what could have changed?  Thanks for any help!

I got this too and it stumped me. Mine started doing this on version 7, will try on 8.

Humm, I just lowered maxconnections to 100 from 256, but no help (per something I read from Evan above...)

I hope Evan hasn't left for the day yet!  LOL

Personnaly to check if port open I do :
telnet  IP  9999

You should see some hieroglyph.
The message from Evan say to put 100+ (so must be higher than 100)

I use a different method for checking ports but its wide open just like its always been, max connections set at 256 in the conf. I only updated an already working MN so it's not like starting from scratch, hadn't changed any firewall settings.

[toknormal]

********** Trading Alert - Post Revaluation Analysis **********

Pleased to see that people are availing themselves of Dark Elevator's stopping by to pick up passengers. Click here for more info on Dark elevator.

On demand: 26115 DRK shot
Available: 6482 DRK shot

Notice how despite people still pissing about with masternode issues etc. the price is now buoyant. Thats because we've had our rights of passage/ price compression phase and technical issues are now "allowed" to occur / be addressed on an ongoing basis without adversely impacting the valuation.

No-one should underestimate the significance of this. We are now getting into Bitcoin territory in terms of confidence. Regardless of how much initial "hype" it gets, almost every cryptocoin project falls flat on it's face during that "rights of passage" phase, never to be seen again. Only a tiny number get through it.

Darkcoin is now one of them.

Make no mistake. Back on May 7th, Darkcoin closed its first 3-day trading period above 0.0045 BTC. At that time the valuation was purely speculative pump/dump mania. But consolidation and subsequent intensive technical development has since done justice to that valuation and it's now solid. Our nearest competitor is a factor of 4 market cap away.

Just sayin - for those of you who get frustrated that fundamentals don't reflect in price. Don't loose faith. It isn't just a question of price. Valuation is a whole different dimension. A hard packed price of 45 is way more elusive than a baloon at 6 times that because as I've just pointed out, most never get to the "hard packed" stage.

The other appealing thing about this project is its market priority. It is trying to do one thing and one thing well. Markets like that. They don't like products which try to be all things to everybody. The 2-tier approach is working. The business model that supports that approach is also working (even though I was sceptical at the time. I didn't think we'd get 1000+ masternodes just like that. My jaw is on the floor).

Look at this growth chart. Look at the volume bars below the valuation profile. It shows that people are holding this coin.

We need to remember that price can change on just a tiny amount of volume or it can change on big volume. During the big DRK revaluation around RC2, volume went in and stayed in. There's probably been a significant natural profit take and change of hands of the coin supply since then, but overall we couldn't have asked for a more healthy growth profile.

Where we are right now is a very good breakout level. All lights are green, ship has steered a correct course on fundamentals and market profile reflects this. 2-tier approach is endorsed by the market and we are experiencing *** "healthy coin syndrome" ***. Whether breakout occurs tomorrow or in weeks/ months is I don't know but I'd say whatever this coin is doing - keep doing it !



By contrast, lets look at an unhealthy growth profile. We can see that not only did the price drop but people ** didn't hold the coin **. Thats what makes the difference. Declining price doesn't mean that people are dumping, it just means that market demand is less than market supply, but the market can be small or large compared to the overall coin supply.

[TanteStefana2]

using 16.8 on both remote and server plus I deleted peers.dat file but I get inbound port not open (but it is!  always has been!) on my local and not capable masternode on my server instead of the usual debug message before you start remote.  what could have changed?  Thanks for any help!

I got this too and it stumped me. Mine started doing this on version 7, will try on 8.

Humm, I just lowered maxconnections to 100 from 256, but no help (per something I read from Evan above...)

I hope Evan hasn't left for the day yet!  LOL

Personnaly to check if port open I do :
telnet  IP  9999

You should see some hieroglyph.
The message from Evan say to put 100+ (so must be higher than 100)

I use a different method for checking ports but its wide open just like its always been, max connections set at 256 in the conf. I only updated an already working MN so it's not like starting from scratch, hadn't changed any firewall settings.

Same here, and yes, it's open    Well it's open in my settings but telnet host 9999 says it's closed.  I don't know why.

[thelonecrouton]

16.8 crapped out for me right on the 60 minute mark. Maybe it will resurrect itself like Lebubar's?  

[TanteStefana2]

Notice how despite people still pissing about with masternode issues etc. the price is now buoyant.

Hey!  I resemble that remark!  LOL.  Seriously, it seems like we go up when bitcoin goes down.  Which it has been doing again...  It's like traders run from one side of the boat to the other and the one that runs first gets the most movement / pump, LOL.

But carry on, I still find that market analysis fascinating

[Lukas_Jackson]

using 16.8 on both remote and server plus I deleted peers.dat file but I get inbound port not open (but it is!  always has been!) on my local and not capable masternode on my server instead of the usual debug message before you start remote.  what could have changed?  Thanks for any help!

If I remember you already had this "masternode not capable" when you update to 16.6?
Something happen to your 1000drk? (mixing or something)

Last time I tried starting the masternode locally with the daemon, but it didn't work.  I switched to QT and it did work.  Right now, I'm trying to start with QT.

Even so, I think something is wrong with my server darkcoind daemons because after a fresh start, they no longer give the old message when I try "masternode debug"  They say right away "not capable masternode"  It's like they close the door on me ;P

Could it have something to do with the ports?  I just checked my local router's firewall and it is open for the computer I use to start the masternodes.  Plus nothing has changed (checked local machine's ip address, still the same.

I appreciate the help, thanks!

Last time when I had it, I loaded firewall.sh again from root, or restarted a vps and then loaded again. Don't remember.

Did you sent 1000 to another addy? If yes wait 15 confirmation if I remember good

[Lebubar]

Notice how despite people still pissing about with masternode issues etc. the price is now buoyant.

lol
If the masternode network don't work your price will not buoyant (thanks I learn a new english word) very long...

[qwizzie]

what does -masternodeaddr=<n> exactly do ? Can i use this from inside cold wallet to check upon a
hot wallet ip address ? See its status ?

[TanteStefana2]

using 16.8 on both remote and server plus I deleted peers.dat file but I get inbound port not open (but it is!  always has been!) on my local and not capable masternode on my server instead of the usual debug message before you start remote.  what could have changed?  Thanks for any help!

If I remember you already had this "masternode not capable" when you update to 16.6?
Something happen to your 1000drk? (mixing or something)

Last time I tried starting the masternode locally with the daemon, but it didn't work.  I switched to QT and it did work.  Right now, I'm trying to start with QT.

Even so, I think something is wrong with my server darkcoind daemons because after a fresh start, they no longer give the old message when I try "masternode debug"  They say right away "not capable masternode"  It's like they close the door on me ;P

Could it have something to do with the ports?  I just checked my local router's firewall and it is open for the computer I use to start the masternodes.  Plus nothing has changed (checked local machine's ip address, still the same.

I appreciate the help, thanks!

Last time when I had it, I loaded firewall.sh again from root, or restarted a vps and then loaded again. Don't remember.

Did you sent 1000 to another addy? If yes wait 15 confirmation if I remember good

Nope, didn't change anything, I'm sure it's the ports.  Could you please explain how to reload the firewall.sh?

[innergy]

Ok great great:

I upgrade my 6 MN with v16.8

(the #5 and #6 still listed after more than 2 hours, MN5 got unlisted but temporatry and re-appear without doing anything...)
lebubar@108:~$ ./grepMN.sh
MN1
    "108.x.x.x:9999" : 1,
MN2
    "104.x.x.x:9999" : 1,
MN3
    "108.x.x.x:9999" : 1,
MN4
    "108.x.x.x:9999" : 1
MN5
    "108.x.x.x:9999" : 1,
MN6
    "128.x.x.x:9999" : 1,

I think we are good

Wait 10 more minutes..

[TanteStefana2]

Ok great great:

I upgrade my 6 MN with v16.8

(the #5 and #6 still listed after more than 2 hours, MN5 got unlisted but temporatry and re-appear without doing anything...)
lebubar@108:~$ ./grepMN.sh
MN1
    "108.x.x.x:9999" : 1,
MN2
    "104.x.x.x:9999" : 1,
MN3
    "108.x.x.x:9999" : 1,
MN4
    "108.x.x.x:9999" : 1
MN5
    "108.x.x.x:9999" : 1,
MN6
    "128.x.x.x:9999" : 1,

I think we are good

Wait 10 more minutes..

Still all good..
lebubar@108:~$ date ; ./grepMN.sh
Sat Nov 15 21:54:43 UTC 2014
MN1
    "108.x.x.x:9999" : 1,
MN2
    "104.x.x.x:9999" : 1,
MN3
    "108.x.x.x:9999" : 1,
MN4
    "108.x.x.x:9999" : 1
MN5
    "108.x.x.x:9999" : 1,
MN6
    "128.x.x.x:9999" : 1,

ElCrouton did your's revive?

Did you compile darkcoind yourself?  That's my next step I guess...

[Lukas_Jackson]

using 16.8 on both remote and server plus I deleted peers.dat file but I get inbound port not open (but it is!  always has been!) on my local and not capable masternode on my server instead of the usual debug message before you start remote.  what could have changed?  Thanks for any help!

If I remember you already had this "masternode not capable" when you update to 16.6?
Something happen to your 1000drk? (mixing or something)

Last time I tried starting the masternode locally with the daemon, but it didn't work.  I switched to QT and it did work.  Right now, I'm trying to start with QT.

Even so, I think something is wrong with my server darkcoind daemons because after a fresh start, they no longer give the old message when I try "masternode debug"  They say right away "not capable masternode"  It's like they close the door on me ;P

Could it have something to do with the ports?  I just checked my local router's firewall and it is open for the computer I use to start the masternodes.  Plus nothing has changed (checked local machine's ip address, still the same.

I appreciate the help, thanks!

Last time when I had it, I loaded firewall.sh again from root, or restarted a vps and then loaded again. Don't remember.

Did you sent 1000 to another addy? If yes wait 15 confirmation if I remember good

Nope, didn't change anything, I'm sure it's the ports.  Could you please explain how to reload the firewall.sh?

I think I restarted vps. If you didn't change anything, then:
chmod +x ./firewall.sh
./firewall.sh