Search results

Things get confusing then using "getblocktemplate" and seeing the bottom information: , "noncerange" : "00000000ffffffff", "sigoplimit" : 20000, "sizelimit" : 1000000, "curtime" : 1422004946, "bits" : "1b126005", "height" : 207852, "votes" : [ ], "payee" : "XtFzRjgQsM9YspaWtbNYJ6RhNUQYYevNxF"...

Yes, when the majority of the network (80-90%) is running the latest build.

...because enforcement isn't on.

People updating more than likely. Masternode count showing 1880.

Didn't we have 80%+ of miners on Core, if so, the majority of nethash should have been mining on the right blockchain. Then again, I read numerous pools rolling back to Onyx for stability so who really knows.

Thoughts eduffield ?

Can't enforcement or some code turn off old builds for masternodes, as in they aren't even recognized by the network. If you are a masternode operator, it is your obligation, much like pool operators, to be on the latest build. When payments stop trickling in, they will get the point. If the...

But I thought the whole reason we turned enforcement back on was due to the majority of nethash being updated to Core...

Due to masternodes or pools because I thought the pools were already on Core and v10's should have forked off (which appears to be the case). Looks like over 80% of the pools are paying Core masternodes.

If you have custom settings in your darkcoin.conf like disabling safemode, wallet mining, etc, you can leave them, but the masternode information can get removed if you are using the masternode.conf in junction with start-many/start-alias.

Absolutely sickening seeing how many Onyx masternodes are still out there. You shitbags don't deserve a single fucking payment you lazy bums.

Nope, it's just downloads and uploads.

No, it doesn't sound like it is gone forever, but at least a day's worth of posts would be.

disablesafemode=1 The D should be lowercase, I just tend to capitalize all my sentences at starts of posts.

Some what related, what ended up happening with the buy wall on Bitfinex? Doesn't look like yours currently at 666 with 9134 was sold into from 45k. The volume just isn't there at that price.

Guys, the warning message is telling you exactly what is happening... that there is another fork (or forks) on the network. It does not mean you are on a bad chain.

Disablesafemode=1 in your conf if stopping and starting doesn't work

It's a bit early to say what caused it at the moment unfortunately.

It's the block hash...

That doesn't mean you are on a bad fork. It just means the client detected another fork out there on the network. Judging by block number, you are on the right fork but check the hash: 0000000000008bba11033c31a1a4df29db8557b8355ef6738f7a93beb2fc4901