[∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved!

[-ck]

There was a problem at the pool end causing some unexpected down time. The pool has been restarted, apologies about the inconvenience. There's a minor issue with it at the moment and I'll be watching it carefully. It will likely need a planned restart tomorrow for updates.

[AtraxPool]

I guess its just solo.ckpool.org that has the issue I am on the DE server it seems to still be up I have a few pointed at solo.ckpool.org and its now showing dead in the status on the miners.

What is the issue ck? Is it related to the recent update?

[-ck]

I guess its just solo.ckpool.org that has the issue I am on the DE server it seems to still be up I have a few pointed at solo.ckpool.org and its now showing dead in the status on the miners.

What is the issue ck? Is it related to the recent update?

It is back up and yes the DE pool remained up. It appeared to be related to the recent update yes. It was software instability which I need to address.

[AtraxPool]

I noticed the last two blocks were no longer showing any signal and the commit to the bitbucket repo what is the main purpose for this code?

Code:

if (likely(witnessdata_check)) {

+					if (wb->insert_witness && witnessdata_check[0] && safecmp(witnessdata_check + 4, wb->witnessdata) != 0)

+						LOGERR("Witness from btcd: %s. Calculated Witness: %s", witnessdata_check + 4, wb->witnessdata);

+				} else

+					LOGNOTICE("Segwit rules returned but no default_witness_commitment to check witness data");

 				break;

 			}

 		}

[-ck]

I noticed the last two blocks were no longer showing any signal and the commit to the bitbucket repo what is the main purpose for this code?

Code:

if (likely(witnessdata_check)) {

+					if (wb->insert_witness && witnessdata_check[0] && safecmp(witnessdata_check + 4, wb->witnessdata) != 0)

+						LOGERR("Witness from btcd: %s. Calculated Witness: %s", witnessdata_check + 4, wb->witnessdata);

+				} else

+					LOGNOTICE("Segwit rules returned but no default_witness_commitment to check witness data");

 				break;

 			}

 		}

The code used on this pool is unique and different from the main ckpool code. That change you're asking about is for broken bitcoin daemons that say they have witness data and then don't provide it.

[Eagleone]

Im still getting rejected

[AtraxPool]

Try point you miners at stratum+tcp://de.ckpool.org:3333

I have some there and they are still hashing away.

it looks like stratum+tcp://solo.ckpool.org:3333 is showing as dead on my miners I attempted to change them ck must be working on the issue.

[-ck]

It never rains. There appears to be a DDOS on the main pool now.

[Eagleone]

Serves me right for not setting up my backup pools...

[-ck]

It never rains. There appears to be a DDOS on the main pool now.

Seems to have subsided (maybe the datacentre ddos protection was responsible) so I restarted the pool and everything looks back to normal.

[AtraxPool]

It never rains. There appears to be a DDOS on the main pool now.

I don't know if this is related but I have noticed my workers jumping in and out every 5 min or so it says "workers": 0   then few moments later there back. they are all pointed at the DE server.

[-ck]

It never rains. There appears to be a DDOS on the main pool now.

I don't know if this is related but I have noticed my workers jumping in and out every 5 min or so it says "workers": 0   then few moments later there back. they are all pointed at the DE server.

The main pool is responsible for reporting the hashrate so if the connectivity between DE and the main pool is affected the main pool will be reporting the wrong hashrate. That doesn't mean that the hashrate was low on DE. Anyway it appears to have subsided now.

[Eagleone]

Most of my miners are far away and no VPN...

[Eagleone]

Hashing happily

[AtraxPool]

Is it just me or have BTC.top been breaking block at a alarming rate?

That to me is more than "lucky"   BTC.TOP    blocks last 24 hrs - 34    Percentege - 21.12%

Code:

 486309 	BTC.TOP 	3 minutes ago 	1MB vote 	285.218 kB
486307 	BTC.TOP 	7 minutes ago 	1MB vote 	325.753 kB
486305 	BTC.TOP 	12 minutes ago 	1MB vote 	991.418 kB
486303 	BTC.TOP 	15 minutes ago 	1MB vote 	974.746 kB
486299 	BTC.TOP 	38 minutes ago 	1MB vote 	986.304 kB
486298 	BTC.TOP 	38 minutes ago 	1MB vote 	967.143 kB 

[-ck]

Is it just me or have BTC.top been breaking block at a alarming rate?

That to me is more than "lucky"   BTC.TOP    blocks last 24 hrs - 34    Percentege - 21.12%

Code:

 486309 	BTC.TOP 	3 minutes ago 	1MB vote 	285.218 kB
486307 	BTC.TOP 	7 minutes ago 	1MB vote 	325.753 kB
486305 	BTC.TOP 	12 minutes ago 	1MB vote 	991.418 kB
486303 	BTC.TOP 	15 minutes ago 	1MB vote 	974.746 kB
486299 	BTC.TOP 	38 minutes ago 	1MB vote 	986.304 kB
486298 	BTC.TOP 	38 minutes ago 	1MB vote 	967.143 kB 

Not really, it's all pretty consistent as luck is like that, but btc.top is pretty big anyway.

Besides this has nothing to do with this pool...

[AtraxPool]

My appoligies ck.  I just thought 34 blocks out the last 24hrs was a really lucky streak.

[-ck]

My appoligies ck.  I just thought 34 blocks out the last 24hrs was a really lucky streak.

No problems; 34 blocks in the last 24 hours HERE would be a really lucky streak... That's like a year's worth of blocks.

[AtraxPool]

My appoligies ck.  I just thought 34 blocks out the last 24hrs was a really lucky streak.

No problems; 34 blocks in the last 24 hours HERE would be a really lucky streak... That's like a year's worth of blocks.

Yeah that would be somthing to see multi blocks one after the other rolling in on ck looks like someone is on a hunt today love to see the hashrate rise like this!

Code:

{"hashrate1m": "5.69P", "hashrate5m": "5.52P", "hashrate15m": "5.35P", "hashrate1hr": "4.77P",

[icey]

Block!

Congrats, 1AUrEziNG7cH5fytYFBGQsnYivtYh2zqT8

http://solo.ckpool.org/users/1AUrEziNG7cH5fytYFBGQsnYivtYh2zqT8

Code:

 "hashrate1m": "1.31P",
 "hashrate5m": "1.33P",
 "hashrate1hr": "1.24P",
 "hashrate1d": "1.04P",
 "hashrate7d": "740T",
 "lastshare": 1506089363,
 "workers": 103,
 "shares": 400345679889,
 "bestshare": 144530105947858.0,
 "bestever": 144530105947858,