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

[splawik21]

masternode | list grep is working. I dont have any problem for this. And result is "1"

I have problem only on drk.mn and Chaeplin's Masternode Monitoring...

I did update yesterday, and had the same issue. Now it is no longer listed on both monitoring sites.
I was selected as payee but it was marked as not detected and payment goes to another node.
( Block 154541 )

MN is still running, grep my ip gives me a one.

I had this in the past and did wait 7 days without payment before i deceided to set up a new IP.

Any ideas what to do and why it is delisted on both MN ?

you've updated but 12h ago multipool.us didn't. They found the block so you missed the payout.
They are on right wallet now.

The monitoring by drk.mn iis on wrong version so it makes ppl confuse...

What confuses me is that after update more than 12h it was shown on chaplins servive.
Now it dissapeared also on his site.

To calm you down I can tell you that some of my MNs gets down too for a couple of hours. Just relax and take a bud

[dotnetmin]

masternode | list grep is working. I dont have any problem for this. And result is "1"

I have problem only on drk.mn and Chaeplin's Masternode Monitoring...

I did update yesterday, and had the same issue. Now it is no longer listed on both monitoring sites.
I was selected as payee but it was marked as not detected and payment goes to another node.
( Block 154541 )

MN is still running, grep my ip gives me a one.

I had this in the past and did wait 7 days without payment before i deceided to set up a new IP.

Any ideas what to do and why it is delisted on both MN ?

you've updated but 12h ago multipool.us didn't. They found the block so you missed the payout.
They are on right wallet now.

The monitoring by drk.mn iis on wrong version so it makes ppl confuse...

What confuses me is that after update more than 12h it was shown on chaplins servive.
Now it dissapeared also on his site.

To calm you down I can tell you that some of my MNs gets down too for a couple of hours. Just relax and take a bud

What value has your masternode count momentary ?   536 ?

[Laxdude7691]

MN is still running, grep my ip gives me a one.

I had this in the past and did wait 7 days without payment before i deceided to set up a new IP.

"masternode list" with YOUR Masternode version (hopefully 0.10.15.13) is what the pools and other Masternodes with THIS version also see, so it's the most reliable way to find out what's going on.

Unfortunately pools with older versions will still pay Masternodes with older versions, but since more and more pools update that will have lesser impact in the near future.

And, as soon as enforcement to 0.10.15.13 kicks in they will completely disappear anyway...

So is the 504 count the number of MN running 10.15.13? If I was still running 10.14.1 would the same command give me a count for that version? One last question on drk.mn page the total MN's shows 773...Is this a bug or did we lose a bunch of MN's? Thanks...

[Icebucket]

Did anyone else check out Onyx after updating ...Slam!
https://www.youtube.com/watch?v=7ADgCeYJMN4

Havent checked them out in over a decade now.. oldschool stuff 

[eahmadov]

The last Twit on miningpoolhub's account is dated September 22 I don't think those guys are gonna upgrade to ONYX. Probably chilaxing in some island in Pacific

[Minotaur26]

We need to give people a few days to update, I am away for the weekend for example and stopped my nodes until I get a chance to update early next week. It would be ideal that everybody updates right away but that is not possible  since people may be busy.

Another factor is pools need to update so running the previous masternode version is no longer profitable, remember pools in the previous version pay masternodes in the previous version so the network needs time I think two weeks is reasonable.

MN is still running, grep my ip gives me a one.

I had this in the past and did wait 7 days without payment before i deceided to set up a new IP.

"masternode list" with YOUR Masternode version (hopefully 0.10.15.13) is what the pools and other Masternodes with THIS version also see, so it's the most reliable way to find out what's going on.

Unfortunately pools with older versions will still pay Masternodes with older versions, but since more and more pools update that will have lesser impact in the near future.

And, as soon as enforcement to 0.10.15.13 kicks in they will completely disappear anyway...

So is the 504 count the number of MN running 10.15.13? If I was still running 10.14.1 would the same command give me a count for that version? One last question on drk.mn page the total MN's shows 773...Is this a bug or did we lose a bunch of MN's? Thanks...

[Laxdude7691]

We need to give people a few days to update, I am away for the weekend for example and stopped my nodes until I get a chance to update early next week. It would be ideal that everybody updates right away but that is not possible  since people may be busy.

Another factor is pools need to update so running the previous masternode version is no longer profitable, remember pools in the previous version pay masternodes in the previous version so the network needs time I think two weeks is reasonable.

MN is still running, grep my ip gives me a one.

I had this in the past and did wait 7 days without payment before i deceided to set up a new IP.

"masternode list" with YOUR Masternode version (hopefully 0.10.15.13) is what the pools and other Masternodes with THIS version also see, so it's the most reliable way to find out what's going on.

Unfortunately pools with older versions will still pay Masternodes with older versions, but since more and more pools update that will have lesser impact in the near future.

And, as soon as enforcement to 0.10.15.13 kicks in they will completely disappear anyway...

So is the 504 count the number of MN running 10.15.13? If I was still running 10.14.1 would the same command give me a count for that version? One last question on drk.mn page the total MN's shows 773...Is this a bug or did we lose a bunch of MN's? Thanks...

I understand if people are unable to update right away but no matter the version or if active or inactive is the total count on drk.mn correct? Showing 772 now...

[crowning]

So is the 504 count the number of MN running 10.15.13? If I was still running 10.14.1 would the same command give me a count for that version? One last question on drk.mn page the total MN's shows 773...Is this a bug or did we lose a bunch of MN's? Thanks...

"masternode count" with 0.10.15.13 gives you the current number of 10.15.13 Masternodes, but the number isn't reliable right know because some of them (ALL of mine  ) have the issue to temporarily go inactive and you have to give them a loving kick in the nuts from time to time.

0.10.14.1 (which I also monitor) is COMPLETELY confused, some 0.10.15.13 Masternodes show up there, some not, some temporarily, and of course the 0.10.14.1 Masternodes.

This will become better when more Masternodes and pools have updated, I hope it will not last TOO long...

BTW, drk.mn still uses the old version, therefore the numbers are wrong.

[fernando]

We need to give people a few days to update, I am away for the weekend for example and stopped my nodes until I get a chance to update early next week. It would be ideal that everybody updates right away but that is not possible  since people may be busy.

Another factor is pools need to update so running the previous masternode version is no longer profitable, remember pools in the previous version pay masternodes in the previous version so the network needs time I think two weeks is reasonable.

MN is still running, grep my ip gives me a one.

I had this in the past and did wait 7 days without payment before i deceided to set up a new IP.

"masternode list" with YOUR Masternode version (hopefully 0.10.15.13) is what the pools and other Masternodes with THIS version also see, so it's the most reliable way to find out what's going on.

Unfortunately pools with older versions will still pay Masternodes with older versions, but since more and more pools update that will have lesser impact in the near future.

And, as soon as enforcement to 0.10.15.13 kicks in they will completely disappear anyway...

So is the 504 count the number of MN running 10.15.13? If I was still running 10.14.1 would the same command give me a count for that version? One last question on drk.mn page the total MN's shows 773...Is this a bug or did we lose a bunch of MN's? Thanks...

No reason to stop them. I haven't had the chance to update either, but there is no harm in leaving them running meanwhile. In fact, I have received some payments while they wait to be updated.

[supporter]

Guys - I hava a question - is it safe to transfer what masternode earns to another wallet and still have masternode active?

[fernando]

Guys - I hava a question - is it safe to transfer what masternode earns to another wallet and still have masternode active?

Yes, but use the inputs control so you don't take any funds from the 0 address. That one needs to one one input of 1000 DRK or the masternode will stop working.

[splawik21]

Guys - I hava a question - is it safe to transfer what masternode earns to another wallet and still have masternode active?

yes
use coincontrol u can activate it in options. Than sento and do list select all but dont tick 1000input

[Minotaur26]

We need to give people a few days to update, I am away for the weekend for example and stopped my nodes until I get a chance to update early next week. It would be ideal that everybody updates right away but that is not possible  since people may be busy.

Another factor is pools need to update so running the previous masternode version is no longer profitable, remember pools in the previous version pay masternodes in the previous version so the network needs time I think two weeks is reasonable.

MN is still running, grep my ip gives me a one.

I had this in the past and did wait 7 days without payment before i deceided to set up a new IP.

"masternode list" with YOUR Masternode version (hopefully 0.10.15.13) is what the pools and other Masternodes with THIS version also see, so it's the most reliable way to find out what's going on.

Unfortunately pools with older versions will still pay Masternodes with older versions, but since more and more pools update that will have lesser impact in the near future.

And, as soon as enforcement to 0.10.15.13 kicks in they will completely disappear anyway...

So is the 504 count the number of MN running 10.15.13? If I was still running 10.14.1 would the same command give me a count for that version? One last question on drk.mn page the total MN's shows 773...Is this a bug or did we lose a bunch of MN's? Thanks...

No reason to stop them. I haven't had the chance to update either, but there is no harm in leaving them running meanwhile. In fact, I have received some payments while they wait to be updated.

In my case  I am moving my masternodes to Flare's masternode hosting service but that means I need to move the 1000DRK to a new vin and coordinate with him so stopping them is necessary for me. There may be multiple reasons.

By the way, if you have 1000DRK consider using Flare's service , is excellent and he charges a fixed monthly fee not a percentage. He also charges no extra coins for setup since he does it himself and is completely trustless you keep your coins in a cold wallet.

[g4q34g4qg47ww]

Did anyone else check out Onyx after updating ...Slam!
https://www.youtube.com/watch?v=7ADgCeYJMN4

Havent checked them out in over a decade now.. oldschool stuff 

Been waitin for someone to crack that one hahahah.

[splawik21]

We need to give people a few days to update, I am away for the weekend for example and stopped my nodes until I get a chance to update early next week. It would be ideal that everybody updates right away but that is not possible  since people may be busy.

Another factor is pools need to update so running the previous masternode version is no longer profitable, remember pools in the previous version pay masternodes in the previous version so the network needs time I think two weeks is reasonable.

MN is still running, grep my ip gives me a one.

I had this in the past and did wait 7 days without payment before i deceided to set up a new IP.

"masternode list" with YOUR Masternode version (hopefully 0.10.15.13) is what the pools and other Masternodes with THIS version also see, so it's the most reliable way to find out what's going on.

Unfortunately pools with older versions will still pay Masternodes with older versions, but since more and more pools update that will have lesser impact in the near future.

And, as soon as enforcement to 0.10.15.13 kicks in they will completely disappear anyway...

So is the 504 count the number of MN running 10.15.13? If I was still running 10.14.1 would the same command give me a count for that version? One last question on drk.mn page the total MN's shows 773...Is this a bug or did we lose a bunch of MN's? Thanks...

No reason to stop them. I haven't had the chance to update either, but there is no harm in leaving them running meanwhile. In fact, I have received some payments while they wait to be updated.

In my case  I am moving my masternodes to Flare's masternode hosting service but that means I need to move the 1000DRK to a new vin and coordinate with him so stopping them is necessary for me. There may be multiple reasons.

By the way, if you have 1000DRK consider using Flare's service , is excellent and he charges a fixed monthly fee not a percentage. He also charges no extra coins for setup since he does it himself and is completely trustless you keep your coins in a cold wallet.

Fully reccomend!
Would be nicer if Flare could use different hosting providers.

[Lukas_Jackson]

Can someone post link to thread on drktalk about looking for a developers? I couldn't find it.

I will try to get someone.

[fernando]

Can someone post link to thread on drktalk about looking for a developers? I couldn't find it.

I will try to get someone.

I think you are talking about this:
https://darkcointalk.org/threads/call-for-devs-software-adoption.2195/

There is already a python dev working on Electrum and looking into Open Bazaar.

[oblox]

masternode | list grep is working. I dont have any problem for this. And result is "1"

I have problem only on drk.mn and Chaeplin's Masternode Monitoring...

I did update yesterday, and had the same issue. Now it is no longer listed on both monitoring sites.
I was selected as payee but it was marked as not detected and payment goes to another node.
( Block 154541 )

MN is still running, grep my ip gives me a one.

I had this in the past and did wait 7 days without payment before i deceided to set up a new IP.

Any ideas what to do and why it is delisted on both MN ?

Because multipool.us was running 10.14.1 when that block was found and enforcement isn't on, so it selected from that 10.14.1 masternode list.

[Laxdude7691]

So is the 504 count the number of MN running 10.15.13? If I was still running 10.14.1 would the same command give me a count for that version? One last question on drk.mn page the total MN's shows 773...Is this a bug or did we lose a bunch of MN's? Thanks...

"masternode count" with 0.10.15.13 gives you the current number of 10.15.13 Masternodes, but the number isn't reliable right know because some of them (ALL of mine  ) have the issue to temporarily go inactive and you have to give them a loving kick in the nuts from time to time.

0.10.14.1 (which I also monitor) is COMPLETELY confused, some 0.10.15.13 Masternodes show up there, some not, some temporarily, and of course the 0.10.14.1 Masternodes.

This will become better when more Masternodes and pools have updated, I hope it will not last TOO long...

BTW, drk.mn still uses the old version, therefore the numbers are wrong.

Crowning mentioned that sometimes the new version will go inactive? Bug I assume? What's the fix just to stop then start again from console? Hoping someone can save me the time of looking though forum as I'm sure this discussed already...

Edit: What's the best way to monitor MN activity? drk.mn?

[oblox]

So is the 504 count the number of MN running 10.15.13? If I was still running 10.14.1 would the same command give me a count for that version? One last question on drk.mn page the total MN's shows 773...Is this a bug or did we lose a bunch of MN's? Thanks...

"masternode count" with 0.10.15.13 gives you the current number of 10.15.13 Masternodes, but the number isn't reliable right know because some of them (ALL of mine  ) have the issue to temporarily go inactive and you have to give them a loving kick in the nuts from time to time.

0.10.14.1 (which I also monitor) is COMPLETELY confused, some 0.10.15.13 Masternodes show up there, some not, some temporarily, and of course the 0.10.14.1 Masternodes.

This will become better when more Masternodes and pools have updated, I hope it will not last TOO long...

BTW, drk.mn still uses the old version, therefore the numbers are wrong.

Crowning mentioned that sometimes the new version will go inactive? Bug I assume? What's the fix just to stop then start again from console? Hoping someone can save me the time of looking though forum as I'm sure this discussed already...

On occasion since there needs to be consensus on the network, your masternode will need to be restarted. As more and more of the network goes Onyx, there will be far more consistent consensus. On your remote daemon, do ./darkcoind stop, wait like 3-5 minutes before running ./darkcoind again. Then on local, initiate the masternode start command. Then back at remote, grep your ip and see if you are 1.