Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 162. (Read 1514767 times)

Crap. I was running rentals for the past few days and have no way to get my stats.  
I know I had one with a high 3xx but can't get the exact no.

Thank you so very much for the kind offer. I may as well take any donation in this regard at the pool address itself
1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ

-ck please send me a BTC address of yours that I can help contribute to compensating these miners. We all human and mistakes happen at the end of the day. I've always admired yours and Kano's honesty and would like to help in this situation. I can't help with much but I'll send through as much as I can each month from my mining earnings

I deleted my post from earlier. I've always admired your coding abilities and thought of you as the most trustworthy person in this area.

I doubted that for a short period but you've proved me wrong. Thank you for your honesty.

I'll check my addresses I was solo mining too, it will take a while as I was mining to a few hundred different addresses.

Well I take full responsibility for this and it is going to cost me big time  

I've spent the last day doing a root cause analysis regarding the best share being above network difficulty issue as mentioned here before and after the last high diff share and have concluded this is entirely my fault. This was always going to be a risk with running this pool as the development point for ckpool.

I'll summarise what happened here.

The first high diff share was on code that was halfway merged from old and new code giving support for segwit in the pool code but without actually activating it, while still on a bitcoind that was not signalling support for segwit. There was one failed submission of a block that happened concurrently with another block find on the network and there was nothing unusual about failing to submit a block at that time since it would have been a stale block. However it was the lack of debug from bitcoind that failed to tell me that there was actually a problem with the block submission rather than it just being stale.

In my enthusiasm to further update the code to support segwit, I completed the update to the pool code to request segwit block templates (when it activates) and updated the bitcoind to signal said support, along with adding more debug output from bitcoind for failed block submissions. This was a ridiculous error of judgement on my part to persist with the code.

The second high diff share mentioned here it was clear from bitcoind that there was actually a block submission failure rather than a stale block as there was no concurrent block that happened on the network and the extra debug code I added from bitcoind told me as much this time.

I've since rolled back the pool to older safe code while leaving bitcoind to signal support for segwit.

Now I wouldn't expect any other pool operator to simply ignore these failed block solves so I plan to take full responsibility and adequately compensate those 2 users who may have otherwise found blocks. Note that with the corruption, these actually would not have been blocks but I'm willing to treat them as such.

As I haven't altered any of the pool or user stats in any way, you will find your best ever share will still show your best share so it is time for you to check your userstats and see if you have one of the following bestever shares:
382969404792 or 821809472417

Please contact me either via PM or email to sign a verification that you are the owner of the associated address and I will organise compensation. As I have logs of who these belong to, you cannot just email me and say it was you without confirming your address.

The worst thing about this is not only would it be almost all the pool's profit for the last 2 years, the code itself works fine on testnet leaving me soul searching for how to prevent it happening on mainnet, and too terrified to deploy it again any time soon.  As segwit isn't going to be activated any time soon, there is no great urgency to get the code out there, and it does not mean I have to stop signalling support for segwit. I'm tempted to just shut the pool down if segwit activates instead. This may be the straw that breaks the camel's back. I've been increasingly unhappy with the bitcoin mining world at large for a while now and I may just choose to abandon it entirely.

I've never been so embarrassed online and I'm drinking hard liquor and it's not even midday here. Please send me boxes of tissues for I will be weeping for years to come over this incident  

Whoops I forgot to say didn't I? It's bfgminer 5.4.2. I'll see if I find anything.

Edit: Add /#skipcbcheck to the end of the pool url  - prior google searches failed cause I was including too much info. yay me.

Thanks for running this pool. I was solo mining for lulz with my obsolete asics on the bitcoin core client, but it's thrashing my disk.

No idea what software that's from; you should seek help from whoever maintains that software or fork or whatever it is since it's not a pool issue per se. and it's not in any software that I maintain.

I keep seeing this:

[2016-11-27 02:27:07] Coinbase check: incomplete coinbase for payout check

I tried adding a --coinbase-sig parameter but it hasn't helped. Any ideas? (I checked the thread but I likely have missed it if this came up before)

My post where I restarted the pool for segwit signalling was after that. You can check the ckpool code, it does check_best_diff where it sets the best share before rejecting shares. The only stale shares which wouldn't get tested for best_diff are those that are so old that the pool can't even find the workinfo for them meaning they'd be more than 10 minutes late because then it can't even decode it as a share.

I didn't think stale or rejected shares registered as "best shares" are you sure it wasn't a pool issue with the new upgrade for segwit signalling?

Restarts complete. Mine on!

Looks like it was a stale share.

The pool will try and submit stale shares anyway since it has nothing to lose, but it was rejected by bitcoind since it had already registered a new block by then.

Best share at 382969404792, orphan?
 
Edit: can't find it on the orphan list. Something wrong with pool and didn't submit the block?

Im up and running again. Thanks -ck.

Last restart fixed problem with westhash

Could have been a coincidence, but they started working after this last one.

Pool was fine, gateway was unhappy about restart but it's fixed now.

same here.. dead.

My s5s wont connect, I have tried re entering the info and power cycling. They report the pool as dead.....

Both pools updated and restarted uneventfully. Mine on!

Pool's fine.