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

[jacobmayes94]

I am mining with an antminer at this pool ant a U3 and have bought a few more antminers to point at it I was going to ask,  I use the CPU miner on my laptop when I am out in the cold and fancy warming up my lap a bit, would LOL if it finds a  block but I use it as a lap heater : )

Jacob

[1714875794]

1714875794

[1714875794]

1714875794

[1714875794]

1714875794

[ezeminer]

I am mining with an antminer at this pool ant a U3 and have bought a few more antminers to point at it I was going to ask,  I use the CPU miner on my laptop when I am out in the cold and fancy warming up my lap a bit, would LOL if it finds a  block but I use it as a lap heater : )

Jacob

Well good luck. Your computer will be burned out if you need to use it tho. And as many others have said, it is not recommended.

[DanielRo]

I am mining with an antminer at this pool ant a U3 and have bought a few more antminers to point at it I was going to ask,  I use the CPU miner on my laptop when I am out in the cold and fancy warming up my lap a bit, would LOL if it finds a  block but I use it as a lap heater : )

Jacob

According to https://www.quora.com/How-many-bitcoins-can-a-basic-computer-produce-per-day an i5 cpu is making about 14 MH/s.
An U3 has 63 GH/s. It is 4000 times more powerfull that your i5. Think you will close your U3 for 10 minutes. You will need a month or so to recover this time with an i5 cpu.

[philipma1957]

Dear @-ck
I find out the script in solo.nicehash is yours like solo.ckpool .
Few month ago i rent some hashrate and pointed to solo.nicehash but i use a wallet address started with 3.
I found a block but unfortunately pool do not accept addresses with 3 that time and create an address and sent fund to this address:
https://blockchain.info/address/1PN9XH9pPXtYHeupDAiFeFrkgXiwKZVUVe

Is there any way that i can access to my coins ?
Nicehash admin's refund to me ~3 btc because of that situation. but i spent more than that and lately i got realy bad luck in my life and this 25 btc would be really good help in this time.  so i came here and ask.
thanks.

@ fredi

so 25-3 = 22 btc correct?

I am not a rich guy so I can't say here is 22 btc , but I feel for you.

 So I pointed this at ck's pool for 1 day  if it hits  I will split the block with you

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


@ nicehash  not telling you what to do but a 3btc refund is a bit lite.  You could have given him more for your error not his.

[Fingolfin]

Wow!  

Thats a very nice guesture of solidarity!!!

@ philipma1957:

If you like to expand the solidary-mining-time, i step in with around 7,7 TH! (3 x SP20 @ around 950 GH/s + 1 x S7 @ around 4850 GH/s). For 48h after your OK!

If we hit a block i would like to get 4,5 Coins out of it (0,5 from that would be reserved to -ck for the nice Pool ... also some other donations are still pending    . If this is OK just reply, i'm online around 7h from know!

Nice fresh wind in the community by the look of things : ) ...

About Nicehash, where excatly is the Problem sending the Block / 25 BTC from "fredi" to an adress that is accesible Sorry! But that's just not legit!!! (or i get something wrong again???)

Best Wishes & Good Luck to all solo miners!    

Fingolfin

Dear @-ck
I find out the script in solo.nicehash is yours like solo.ckpool .
Few month ago i rent some hashrate and pointed to solo.nicehash but i use a wallet address started with 3.
I found a block but unfortunately pool do not accept addresses with 3 that time and create an address and sent fund to this address:
https://blockchain.info/address/1PN9XH9pPXtYHeupDAiFeFrkgXiwKZVUVe

Is there any way that i can access to my coins ?
Nicehash admin's refund to me ~3 btc because of that situation. but i spent more than that and lately i got realy bad luck in my life and this 25 btc would be really good help in this time.  so i came here and ask.
thanks.

@ fredi

so 25-3 = 22 btc correct?

I am not a rich guy so I can't say here is 22 btc , but I feel for you.

 So I pointed this at ck's pool for 1 day  if it hits  I will split the block with you

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


@ nicehash  not telling you what to do but a 3btc refund is a bit lite.  You could have given him more for your error not his.

EDIT: Yes, i confused "jacobmayes94" with "fredi" ! Icorrected my Post! Sorry!

[nicehash]

About Nicehash, where excatly is the Problem sending the Block / 25 BTC from "jacobmayes94" to an adress that is accesible Sorry! But that's just not legit!!! (or i get something wrong again???)

Hmm, how is "jacobmayes94" related to this issue? As already said, there was a serious bug in ck's ckpool source code, which was unfortunately not discovered neither by ck's testing nor our testing (the bug was present in ck's solo pool as well as in our pool or any solo pool that was built on top of ckpool source code) - this bug was unfortunately hit by fredi. To explain what happened (simplified explanation): ckpool code was unable to handle generating found block to a multi-sig address (3xxx). When fredi was mining it was using multi-sig address and he was the first ever to find block when using mulit-sig address. When the block was found the ckpool code generated this block to a "random" Bitcoin address (ckpool converted the bitcoin address to hash160, and "inserted" that hash to coinbase tx).

That said: nobody (or actually someone random) has these 25 Bitcoins, therefore neither us nor ck- as the author of ckpool source code can't refund this. It's an unlucky event, but our solo pool service is free to use (only charge fee at block found event, the same as ck's solo pool) and we unfortunately can't guarantee for these kind of unlucky events. But as said, we addressed this issue immediately by refunding 100% of the costs that fredi had with renting hashing power (this refund came directly out of our pockets, since these 3+ Bitcoins were already paid to miners selling hashing power) to mine on solo pool and we also immediately worked with ck to solve this bug.


Best regards,
NiceHash

[jacobmayes94]

I think he's confused me with fredi.

In response to the other post I turn on the cpu miner when I'm out in low temperatures only haha quite a way to warm you up I don't run it much though I'd rather not stress it if one wants to cpu mine a block erupted is better

[Fingolfin]

@nicehash

Sorry, i didn't wanted to offend you, my intention for this post was a complete other!   

quote:

To explain what happened (simplified explanation): ckpool code was unable to handle generating found block to a multi-sig address (3xxx). When fredi was mining it was using multi-sig address and he was the first ever to find block when using mulit-sig address. When the block was found the ckpool code generated this block to a "random" Bitcoin address (ckpool converted the bitcoin address to hash160, and "inserted" that hash to coinbase tx).

quote end

I don't said you or -ck has access to the coins! I'm just wondering why (obviously a bug! or?), a bitcoin adress is randomly generated and there is nowhere access to the corresponding private key. That where my thoughts! Nothing else! Sorry, i just was wondering!

When i read my post again, i better had skipped the "not legit" part! Sorry again!

Best Regards!

Fingolfin

[Fingolfin]

I think he's confused me with fredi.

In response to the other post I turn on the cpu miner when I'm out in low temperatures only haha quite a way to warm you up I don't run it much though I'd rather not stress it if one wants to cpu mine a block erupted is better

Yes! Sorry, i changed the Name to "fredi" in my post    ... Good Luck with CPU-mining     .... i tried 70 days with around 11TH .... nope, nothing , nada    Best share around 8.800.000.000 ... later with around 1 TH 11.000.000.000   .... speed is only part of the game    ... Luck is more important! Don't overheat your Laptop

Fingolfin

[hodedowe]

I'm of the opinion that 12.5 BTC + 3 BTCwould have been sufficient for a refund. That would make NH come out like the big guy doing well by its customers for having untested faulty code (either on the website, checking for non-compliant addresses, or the backend mining code) and give Fredi a bug-finding reward. He wouldn't have thrown a fit and made the problem so public had he been made happy within reason either, further tarninshing NiceHash's reputation.


I'll add that I'll mine for you too, Fredi. For the next WEEK my little Sparky experiment will be mining for you. If I win, I'll send you 15.5 BTC and feel good about every bit of it.


Good luck!

[philipma1957]

I'm of the opinion that 12.5 BTC + 3 BTCwould have been sufficient for a refund. That would make NH come out like the big guy doing well by its customers for having untested faulty code (either on the website, checking for non-compliant addresses, or the backend mining code) and give Fredi a bug-finding reward. He wouldn't have thrown a fit and made the problem so public had he been made happy within reason either, further tarninshing NiceHash's reputation.


I'll add that I'll mine for you too, Fredi. For the next WEEK my little Sparky experiment will be mining for you. If I win, I'll send you 15.5 BTC and feel good about every bit of it.


Good luck!

I did a long signature with nicehash  maybe 6 months he was pretty good to me.  ck has been pretty good to me.  So I am not throwing them under the bus.

I think the mining community needs both a solid solo pool like ck runs and I think we need a service like nicehash.

But I feel for fredi so if a few of us donate a bit maybe it will work out for him.  He did take a bullet for all of us on the multi sig issue.

[hodedowe]

Not under the bus, but NH's customer service in this instance left a lot to be desired. CK I've got no problem with - he runs a good solo pool and we agree on a lot of stuff. Plus he MADE Cgminer so...lifetime free pass in my book.  

 The problem lies with NiceHash selling a service, letting someone play the game by the rules, and then telling them sorry, your not a winner. Here's the money you paid in so let's just pretend this didn't happen.

Anyway, what's done is done. I'll put a week on Fredi's ticket and we'll see what happens.

[jacobmayes94]

when I hit I will donate 1 BTC to this guy if a solution hasn't been found for him, I will also donate 0.5BTC to CK as well to contribute to the solo pool. I feel though that nicehash being a big player could have afforded giving this guy something more than what he paid as a gesture of goodwill. Even if not the 25BTC. But what 'random' address was this? How did a random address generated just so happened to be a valid one? Or was it generated then, but no corresponding private key exists? Has there been any activity from this wallet in past or present? A check of the blockchain could find this out? Like if its a wallet someone already has or if it was generated then with no private key to match? I am not saying this is a conspiracy of any kind on the part of nicehash but I always like to know the full, and both sides of a story! To be fair out of all solo type pools I think CKs is the only one I will mine on. I trust it more than my own node in terms of its latency too.


Jacob

[Fingolfin]

Hi Philip,

maybe you ignore newbs by default!? However, to show that i mean what i say i just added the promissed hashrate to : http://solo.ckpool.org/users/1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje    until 03. November 21:00h 2015 Berlin Time

I liked your solidarity, and decided i like to step in. If we hit a block, proceed like you whish! But if you will fund 4,5 BTC to the adress i will specify in the "lucky case", all (Kano, -ck, and my electricity bill will have fun ; ) ... also fredi will feel much better! Which was the main reason    ... maybe we also can start talking about legit s5 & S7 firmware....

By the way, i used your Nice Hash Sig-link to open an account there and also spend alot of coins 

So far...  nevermind! But maybe not all people should mistrust newbs by default ( for example: your mistrust against RichBC ... he didn't wanted to sell you anything! Also, i didn't asked for your trust, i made the total different! think about!)

And for second time! Thanks for ALL your usefull posts!

Best Wishes!

Fingolfin

I'm of the opinion that 12.5 BTC + 3 BTCwould have been sufficient for a refund. That would make NH come out like the big guy doing well by its customers for having untested faulty code (either on the website, checking for non-compliant addresses, or the backend mining code) and give Fredi a bug-finding reward. He wouldn't have thrown a fit and made the problem so public had he been made happy within reason either, further tarninshing NiceHash's reputation.


I'll add that I'll mine for you too, Fredi. For the next WEEK my little Sparky experiment will be mining for you. If I win, I'll send you 15.5 BTC and feel good about every bit of it.


Good luck!

I did a long signature with nicehash  maybe 6 months he was pretty good to me.  ck has been pretty good to me.  So I am not throwing them under the bus.

I think the mining community needs both a solid solo pool like ck runs and I think we need a service like nicehash.

But I feel for fredi so if a few of us donate a bit maybe it will work out for him.  He did take a bullet for all of us on the multi sig issue.

[kano]

About Nicehash, where excatly is the Problem sending the Block / 25 BTC from "jacobmayes94" to an adress that is accesible Sorry! But that's just not legit!!! (or i get something wrong again???)

Hmm, how is "jacobmayes94" related to this issue? As already said, there was a serious bug in ck's ckpool source code, which was unfortunately not discovered neither by ck's testing nor our testing (the bug was present in ck's solo pool as well as in our pool or any solo pool that was built on top of ckpool source code) - this bug was unfortunately hit by fredi. To explain what happened (simplified explanation): ckpool code was unable to handle generating found block to a multi-sig address (3xxx). When fredi was mining it was using multi-sig address and he was the first ever to find block when using mulit-sig address. When the block was found the ckpool code generated this block to a "random" Bitcoin address (ckpool converted the bitcoin address to hash160, and "inserted" that hash to coinbase tx).

Sorry, but this is a scam excuse.
You modified ckpool to update the coinbase for every user mining to you solo pool.
-ck did not give you his solo pool code changes (that also didn't work) - your solo pool changes were written by you.

... and I can add, that kano.is never had this problem, simply because I knew that the ckpool code worked for how I was using it (1 address coinbase) and my payout process uses bitcoind to do transaction generation and testing so if bitcoind couldn't do it right ... then yeah that would be a major problem for everyone.

[nicehash]

Sorry, but this is a scam excuse.
You modified ckpool to update the coinbase for every user mining to you solo pool.
-ck did not give you his solo pool code changes (that also didn't work) - your solo pool changes were written by you.

... and I can add, that kano.is never had this problem, simply because I knew that the ckpool code worked for how I was using it (1 address coinbase) and my payout process uses bitcoind to do transaction generation and testing so if bitcoind couldn't do it right ... then yeah that would be a major problem for everyone.

Eh, kano, take a look here: https://bitcointalk.org/index.php?topic=763510.msg11621884#msg11621884

ck- admitted there was a bug and fixed it. We could also keep the info about this bug to our self, fixed it at our side and then someday the same issue might happen to ck solo pool - but the beauty of open source code is sharing the experience and improving the code.

And here is the unfortunate transaction: https://blockchain.info/tx/778724d38cfec7dc8782621cd8d0d9f09e4a7c1a1f82a66ddbdda698ef3b9433

[kano]

Sorry, but this is a scam excuse.
You modified ckpool to update the coinbase for every user mining to you solo pool.
-ck did not give you his solo pool code changes (that also didn't work) - your solo pool changes were written by you.

... and I can add, that kano.is never had this problem, simply because I knew that the ckpool code worked for how I was using it (1 address coinbase) and my payout process uses bitcoind to do transaction generation and testing so if bitcoind couldn't do it right ... then yeah that would be a major problem for everyone.

Eh, kano, take a look here: https://bitcointalk.org/index.php?topic=763510.msg11621884#msg11621884

ck- admitted there was a bug and fixed it. We could also keep the info about this bug to our self, fixed it at our side and then someday the same issue might happen to ck solo pool - but the beauty of open source code is sharing the experience and improving the code.

And here is the unfortunate transaction: https://blockchain.info/tx/778724d38cfec7dc8782621cd8d0d9f09e4a7c1a1f82a66ddbdda698ef3b9433

We know there was a bug in -ck's code.
I even stated that.
Can you not read?

You modified ckpool to update the coinbase for every user mining to you solo pool.
-ck did not give you his solo pool code changes (that also didn't work) - your solo pool changes were written by you.

Your code changes didn't work.

[philipma1957]

Sorry, but this is a scam excuse.
You modified ckpool to update the coinbase for every user mining to you solo pool.
-ck did not give you his solo pool code changes (that also didn't work) - your solo pool changes were written by you.

... and I can add, that kano.is never had this problem, simply because I knew that the ckpool code worked for how I was using it (1 address coinbase) and my payout process uses bitcoind to do transaction generation and testing so if bitcoind couldn't do it right ... then yeah that would be a major problem for everyone.

Eh, kano, take a look here: https://bitcointalk.org/index.php?topic=763510.msg11621884#msg11621884

ck- admitted there was a bug and fixed it. We could also keep the info about this bug to our self, fixed it at our side and then someday the same issue might happen to ck solo pool - but the beauty of open source code is sharing the experience and improving the code.

And here is the unfortunate transaction: https://blockchain.info/tx/778724d38cfec7dc8782621cd8d0d9f09e4a7c1a1f82a66ddbdda698ef3b9433

It was good of you to share  that info and  the refund of his 3 btc was good.   But you should have given him some more.

yeah maybe not 22 more coins or whatever the full block was worth but he did you a favor and the all of us mining solo on ck's pool a favor.

I read  about this in a few posts but did not understand fully what happened.

   I hit 2 blocks in 90 minutes on ck's pool with a single signature hot wallet address.  If I was doing  a multi-signature  I would have lost 50 coins.  and since I was running the solo for 10 people 45 coins would have come out of my pocket as I am not going to let the people down. I would have lost about 11000 dollars at the time.  I mention it since I hit the 2 blocks very close in time to this lost block.

You have been a standup guy and run a good service you should consider giving him some more coin.  

Just my opinion  BTW I am renting from your pool to give him a shot at ½ a  block.

[o_solo_miner]

  cool another Live view.

Congrats to 1LPWZ9AskyF8Ux384cXoYbvNRTKgLooGh3 for Block 381610

[Rikim4ru]

Wow!

Looks like a quick 200th rental

Someone have a good KARMA!
Happy for you, whoever!