v0.10.15 - Onyx Release

GermanRed+ said:
I don't think suchpool was the bad guy. Maybe, some miner on suchpool did that.
Click to expand...

A pool-miner can't do this, they just get shares and return hashes.

And because Suchpool _are_ the good guys (I mine there literally from day one) I guess the enforcement code is still a bit buggy.
 
crowning said:
A pool-miner can't do this, they just get shares and return hashes.

And because Suchpool _are_ the good guys (I mine there from day one) I guess the enforcement code is still a bit buggy.
Click to expand...
That's understandable. A large fraction of payments I got from the pre-enforcement days came from suchpool so I highly doubt suchpool was the evil one.
 
From https://drk.mn/masternodes.html
See pic, good or bad, is this connected to enforcing forks in any way?

daemons.png
 
AjM said:
You say they are on purpose wrong?
Click to expand...
Sure, RC5 introduced a new masternode payment scheme, and after enforcement was turned on the first time (at least it was enabled for ~20 hours) the outdated clients forked.

I suppose elbereth is just running these old daemons to monitor the (deprecated) masternode networks adjacted to them.
 
flare said:
Sure, RC5 introduced a new masternode payment scheme, and after enforcement was turned on (at least it was enabled for ~20 hours) the outdated clients forked.

I suppose elbereth is just running these old daemons to monitor the (deprecated) masternode networks adjacted to them.
Click to expand...
Ok, just wondering :smile:
 
OK, I updated the official Twitter with the call to re-start daemons with the --reindex command. Evan suggested that owners that are stuck do that, but it's better that everyone does it, to avoid confusion. There are a lot of new owners out there! Please RT if you are on Twitter.
 
Can't wait to bug the pools again after Evan posts a new update with fork fix :tongue:

I think pool operators soon will voluntarily agree for masternoes to replace the pools, in exchnage for not being asked again for an upgrade :grin:
 
TaoOfSatoshi said:
OK, I updated the official Twitter with the call to re-start daemons with the --reindex command. Evan suggested that owners that are stuck do that, but it's better that everyone does it, to avoid confusion. There are a lot of new owners out there! Please RT if you are on Twitter.
Click to expand...

I'm afraid this is going to cause confusion because people will automatically think something is wrong with their masternodes, when that is not the case at all.
 
David said:
I'm afraid this is going to cause confusion because people will automatically think something is wrong with their masternodes, when that is not the case at all.
Click to expand...
No, it is just a maintenance call. The tone of the announcement was not urgent.
 
thelonecrouton said:
Agreed, AFAIK there's no need for 1100 MN ops to do this.
Click to expand...
There are a lot of new owners who don't know how to check if their node is doing something wrong. It doesn't hurt to do this procedure. I did it to my 5 nodes and they're humming along, nicely!
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top