SoloMining with CGMiner against Bitcoind / Bitcoin Core v0.18.1

[kano]

Well, wrong, look here:

I think it should be native segwit (bech32), I corrected it

Seriously shitc0in - facts please.
You make up shit all the time.

Git commit to add bc1 addresses to ckpool code February 2018
Con Kolivas committed 61513a7
2018-02-06
Implement native bech32 segwit address support.
https://bitbucket.org/ckolivas/ckpool/commits/61513a765b12947fae30535179194b1672dc82b5

His last commit into cgminer December 2018
https://github.com/ckolivas/cgminer/commits/master
Commits on Dec 6, 2018
    Merge pull request #734 from Johnson-Fan/master
   @ckolivas ckolivas committed on Dec 7, 2018

[1715019339]

1715019339

[1715019339]

1715019339

[1715019339]

1715019339

[1715019339]

1715019339

[1715019339]

1715019339

[citb0in]

seems like bech32 was only implemented in the CKpool but not included in cgminer for other reasons then.

What it is important to note --> bech32 is not supported by cgminer for solo mining and to read the previous important information and suggested solution to enable solo mining funtionality in cgminer. That is was the topic here is about.

[yoshimitsu777]

Hello yoshitmitsu,

you can solo mine on your own full node (bitcoind) without hesitation. Don't be put off by Kano's statements. He is constantly bashing other pool operators because he sees everyone as a rival. As you note, he also doesn't even address your questions that you understandably asked, instead he also attacks you for supposedly promoting the patch that unlocks solo functionality. He doesn't like that thousands of solo-mining enthusiasts out there could mine on their own full-node because that would mean even fewer participants on his pool. As you may know cgminer was developed by Con Kolivas (-Ck) and Kano had participated there as a developer. Kano especially developed the driver parts. CK kicked Kano out many years ago and banned him from development because of personal disputes between the two. Since then, Kano has been constantly ranting on CK and everything that has to do with him. However, this bashing does not exist the other way around. CK stopped the development of cgminer a long time ago and made it public. Kano has been managing cgminer on his own since then and has his own fork at github.com/kanoi/cgminer. There he maintains e.g. the latest drivers, especially those from Gekkoscience. He sees himself as a god, everyone else is a loser in his opinion.

About your questions and your intention. You are of course welcome to apply the golden-guy patch. As it was already suggested to you, you could clone the current cgminer version from Kanos' github repository and then apply the golden-guy patch. As mentioned here in the thread, there are also numerous other github repositories that include this patch, which unlocks solo mining functionality. What you should pay attention to when you manually apply the golden-guy patch --> you must NOT specify a bech32 address (begins with bc1q...) as payout address but you should exclusively use a legacy P2PKH address (begins with 1...). If you would use a bech32 as payout address (eg. bc1qxyz123abc...) then cgminer would seem to run without any problems at first sight, but if you should really hit a block, then the coinbase transaction would be erroneous and the reward would not be transferred to your specified bc1q.... (Bech32) address but to a random bitcoin address. Your reward would be lost, that would be fatal and nobody wants that. This is what Kano means with his incomplete statement and although he knows the risk, he resists to post this information here publicly, so that he can claim himself as a prophet afterwards full of glee (by actions like that). Such behavior is anything but exemplary.

Bech32 didn't exist when CK implemented solo mining in cgminer those times and as explained before cgminer was put in archive mode by CK. Kano still deliberately avoids unlocking solo functionality in his current versions, and he tries to justify this in the sense that it would be foolish to mine on a dedicated full-node. Of course, it should be clear to everyone that a full node and mining on such a full node requires certain minimum requirements and how important performance is in the context of the mining process. A possibly found valid block must finally find its way into the blockchain in the shortest and fastest way and reach many nodes at ultra-fast speed, otherwise one runs the risk of stale shares and orphan blocks. Not only a high-performance full node is important, but also the speed to the Internet plays a role, as well as the routers and hops in between. At best, everything runs in a data center with high-quality devices and top performance with an extremely fast Internet connection. Keep in mind the sheer amount of data (some TBs per month) just for the GBT traffic so running this at a data center makes only sense if your miner is located on-site, too. This information could all be mentioned, explained and ultimately left to the user's free decision to solo-mine on a full-node.

So that you don't do anything wrong when enabling the solo mining functionality and risk misconfiguration, I would highly recommend you to use ready-made cgminer versions that already contain this patch. There are several Github repositories. My own favorite is github.com/phaenomenon/cgminer, which is quite up-to-date (version 4.12.1) and includes many other useful things besides the actual Golden Guy patch. For example, it automatically checks the given payout address for correctness, only then the mining process starts at all. If you accidentally entered a Bech32 for solo mining, cgminer warns you at startup and aborts with an error message so you can correct it. Also, you can mine not only in mainnet but also in testnet. In testnet you need to provide a legacy address that starts with "m" or "n" and this is also handled by the input validation. The README contains useful information under "SOLO mining" and there are also very cool start scripts included, so you can get started right away.

I also highly recommend reading those two How-To's from nullama which explains how to mine on testnet using a GekkoScience Compac-F USB miner or even with a GPU/CPU:
[Guide] Solo mine testnet bitcoins with cgminer, Bitcoin Core, and a Compac F
[Guide] Solo mine testnet bitcoins with bfgminer, Bitcoin Core, and a CPU/GPU

In case you use a GekkoScience Compac F, the installation process is as follows.

Code:

# clone the repository
git clone https://github.com/phaenomenon/cgminer

# rename it to a meaningful name so you can distinguish it in case you want to try other cgminer versions, too.
mv cgminer cgminer_phaenomenon

# enter directory
cd cgminer_phaenomenon

# compile it
CFLAGS="-O2 -march=native -fcommon" ./autogen.sh --enable-gekko
make

# look at the provided three start scripts *.sh and *.conf files and adjust to suit your needs, here I choose testnet for the initial test
vi start_solomining_ownFullNode_testnet.sh

# ensure your bitcoind is running testnet and then launch cgminer
./start_solomining_ownFullNode_testnet.sh

Logs are written to the subfolder "logs\" which I find very convenient. After you have successfully mined your first block on testnet and received succesful your block reward, you could switch to mainnet.

Hope this guide is helpful for everyone. Good luck and happy solo-mining

citb0in

awesome this is exactly what i looked for.thanks bro! works like a charm
this guide should be pinned if you ask me

[kano]

who do you mean?i did not advertise code for free.i had quoted the patch to ask if you had referred to it in your previous reply because it was not clear.

still unanswered is your statement that this patch sends coins to a foreign address. I'd love to understand, but you don't seem to want to answer.

does anyone else know what kano means and what it has to do with this patch?

Just ignore it. Up to now he has never come up with his own approach - and he probably never will - but rather spends his time on telling other people's work off. That's the real tragedy here.

All I can say is that FOR ME, this golden-guy patch has proven to find blocks countless times on BTC testnet and other forks when solo mining on an own node. And I have tested this with lots of different addresses by now.

But this is no promo, no recommendation and you always do things at your own risk.

Quoted for posterity, coz that's a pretty specific statement you make there.

Meanwhile, as most now know, coz I pointed out why in discord weeks ago, and that info has spread, indeed 100knot2dae was telling people to use a patch that would fail if any address you used didn't start with 1.
All new wallets by default do not use 1 address.

[100knot2dae]

who do you mean?i did not advertise code for free.i had quoted the patch to ask if you had referred to it in your previous reply because it was not clear.

still unanswered is your statement that this patch sends coins to a foreign address. I'd love to understand, but you don't seem to want to answer.

does anyone else know what kano means and what it has to do with this patch?

Just ignore it. Up to now he has never come up with his own approach - and he probably never will - but rather spends his time on telling other people's work off. That's the real tragedy here.

All I can say is that FOR ME, this golden-guy patch has proven to find blocks countless times on BTC testnet and other forks when solo mining on an own node. And I have tested this with lots of different addresses by now.

But this is no promo, no recommendation and you always do things at your own risk.

Quoted for posterity, coz that's a pretty specific statement you make there.

Meanwhile, as most now know, coz I pointed out why in discord weeks ago, and that info has spread, indeed 100knot2dae was telling people to use a patch that would fail if any address you used didn't start with 1.
All new wallets by default do not use 1 address.

Let it be Kano...
https://bitcointalk.org/index.php?topic=5373190.msg58531767#msg58531767
https://bitcointalk.org/index.php?topic=5373190.msg61436321#msg61436321

[kano]

who do you mean?i did not advertise code for free.i had quoted the patch to ask if you had referred to it in your previous reply because it was not clear.

still unanswered is your statement that this patch sends coins to a foreign address. I'd love to understand, but you don't seem to want to answer.

does anyone else know what kano means and what it has to do with this patch?

Just ignore it. Up to now he has never come up with his own approach - and he probably never will - but rather spends his time on telling other people's work off. That's the real tragedy here.

All I can say is that FOR ME, this golden-guy patch has proven to find blocks countless times on BTC testnet and other forks when solo mining on an own node. And I have tested this with lots of different addresses by now.

But this is no promo, no recommendation and you always do things at your own risk.

Quoted for posterity, coz that's a pretty specific statement you make there.

Meanwhile, as most now know, coz I pointed out why in discord weeks ago, and that info has spread, indeed 100knot2dae was telling people to use a patch that would fail if any address you used didn't start with 1.
All new wallets by default do not use 1 address.

Let it be Kano...
https://bitcointalk.org/index.php?topic=5373190.msg58531767#msg58531767
https://bitcointalk.org/index.php?topic=5373190.msg61436321#msg61436321

Yet you posted here about it and didn't point out that problem anywhere here before I pointed out the random address issue ...
You even then followed up as can be seen above "And I have tested this with lots of different addresses by now." <- which will fail with most address.
Then you didn't even bother replying with the issue but instead post shit about me - lol.
Yeah fine you mentioned it once last year, but then go around telling people here it's OK to use it without pointing out that for most of them it will fail.

[100knot2dae]

who do you mean?i did not advertise code for free.i had quoted the patch to ask if you had referred to it in your previous reply because it was not clear.

still unanswered is your statement that this patch sends coins to a foreign address. I'd love to understand, but you don't seem to want to answer.

does anyone else know what kano means and what it has to do with this patch?

Just ignore it. Up to now he has never come up with his own approach - and he probably never will - but rather spends his time on telling other people's work off. That's the real tragedy here.

All I can say is that FOR ME, this golden-guy patch has proven to find blocks countless times on BTC testnet and other forks when solo mining on an own node. And I have tested this with lots of different addresses by now.

But this is no promo, no recommendation and you always do things at your own risk.

Quoted for posterity, coz that's a pretty specific statement you make there.

Meanwhile, as most now know, coz I pointed out why in discord weeks ago, and that info has spread, indeed 100knot2dae was telling people to use a patch that would fail if any address you used didn't start with 1.
All new wallets by default do not use 1 address.

Let it be Kano...
https://bitcointalk.org/index.php?topic=5373190.msg58531767#msg58531767
https://bitcointalk.org/index.php?topic=5373190.msg61436321#msg61436321

Yet you posted here about it and didn't point out that problem anywhere here before I pointed out the random address issue ...
You even then followed up as can be seen above "And I have tested this with lots of different addresses by now." <- which will fail with most address.
Then you didn't even bother replying with the issue but instead post shit about me - lol.
Yeah fine you mentioned it once last year, but then go around telling people here it's OK to use it without pointing out that for most of them it will fail.

You had your chance to shine on this topic for a long time, but decided against. That was your decision.

However, by now everybody who had serious interest in the solo mining topic was aware of this fact. It is with reason that e.g. the golden-guy version of cgminer has added a bitcoin address check (https://github.com/golden-guy/cgminer/commit/90d03dd12f4b7d800eb9976356875c9c003aac2e for P2PKH addresses when solo mining.

Nothing else to say here. So please stop this senseless discussion, at least I will now.

[kano]

who do you mean?i did not advertise code for free.i had quoted the patch to ask if you had referred to it in your previous reply because it was not clear.

still unanswered is your statement that this patch sends coins to a foreign address. I'd love to understand, but you don't seem to want to answer.

does anyone else know what kano means and what it has to do with this patch?

Just ignore it. Up to now he has never come up with his own approach - and he probably never will - but rather spends his time on telling other people's work off. That's the real tragedy here.

All I can say is that FOR ME, this golden-guy patch has proven to find blocks countless times on BTC testnet and other forks when solo mining on an own node. And I have tested this with lots of different addresses by now.

But this is no promo, no recommendation and you always do things at your own risk.

Quoted for posterity, coz that's a pretty specific statement you make there.

Meanwhile, as most now know, coz I pointed out why in discord weeks ago, and that info has spread, indeed 100knot2dae was telling people to use a patch that would fail if any address you used didn't start with 1.
All new wallets by default do not use 1 address.

Let it be Kano...
https://bitcointalk.org/index.php?topic=5373190.msg58531767#msg58531767
https://bitcointalk.org/index.php?topic=5373190.msg61436321#msg61436321

Yet you posted here about it and didn't point out that problem anywhere here before I pointed out the random address issue ...
You even then followed up as can be seen above "And I have tested this with lots of different addresses by now." <- which will fail with most address.
Then you didn't even bother replying with the issue but instead post shit about me - lol.
Yeah fine you mentioned it once last year, but then go around telling people here it's OK to use it without pointing out that for most of them it will fail.

You had your chance to shine on this topic for a long time, but decided against. That was your decision.

However, by now everybody who had serious interest in the solo mining topic was aware of this fact. It is with reason that e.g. the golden-guy version of cgminer has added a bitcoin address check (https://github.com/golden-guy/cgminer/commit/90d03dd12f4b7d800eb9976356875c9c003aac2e for P2PKH addresses when solo mining.

Nothing else to say here. So please stop this senseless discussion, at least I will now.

The patch you and others quoted to use
https://bitcointalk.org/index.php?topic=5373190.msg61184493#msg61184493
does NOT include that fix and you didn't point out the 1 address requirement.
That post says to use this patch:
https://github.com/golden-guy/cgminer/commit/168a1bdfedb1408a690f5387e04e3c9af7842c5e.patch
That was the reason for my post after those posts.
You fucked up and I pointed out it would generate a random address payment.
Seriously, get your facts straight.

As I said:

Be aware that the patch mentioned above will not send the coins to your address but a random address under certain circumstances.
Most people don't like thoroughly testing patches, so yeah too bad about that hey.

[citb0in]

You have enabled other code that wont always work.
Rather simple and obvious actually for a programmer.

Be aware that the patch mentioned above will not send the coins to your address but a random address under certain circumstances.
Most people don't like thoroughly testing patches, so yeah too bad about that hey.

you said that after applying this patch cgminer will not send the coins to your address but a
random address under certain circumstances.What code does the patch enable?
can you please be more specific with your reply?

No, coz in your case you are advertising code for free to people claiming it will work, without testing it properly,
with clearly no understanding of what you are doing, and people are silly enough to listen to you and some of them, if they find  a block, will not get the reward.

Yeah this place is full of hackers that think they know what they are doing but wont be found when the shit hits the fan.

If you were to actually test it properly you would 'likely' spot the obvious issue.

who do you mean?i did not advertise code for free.i had quoted the patch to ask if you had referred to it in your previous reply because it was not clear.

still unanswered is your statement that this patch sends coins to a foreign address. I'd love to understand, but you don't seem to want to answer.

does anyone else know what kano means and what it has to do with this patch?

Hiding important information when it could knowingly lead to a fatal outcome for others is simply shameful for Kano.

[...]
You are of course welcome to apply the golden-guy patch. As it was already suggested to you, you could clone the current cgminer version from Kanos' github repository and then apply the golden-guy patch. As mentioned here in the thread, there are also numerous other github repositories that include this patch, which unlocks solo mining functionality. What you should pay attention to when you manually apply the golden-guy patch --> you must NOT specify a bech32 address (begins with bc1q...) as payout address but you should exclusively use a legacy P2PKH address (begins with 1...). If you would use a bech32 as payout address (eg. bc1qxyz123abc...) then cgminer would seem to run without any problems at first sight, but if you should really hit a block, then the coinbase transaction would be erroneous and the reward would not be transferred to your specified bc1q.... (Bech32) address but to a random bitcoin address. Your reward would be lost, that would be fatal and nobody wants that. This is what Kano means with his incomplete statement and although he knows the risk, he resists to post this information here publicly, so that he can claim himself as a prophet afterwards full of glee (by actions like that). Such behavior is anything but exemplary.
[...]

Meanwhile, as most now know, coz I pointed out why in discord weeks ago, and that info has spread, indeed 100knot2dae was telling people to use a patch that would fail if any address you used didn't start with 1.
All new wallets by default do not use 1 address.

After the explanation for all understandably was revealed Kano tries in vain with such clumsy apology attempts to get up. Kano has once again successfully demonstrated his rotten and abysmal character. Congratulations.

[kano]

I said it quite clearly, learn english.

Be aware that the patch mentioned above will not send the coins to your address but a random address under certain circumstances.
Most people don't like thoroughly testing patches, so yeah too bad about that hey.

You have enabled other code that wont always work.

Rather simple and obvious actually for a programmer.

All this ranting about me coz he came to my pool, solo mined using MRR, MRR used some miners that are blocked by my pool, and then MRR kept some of his BTC coz some were blocked.

So what this is all about is Renegade seems to think that I don't have the right to block miners on my pool that have always violated MY cgminer license.

Oh well. Glad you left. Pity you stalk the discord channel under another name.

I posted that info in discord 15/12/2022 01:33 UTC
You then posted your post
Quote from: citb0in on December 18, 2022, 12:50:37 PM

[citb0in]

I don't know what kind of content you are ingesting, but you have a whole different set of problems.

You let the questioner run into the dark just like all other readers who stumble upon this thread. You knew at all times the cause and effect and are aware that this could be fatal for one if he would not use a bitcoin address with prefix 1. In spite of everything, you kept it quiet willfully in order to portray yourself as a "hero" afterwards. This becomes clear through such reactions:

Quoted for posterity, coz that's a pretty specific statement you make there.

You should get yourself checked out and take professional medical and psychological help, that's some well meaning advice.

[Yaghoob802]

I guess the true test will be if you find a block, hopefully no-one else finds it at the same time and you can propogate the results out the rest of the network fast enough so that it recognizes your result before anyone elses.

[citb0in]

And for this you have created a new forum account? Well then, congratulations on your virgin post 

[SilverDesert]

Hi all,

I cannot install the cgminer on my Ubuntu 20.04.5 LTS. I keep on getting this error message:

make[2]: *** [Makefile:999: cgminer-cgminer.o] Error 1
make[2]: Leaving directory '/home/user/bitcoin_testnet/cgminer'
make[1]: *** [Makefile:1894: all-recursive] Error 1
make[1]: Leaving directory '/home/user/bitcoin_testnet/cgminer'
make: *** [Makefile:808: all] Error 2

I have installed and updated all the libraries and tried to do the whole process over and over but I get the same end result.

Any thoughts on this issue?

[100knot2dae]

Hi all,

I cannot install the cgminer on my Ubuntu 20.04.5 LTS. I keep on getting this error message:

make[2]: *** [Makefile:999: cgminer-cgminer.o] Error 1
make[2]: Leaving directory '/home/user/bitcoin_testnet/cgminer'
make[1]: *** [Makefile:1894: all-recursive] Error 1
make[1]: Leaving directory '/home/user/bitcoin_testnet/cgminer'
make: *** [Makefile:808: all] Error 2

I have installed and updated all the libraries and tried to do the whole process over and over but I get the same end result.

Any thoughts on this issue?

Some more log lines would be helpful, but I assume it's the issue with GCC 10+ which needs the CFLAGS=-fcommon to compile the cgminer code.

[SilverDesert]

This is the sequence I used:
git clone https://github.com/kanoi/cgminer
cd cgminer
./autogen.sh
CFLAGS="-O2 -Wall -march=native -fcommon" ./configure --enable-ants3
make

[100knot2dae]

This is the sequence I used:
git clone https://github.com/kanoi/cgminer
cd cgminer
./autogen.sh
CFLAGS="-O2 -Wall -march=native -fcommon" ./configure --enable-ants3
make

That's an ancient build target, and not actively supported anymore. Try an older version that should build fine, e.g. https://github.com/vthoang/cgminer

[SilverDesert]

Thank you.
This one compiled with no issues...

[Kurtis91]

Your setup looks quite good.  But note that cgminer does not support BECH (bc1...) addresses for solo mining, so stick to legacy addresses p2pkh (1...) here.

In general, I would suggest to first mine some low diff bitcoin-forked altcoin (for example Bitflate or Widecoin) for testing purposes. So that you can verify your setup and make sure that you actually find blocks.

To avoid having the rpc password stored in plaintext in the bitcoin.conf config file, you can use rpcauth.py to generate a salted password hash, see https://github.com/bitcoin/bitcoin/blob/master/share/rpcauth/rpcauth.py

Noted and changed the BTC address. Thank you for this!

I'm not overly concerend with the RPC call showing the password in plain text as the LAN is isolated from the WAN and world so the plain text password doesn't concern me too much but I will look into modifying this in the future.

I guess the true test will be if you find a block, hopefully no-one else finds it at the same time and you can propogate the results out the rest of the network fast enough so that it recognizes your result before anyone elses.

Dedicated Fiber internet so I think I would be good on the network side.

I am most concerned if I have my setup correct!

[igorokkk]

Hello. Can't start solo mining Bitcoin :-(
My configuration: computer with Windows 7, full node Bitcoin Core 0.18.1, cgminer 4.12.   USB Miner BitForce Jalapeno 7.5 GH/s

bitcoin.conf:
listen=1
daemon=1
server=1
rpcuser=xxxxxx
rpcpassword=xxxxxxxx
rpcallowip=127.0.0.1
rpcport=3333

cgminer command:

cgminer -o http://localhost:3333 -u USER -p PASS --btc-address YOURBITCOINADDRESS