coinbaseaux and ckpool

[fcojperez]

Hi. I am pretty new in all this stuff so as an exercise I am deploying the ckpool in one of my servers using the source code shared here, https://bitbucket.org/ckolivas/ckpool/src/master/.

The issue that I have is that I am getting this error below.

Code:

[2021-03-07 23:14:35.512] JSON failed to decode GBT 0000000000000000000d044b4decb68ed01c0ad5f135c15cc7a418e88b43713d 0000000000000000000d1f8c0000000000000000000000000000000000000000 536870912 1615155275 170d1f8c (null) with errno 11: Resource temporarily unavailable

So far I am aware, the issue is due to coinbaseaux is empty as it is an optional value. So I wonder how this pool is working, solo.ckpool.org:3333.

is that pool using other different code? or should I setup something before executing ckpool?

Please any help I will apreciate. Thanks.

Regards,
FP.

[1714905546]

1714905546

[1714905546]

1714905546

[1714905546]

1714905546

[1714905546]

1714905546

[kano]

It's using an old bitcoin version - yeah you have to pay him to fix his own pool

[100knot2dae]

I wondered about that too. He's probably got a good reason not to upgrade, since fixing just this would be easy.

Only ck can tell his intentions.

[NotFuzzyWarm]

He's probably got a good reason not to upgrade, since fixing just this would be easy.

The problem is that -ck just does not care about it anymore.

You have to remember that -ck is not a professional programmer: He is a medical doctor, specifically an anesthesiologist so bitcoin stuff is mainly a hobby for him and as a result he stopped updating/fixing cgminer & ckpool quite a while ago... The one other main coder for them was Kano who IS a professional programmer and several years ago due to irreconcilable differences over proper coding techniques and testing of said code -ck booted Kano from the gits

[100knot2dae]

The problem is that -ck just does not care about it anymore.

Maybe it's really as simple as that.

For the rest, I tend to disagree, knowing his work also on the linux kernel. Unless you define "professional" only as getting paid for what one is doing. For that part, I agree.

[NotFuzzyWarm]

Unless you define "professional" only as getting paid for what one is doing.

I define Professional as one who's been formally trained in what they do and made a career out of it. Even more to the point, it is someone who cares about the quality of their work and if there is a problem - they fix it.

Given that, he is programming hobbyist. Not without some talent, but nonetheless still just a hobbyist.

[100knot2dae]

@fcojperez: coming back to the original question:

Best use bitcoind 0.19 then if you want to run your own ckpool instance. Or amend the code to make the coinbaseaux flags in the response optional, similar to what I did for cgminer here: https://github.com/golden-guy/cgminer/commit/168a1bdfedb1408a690f5387e04e3c9af7842c5e

This should work just as well for the ckpool code.

[kano]

@fcojperez: coming back to the original question:

Best use bitcoind 0.19 then if you want to run your own ckpool instance. Or amend the code to make the coinbaseaux flags in the response optional, similar to what I did for cgminer here: https://github.com/golden-guy/cgminer/commit/168a1bdfedb1408a690f5387e04e3c9af7842c5e

This should work just as well for the ckpool code.

So have you tested this actually works with real blocks - or is it an untested change?

That's happened a number of times in the past with ck not testing code fully, and they've lost blocks due to it.
Nowadays, you're talking about 1/3million dollars lost if it doesn't work 100%

[100knot2dae]

Feel free to test it. Or maybe you could just as well share your solution?

It is a suggestion after all, as indicated by *should work*. But when looking at the code, it's very likely to work with ckpool just as well.
As with every code under the GPL, no liability assumed and to be used at everyone's own risk.

It works for cgminer and was confirmed by at least one another user here: https://bitcointalk.org/index.php?topic=5053833.msg56477759#msg56477759

[kano]

...
It works for cgminer and was confirmed by at least one another user here: https://bitcointalk.org/index.php?topic=5053833.msg56477759#msg56477759

Confirmed? Oh he found a block with a gekko? Wow?

https://bitcointalk.org/index.php?topic=5053833.msg56614055#msg56614055

[100knot2dae]

Wow, so this is one of those said moments when people are getting struck by your professionalism. Feeling almost proud to achieve this honour in such a short time here. 

[NotFuzzyWarm]

Wow, so this is one of those said moments when people are getting struck by your professionalism. Feeling almost proud to achieve this honour in such a short time here.  

Do not forget that mining is a Financial endeavor and software/hardware MUST be properly vetted to be sure it works properly. A decent developer will do that by running it on their own network before releasing it to the world.

One does not just write code, see that it does not crash and then announce "it works!" You the developer should provide proof and NOT put others at risk by making them be testing guinea pigs.

[100knot2dae]

Now this is getting bizarre  

The plain necessity of this simple change has been introduced by this upstream commit: https://github.com/bitcoin/bitcoin/commit/e9a27cf338dc618b8ecab8984abc54d588de8a05

How to verify? Similarly simple:

Does it mine with it? -> Yes
Does it mine without? -> No

Regarding the scope of this very change, no further verification is needed!

I won't discuss this any further. Anyone who feels the need for it, shall take it, and others shall just leave it. That's the beauty of open source.