Author

Topic: [∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 244. (Read 102489 times)

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
In addition, I've made publicly available the code as used by this solo pool now as well:
https://bitbucket.org/ckolivas/ckpool-solo

Bear in mind it expects certain customisations and I will take no responsibility if someone misuses this in the community and creates a new solo pool with it, but perhaps someone skilled enough can fill the gap with it from me closing this pool.
hero member
Activity: 1220
Merit: 612
OGRaccoon
I will also shout 2 BTC shout from me to the lost block fund if I hit highly unlikely though,  but as above, stranger things have happened!

Also very sad to know that you will be closing the pool's CK i'm sure a lot of us really value your service to the community over the years.

A very sad day indeed. 
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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 😂😎
Code:
hashrate1m": "140T",
 "hashrate5m": "124T",
 "hashrate1hr": "115T",
 "hashrate1d": "123T",
 "hashrate7d": "70.8T",
 "lastshare": 1589154060,
 "workers": 6,
 "shares": 15486797073,
 "bestshare": 40661720994071.75,
 "bestever": 40661720994071,
 "worker"::
Sure thing. The 70TH estimate is irrelevant, as the total shares already told me how much hash you've committed total. I can either work that out or you can just tell me how long it's been and at what electricity rate as I'm happy to do it on trust as I feel bad enough as it is.
jr. member
Activity: 56
Merit: 4
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:
Code:
"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 😂😎
Code:
hashrate1m": "140T",
 "hashrate5m": "124T",
 "hashrate1hr": "115T",
 "hashrate1d": "123T",
 "hashrate7d": "70.8T",
 "lastshare": 1589154060,
 "workers": 6,
 "shares": 15486797073,
 "bestshare": 40661720994071.75,
 "bestever": 40661720994071,
 "worker"::
member
Activity: 453
Merit: 16
Very Sad,
I too will give 1btc to the gent that lost out should I hit a block.
I will keep mining here until the end too.

hero member
Activity: 1220
Merit: 612
OGRaccoon
pretty speechless myself terrible news for the miner and CK.

 Shocked
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
very sad news.

I will stay pointed till the bitter end.

If i have a miracle and hit I will give 2btc. to the person that lost out.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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:
Code:
"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.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
So far I know the block got submitted but got rejected for being stale but the nearest block wasn't as close as I would have expected. The block that succeeded it was block 629777 by poolin.
sr. member
Activity: 406
Merit: 254

1. ailikun   0.01 btc
2. VRobb   0.01 btc
3. Ivcelmik 0.01 btc
4. achkn    0.03 btc
5.
6.
7.
8.
9.
10.

I'm in yet again!  What's wrong with us...?  Cheesy

I'm in!
Time to eat some chicken  Grin


Sorry Guys, looks like there might be something with the pool, so no "solo run 24 hours before the halving".
I will refund you tomorrow, as soon as I get to my Pc with the wallet.
We will try next time then.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Pool is back up, I've saved all the logs to investigate and will report back.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Code:

   "hashrate1m": "13.5T",
   "hashrate5m": "13.1T",
   "hashrate1hr": "13.4T",
   "hashrate1d": "12.5T",
   "hashrate7d": "8.77T",
   "lastshare": 1589133889,
   "shares": 2097197030,
   "bestshare": 40661720994071.75,
   "bestever": 40661720994071

I thought if a share was over the difficulty then it was a block? Or am I completely mistaken? Because 40 trillion is defiantly more than 16 trillion. Huh  Huh
My miner says it found 2 blocks

This looks correct yet there was no successful block solve so I'm going to take the pool down to investigate. Sorry to all the people who want to mine in the lead-up to the halving. I don't know how long the pool will be down for. I'm terribly sorry about any inconvenience.

hero member
Activity: 1220
Merit: 612
OGRaccoon
Would it not show as a stale in his screen shot? looks like his stale value is 0

At first I thought this was going to be some edited screen shot but the numbers there on the pool to see and if it was a orphan that's very unlucky but I can't see any orphan blocks on any online stats.




I mean my luck is usually shit so when I opened the miner and saw 2  found blocks in 13 hours I was crazy excited but then my wallet only has the same 1.2 btc was like oh hell the fuck no this is bullshit on a planet of fucking garbage  yup lady luck is not my friend it would seem.

To find 2 in a row would be astronomical odds and to do so in 13 hours would make those odd's even higher.

Best person who can answer this is the pool OP as already stated.
jr. member
Activity: 56
Merit: 4
Would it not show as a stale in his screen shot? looks like his stale value is 0

At first I thought this was going to be some edited screen shot but the numbers there on the pool to see and if it was a orphan that's very unlucky but I can't see any orphan blocks on any online stats.




I mean my luck is usually shit so when I opened the miner and saw 2  found blocks in 13 hours I was crazy excited but then my wallet only has the same 1.2 btc was like oh hell the fuck no this is bullshit on a planet of fucking garbage  yup lady luck is not my friend it would seem.
legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
That is why I told him to wait until ck is there, he is the only one who can check and tell what was going on.
So just wait until AU is waking up.
I leaved him a message on irc, he will show up then.
hero member
Activity: 1220
Merit: 612
OGRaccoon
Would it not show as a stale in his screen shot? looks like his stale value is 0

At first I thought this was going to be some edited screen shot but the numbers there on the pool to see and if it was a orphan that's very unlucky but I can't see any orphan blocks on any online stats.


sr. member
Activity: 406
Merit: 254

Then please post your btc address you are mining with on solo , so we can check that.



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

Yeah, that definatly should've been a block.
Maybe a stale one, but damn that really hurts if it is.
legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
That looks like a block, could be a orphan one, but only ck can check that.
ok, wait for ck comes online.

legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
Code:

   "hashrate1m": "13.5T",
   "hashrate5m": "13.1T",
   "hashrate1hr": "13.4T",
   "hashrate1d": "12.5T",
   "hashrate7d": "8.77T",
   "lastshare": 1589133889,
   "shares": 2097197030,
   "bestshare": 40661720994071.75,
   "bestever": 40661720994071

I thought if a share was over the difficulty then it was a block? Or am I completely mistaken? Because 40 trillion is defiantly more than 16 trillion. Huh  Huh
My miner says it found 2 blocks


Then please post your btc address you are mining with on solo , so we can check that.
Jump to: