My conclusion isn't a pretty one unfortunately and is mostly my fault to do with the resource capabilities of the pool hardware.
There was a single hash good enough for a block solve by rasmukri at 2020-05-10T12:34:16.287799Z but due to an unfortunate storm of coincidences a backup job was running on the pool at the time which overloaded the server pushing it heavily into swap memory. This caused the bitcoin daemon to be effectively out of sync with the blockchain for a while. Unfortunately this means that even though it was a potential block, it was not up to date with the current blockchain tip and was effectively stale anyway. The pool didn't record it as stale because it was a valid hash in the pool's eyes and its resource usage is much less than the bitcoin daemon so it was still operating normally, though complaining about not getting new block templates. Note that there was only one blocksolve hash good enough, and no other miners submitted potential block solves in that time. As is often the case with bitmain hardware, I would not trust it if it said it had solved blocks normally, but in this scenario one of them was very real.
As this pool doesn't make an awful lot of money, I could not really afford to dedicate much in the way of hardware resources to the pool. Since this is my fault for not ensuring the pool had enough resources for the bitcoin daemon, pool, and backup at the same time, I would like to come to an agreement with rasmukri by reimbursing him for his mining costs for time spent mining solo here, and as some degree of recompense I am willing to pay back double the cost of the mining. It may not be a full block's reward, but it is better than you could have earned mining in a regular pool. The only saving grace is that this didn't happen to any of the bigger miners who spent a lot dumping hashrate here in that time.
As of the time of posting this, the summary of your stats are as follows:
"hashrate1m": "43.5T",
"hashrate5m": "68T",
"hashrate1hr": "112T",
"hashrate1d": "123T",
"hashrate7d": "70.7T",
"lastshare": 1589151959,
"workers": 3,
"shares": 15429406451,
"bestshare": 40661720994071.75,
"bestever": 40661720994071,
The 15 billion shares you submitted should give an approximation of how long you have mined here with your average 70TH (according to the weekly average.)
Please tell me if you find this satisfactory and we can take it to private message to resolve further.
In addition it is with a heavy heart that I find myself unable to cope with the potential stress of similar situations and loss of interest in maintaining any pool in this climate, along with the upcoming halving making it virtually completely impossible for individual miners to meaningfully mine and that I wish to close this and the shared pool after the halving.
Any existing miners you may wish to withdraw your hashrate sooner rather than later to prevent a similar situation happening between now and its closure, or you may wish to just hammer it hard until it's closed but I give no guarantees that it may not happen again and I will not be trying to reimburse anyone again.
Thanks for looking into that, you have no idea how excited I was when I saw the 40 trillion, until I opened my wallet. But at the time of you pulling my stats I guess it was right after my reboot of everything. It's strange how the stats work. I've been on here for almost a week and I've been pretty steady at (125th/s +-) but I guess it's gotta work up an average or something. I appreciate the offer to compensate and will take you up on it. I will also keep my miner pointed here untill you take it down, I have lottery winning dreams 😂😎
hashrate1m": "140T",
"hashrate5m": "124T",
"hashrate1hr": "115T",
"hashrate1d": "123T",
"hashrate7d": "70.8T",
"lastshare": 1589154060,
"workers": 6,
"shares": 15486797073,
"bestshare": 40661720994071.75,
"bestever": 40661720994071,
"worker"::