[Guide] Solo mine testnet bitcoins with cgminer, Bitcoin Core, and a Compac F

Demontager

newbie

Activity: 63

Merit: 0

Quote from: ABCbits on Today at 03:57:50 AM

Quote from: Demontager on November 03, 2024, 05:24:19 AM

--snip--
I have disabled restart function and so far the miner running for 10 mins without restarts keeping approx. 9th/s hashrate.

It's a not a big deal, but why it cant reach at least 13 th/s which it has on antpool?
--snip--

I was thinking about low power enchanted mode being enabled, but you also mentioned you get 13 TH/s on Antpool. So at this point, i suggest you to create new thread on Mining support section.

Yes, i had 13 th/s on antpool for about 20 mins of testing. I further investigated miner chips and found that many already yellow and red, therefore asic runs unstable and reducing hashrate. Considering above i have reduced mining speed at the lowest possible profile 8 th/s and 600 watt power which is more than enough for mining tbtc. At that point i've mined more than i need tbtc for my development work, and i'm going to share the rest with other developers in separate thread.

Nexus9090

member

Activity: 249

Merit: 83

So many numbers and so little time

All getting a bit off-topic here... Wink

Perhaps best to export these S9 questions to a separate thread?

ABCbits

legendary

Activity: 2870

Merit: 7490

Crypto Swap Exchange

Quote from: Demontager on November 03, 2024, 05:24:19 AM

--snip--
I have disabled restart function and so far the miner running for 10 mins without restarts keeping approx. 9th/s hashrate.

It's a not a big deal, but why it cant reach at least 13 th/s which it has on antpool?
--snip--

I was thinking about low power enchanted mode being enabled, but you also mentioned you get 13 TH/s on Antpool. So at this point, i suggest you to create new thread on Mining support section.

Demontager

newbie

Activity: 63

Merit: 0

Quote from: ABCbits on November 03, 2024, 03:53:55 AM

Quote from: Demontager on November 02, 2024, 05:13:13 PM

--snip--
Miner status page showing that pool alive and it accepts blocks, but public pool log shows that antminer connects and disconnects.

Code:

getblocktemplate tx count: 3519
new block
getblocktemplate tx count: 3522
getblocktemplate tx count: 3525
getblocktemplate tx count: 3525
Killing dead clients
getblocktemplate tx count: 3527
Client d7cddb19 disconnected, hadError?:false
block height change
block height change
block height change
New client ID: : ae04772d, ::ffff:192.168.1.170:43403
getblocktemplate tx count: 3520
getblocktemplate tx count: 3522
getblocktemplate tx count: 3523
Killing dead clients
getblocktemplate tx count: 3525
getblocktemplate tx count: 3525
getblocktemplate tx count: 3526
Client ae04772d disconnected, hadError?:false
New client ID: : 5dffbf71, ::ffff:192.168.1.170:43643
getblocktemplate tx count: 3527
getblocktemplate tx count: 3529
Killing dead clients
getblocktemplate tx count: 3530
getblocktemplate tx count: 3530
getblocktemplate tx count: 3533
getblocktemplate tx count: 3535
Client 5dffbf71 disconnected, hadError?:false
Killing dead clients
New client ID: : 822fc25b, ::ffff:192.168.1.170:43965
getblocktemplate tx count: 3536

I guess it some problem with public pool config again. Previously i tested this Antminer S9 on real btc pool (antpool) and it was working fine without disconnects.

All i can suggest is to also check your S9 log, either from it's webpage[1] or SSH (if you already use custom firmware which allow that) in order to see whether S9 mention reason of the disconnection.

[1] https://support.bitmain.com/hc/en-us/articles/360025531034--For-S9series-Common-Problems-Indicated-by-Miner-s-Kernel-Log-and-Ways-to-Resolve-them

Thanks for suggestions, indeed it was related to to miner settings, i found theses messages in its watchdog logs

Code:

Sun Nov 3 08:27:36 2024 Total hashrate 9609.871 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 08:34:18 2024 Total hashrate 9653.626 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 08:41:00 2024 Total hashrate 9631.782 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 08:47:42 2024 Total hashrate 9607.137 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 08:54:24 2024 Total hashrate 9470.335 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 09:08:08 2024 Total hashrate 9635.339 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 09:14:29 2024 Total hashrate 9790.512 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 09:21:11 2024 Total hashrate 9694.529 is less than 90 percents of 13115.70, stopping miner
Sun Nov 3 09:27:53 2024 Total hashrate 9782.224 is less than 90 percents of 13115.70, stopping miner

It means miner was stopping because of hashrate threshold drop, and further i found setting which adjust this

Restart if hashrate us below given number of percents of ideal hashrate

I have disabled restart function and so far the miner running for 10 mins without restarts keeping approx. 9th/s hashrate.

It's a not a big deal, but why it cant reach at least 13 th/s which it has on antpool?

LoyceV

legendary

Activity: 3290

Merit: 16489

Thick-Skinned Gang Leader and Golden Feather 2021

Quote from: Demontager on November 03, 2024, 04:17:58 AM

i don't understand why balance showing as unmatured and on-chain separately

"New" Bitcoins need 100 confirmations before you can spend them.

Demontager

newbie

Activity: 63

Merit: 0

Okay, i left miner running while i was sleeping and despite his disconnects it mined 5 btc. But i don't understand why balance showing as unmatured and on-chain separately, these small transactions in october i got from btc faucets.

ABCbits

legendary

Activity: 2870

Merit: 7490

Crypto Swap Exchange

Quote from: Demontager on November 02, 2024, 05:13:13 PM

--snip--
Miner status page showing that pool alive and it accepts blocks, but public pool log shows that antminer connects and disconnects.

Code:

getblocktemplate tx count: 3519
new block
getblocktemplate tx count: 3522
getblocktemplate tx count: 3525
getblocktemplate tx count: 3525
Killing dead clients
getblocktemplate tx count: 3527
Client d7cddb19 disconnected, hadError?:false
block height change
block height change
block height change
New client ID: : ae04772d, ::ffff:192.168.1.170:43403
getblocktemplate tx count: 3520
getblocktemplate tx count: 3522
getblocktemplate tx count: 3523
Killing dead clients
getblocktemplate tx count: 3525
getblocktemplate tx count: 3525
getblocktemplate tx count: 3526
Client ae04772d disconnected, hadError?:false
New client ID: : 5dffbf71, ::ffff:192.168.1.170:43643
getblocktemplate tx count: 3527
getblocktemplate tx count: 3529
Killing dead clients
getblocktemplate tx count: 3530
getblocktemplate tx count: 3530
getblocktemplate tx count: 3533
getblocktemplate tx count: 3535
Client 5dffbf71 disconnected, hadError?:false
Killing dead clients
New client ID: : 822fc25b, ::ffff:192.168.1.170:43965
getblocktemplate tx count: 3536

I guess it some problem with public pool config again. Previously i tested this Antminer S9 on real btc pool (antpool) and it was working fine without disconnects.

All i can suggest is to also check your S9 log, either from it's webpage[1] or SSH (if you already use custom firmware which allow that) in order to see whether S9 mention reason of the disconnection.

[1] https://support.bitmain.com/hc/en-us/articles/360025531034--For-S9series-Common-Problems-Indicated-by-Miner-s-Kernel-Log-and-Ways-to-Resolve-them

Demontager

newbie

Activity: 63

Merit: 0

Quote

At a glance, your config seems to be right. Have you tried checking debug.log file created by Bitcoin Core? It may give some hints why public-pool unable connect to Bitcoin Core.

I'm back, had some home issues.
So, i found problem in my .env config file, BITCOIN_RPC_URL was defined in wrong way. I've added port number to it, but it should be ommited.
instead
BITCOIN_RPC_URL=http://192.168.1.181:5000
should be
BITCOIN_RPC_URL=http://192.168.1.181

And pool log now says it connected to bitcoind.

Code:

[Nest] 6983  - 11/02/2024, 11:23:17 PM     LOG [RouterExplorer] Mapped {/api/client/:address/:workerName/:sessionId, GET} route +1ms
[Nest] 6983  - 11/02/2024, 11:23:17 PM     LOG [RoutesResolver] AddressController {/api/address}: +0ms
[Nest] 6983  - 11/02/2024, 11:23:17 PM     LOG [RouterExplorer] Mapped {/api/address/settings, PATCH} route +1ms
[Nest] 6983  - 11/02/2024, 11:23:17 PM     LOG [NestApplication] Nest application successfully started +20ms
API listening on http://0.0.0.0:3334
Bitcoin RPC connected
block height change
Stratum server is listening on port 3333

Then i have configured Antminer S9 pool config as
pool: stratum+tcp://192.168.1.15:3333
Worker: mrYpN6imcBNkmsceuw5C7JjtFa9AyasEBL
password: x

Miner status page showing that pool alive and it accepts blocks, but public pool log shows that antminer connects and disconnects.

Code:

getblocktemplate tx count: 3519
new block
getblocktemplate tx count: 3522
getblocktemplate tx count: 3525
getblocktemplate tx count: 3525
Killing dead clients
getblocktemplate tx count: 3527
Client d7cddb19 disconnected, hadError?:false
block height change
block height change
block height change
New client ID: : ae04772d, ::ffff:192.168.1.170:43403
getblocktemplate tx count: 3520
getblocktemplate tx count: 3522
getblocktemplate tx count: 3523
Killing dead clients
getblocktemplate tx count: 3525
getblocktemplate tx count: 3525
getblocktemplate tx count: 3526
Client ae04772d disconnected, hadError?:false
New client ID: : 5dffbf71, ::ffff:192.168.1.170:43643
getblocktemplate tx count: 3527
getblocktemplate tx count: 3529
Killing dead clients
getblocktemplate tx count: 3530
getblocktemplate tx count: 3530
getblocktemplate tx count: 3533
getblocktemplate tx count: 3535
Client 5dffbf71 disconnected, hadError?:false
Killing dead clients
New client ID: : 822fc25b, ::ffff:192.168.1.170:43965
getblocktemplate tx count: 3536

I guess it some problem with public pool config again. Previously i tested this Antminer S9 on real btc pool (antpool) and it was working fine without disconnects.

ABCbits

legendary

Activity: 2870

Merit: 7490

Crypto Swap Exchange

Quote from: Nexus9090 on October 22, 2024, 09:23:34 AM

Is GBT outdated? I didn't think it was.

At least, i don't remember any change or update since it's created on 2012. Meanwhile Stratum V2 exist, although AFAIK the adaption is very slow.

Quote from: Nexus9090 on October 22, 2024, 09:23:34 AM

Perhaps I've misunderstood something all this time but isn't Stratum just a bridge between Bitcoin core GBT and pool services?

There's possibility some mining pool may use Bitcoin Core's GBT to create block they'll mine. But Stratum doesn't know or care how it's created.

Quote from: Demontager on October 22, 2024, 02:53:09 PM

Quote

Earlier i forget to mention you could connect S9 directly to Bitcoin Core since GBT protocol is very outdated. You may want to try that since you've failed to run public-pool.

I was able to run public pool after i match node and npm version used in docker container, but got "Error getmininginfo 404 - undefined
" error. Probably it's some issue with my configs.

At a glance, your config seems to be right. Have you tried checking debug.log file created by Bitcoin Core? It may give some hints why public-pool unable connect to Bitcoin Core.

Demontager

newbie

Activity: 63

Merit: 0

Quote

Earlier i forget to mention you could connect S9 directly to Bitcoin Core since GBT protocol is very outdated. You may want to try that since you've failed to run public-pool.

I was able to run public pool after i match node and npm version used in docker container, but got "Error getmininginfo 404 - undefined
" error. Probably it's some issue with my configs.

bitcoin_testnet.conf

Code:

testnet=1
txindex=1
server=1
[test]
rpcport=5000
rpcallowip=192.168.1.0/24
rpcuser=dem
rpcpassword=mypassword
rpcbind=0.0.0.0

.env

Code:

# bitcoin node running in your private network 192.168.1.0/24
BITCOIN_RPC_URL=http://192.168.1.181:5000

# bitcoin node running undockered on the same PC
# needs to add rpcallowip=172.16.0.0/12 to your bitcoin.conf
#BITCOIN_RPC_URL=http://host.docker.internal

BITCOIN_RPC_USER=dem
BITCOIN_RPC_PASSWORD=mypassword
BITCOIN_RPC_PORT=5000
BITCOIN_RPC_TIMEOUT=10000

# You can use this instead of BITCOIN_RPC_USER and BITCOIN_RPC_PASSWORD
BITCOIN_RPC_COOKIEFILE=

# Enable in bitcoin.conf with
# zmqpubrawblock=tcp://*:3000
# BITCOIN_ZMQ_HOST="tcp://192.168.1.100:3000"

API_PORT=3334
STRATUM_PORT=3333

#optional telegram bot
#TELEGRAM_BOT_TOKEN=

#optional discord bot
#DISCORD_BOT_CLIENTID=
#DISCORD_BOT_GUILD_ID=
#DISCORD_BOT_CHANNEL_ID=

#optional
DEV_FEE_ADDRESS=
# mainnet | testnet
NETWORK=testnet

API_SECURE=false
# Default is "public-pool", you can change it to any string it will be removed if it will make the block or coinbase script too big
POOL_IDENTIFIER="public-pool"

And actual error after starting public pool

Code:

$ npm run start

> [email protected] start
> nest start

[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [NestFactory] Starting Nest application...
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] TypeOrmModule dependencies initialized +117ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] HttpModule dependencies initialized +1ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] CacheModule dependencies initialized +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] ConfigHostModule dependencies initialized +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] DiscoveryModule dependencies initialized +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] ConfigModule dependencies initialized +1ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] ScheduleModule dependencies initialized +1ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] TypeOrmCoreModule dependencies initialized +37ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] TypeOrmModule dependencies initialized +1ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] TypeOrmModule dependencies initialized +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] TypeOrmModule dependencies initialized +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] TypeOrmModule dependencies initialized +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] TypeOrmModule dependencies initialized +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] TypeOrmModule dependencies initialized +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] ClientStatisticsModule dependencies initialized +1ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] ClientModule dependencies initialized +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] AddressSettingsModule dependencies initialized +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] TelegramSubscriptionsModule dependencies initialized +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] BlocksModule dependencies initialized +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] RpcBlocksModule dependencies initialized +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [InstanceLoader] AppModule dependencies initialized +4ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [RoutesResolver] AppController {/api}: +32ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [RouterExplorer] Mapped {/api/info, GET} route +5ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [RouterExplorer] Mapped {/api/pool, GET} route +1ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [RouterExplorer] Mapped {/api/network, GET} route +1ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [RouterExplorer] Mapped {/api/info/chart, GET} route +1ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [RoutesResolver] ClientController {/api/client}: +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [RouterExplorer] Mapped {/api/client/:address, GET} route +1ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [RouterExplorer] Mapped {/api/client/:address/chart, GET} route +1ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [RouterExplorer] Mapped {/api/client/:address/:workerName, GET} route +1ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [RouterExplorer] Mapped {/api/client/:address/:workerName/:sessionId, GET} route +1ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [RoutesResolver] AddressController {/api/address}: +0ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [RouterExplorer] Mapped {/api/address/settings, PATCH} route +1ms
[Nest] 13117  - 10/22/2024, 10:43:11 PM     LOG [NestApplication] Nest application successfully started +24ms
API listening on http://0.0.0.0:3334
Could not reach RPC host
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Error getmininginfo 404 - undefined
Stratum server is listening on port 3333
Error getmininginfo 404 - undefined

Quote

2. Ignore step 2 of tutorial on this thread. You need to configure your S9 connect to your Bitcoin Core directly using RPC url, user and password (which use GBT protocol) or your own mining pool (which use stratum protocol).

I can't get how to set bitcoin testnet address and rpc username and password in asic config.

I tried to set as:
URL: http://dem:[email protected]:5000
Worker: bitcoin_testnet_address
Password: x

but it does not work, miner reports Dead pool

Nexus9090

member

Activity: 249

Merit: 83

So many numbers and so little time

Quote from: ABCbits on October 21, 2024, 03:54:42 AM

-SNIP-

connect to your Bitcoin Core directly using RPC url, user and password (which use GBT protocol) or your own mining pool (which use stratum protocol).

-SNIP-

since GBT protocol is very outdated.

Hi ABCbits,

Sorry jumping on your thread updates here.

Is GBT outdated? I didn't think it was. Perhaps I've misunderstood something all this time but isn't Stratum just a bridge between Bitcoin core GBT and pool services?

Thanks

G.

ABCbits

legendary

Activity: 2870

Merit: 7490

Crypto Swap Exchange

Quote from: Demontager on October 21, 2024, 12:31:06 PM

Quote from: ABCbits on October 21, 2024, 03:54:42 AM

Quote from: Demontager on October 19, 2024, 04:42:30 PM

Did anyone try antminer s9 (14 th) ?
I wish to try to mine test btc and looking for some reliable old miner.

FYI, AntMiner S9 has it's own OS/computer.

Well, I have received S9 and checked it's work on antpool, seems all fine getting 13.1Th/s. Miner running Hiveon ASIC.
But i don't understand why i can't use tutorial from that thread to mine testing btc.

UPD.
Tried to use https://github.com/benjamin-wilson/public-pool and it failed to build in docker and wont run with npm run start
Anyway i opened github issue, might someone help to resolve.

I never say it's impossible, but rather need to change some steps. I don't own S9 or any similar ASIC, but roughly you need to.
1. Follow step 1 of tutorial on this thread. If you don't know IP of your S9, you could use rpcallowip=192.168.0.0/16.
2. Ignore step 2 of tutorial on this thread. You need to configure your S9 connect to your Bitcoin Core directly using RPC url, user and password (which use GBT protocol) or your own mining pool (which use stratum protocol).

Earlier i forget to mention you could connect S9 directly to Bitcoin Core since GBT protocol is very outdated. You may want to try that since you've failed to run public-pool.

Demontager

newbie

Activity: 63

Merit: 0

Quote from: ABCbits on October 21, 2024, 03:54:42 AM

Quote from: Demontager on October 19, 2024, 04:42:30 PM

Did anyone try antminer s9 (14 th) ?
I wish to try to mine test btc and looking for some reliable old miner.

FYI, AntMiner S9 has it's own OS/computer.

Well, I have received S9 and checked it's work on antpool, seems all fine getting 13.1Th/s. Miner running Hiveon ASIC.
But i don't understand why i can't use tutorial from that thread to mine testing btc.

UPD.
Tried to use https://github.com/benjamin-wilson/public-pool and it failed to build in docker and wont run with npm run start
Anyway i opened github issue, might someone help to resolve.

ABCbits

legendary

Activity: 2870

Merit: 7490

Crypto Swap Exchange

Quote from: Demontager on October 19, 2024, 04:42:30 PM

Did anyone try antminer s9 (14 th) ?
I wish to try to mine test btc and looking for some reliable old miner.

FYI, AntMiner S9 has it's own OS/computer. You'll need to run your own mining pool software such as https://github.com/benjamin-wilson/public-pool or https://github.com/tpruvot/yiimp, then point your S9 to IP which run the software.

Demontager

newbie

Activity: 63

Merit: 0

Did anyone try antminer s9 (14 th) ?
I wish to try to mine test btc and looking for some reliable old miner.

Nexus9090

member

Activity: 249

Merit: 83

So many numbers and so little time

You're welcome. I've spent days chasing typo's before it can get real frustrating.

Good you got it working.

?

Activity: -

Merit: -

Quote from: Nexus9090 on October 04, 2024, 12:58:34 PM

Try your local net address instead of what I think you have mistyped.

127.0.0.1 not 172.0.0.1

Thank you sooooooooooo very much for this! I spent days trying and trying and couldn't find what I missed. It works now.

Nexus9090

member

Activity: 249

Merit: 83

So many numbers and so little time

Try your local net address instead of what I think you have mistyped.

127.0.0.1 not 172.0.0.1

?

Activity: -

Merit: -

I bought a second hand red compac F miner, and followed your instructions. I need help to get it working.

Bitcoin Core, cgminer and the compac F are installed on the same system.

Quote from: nullama on September 29, 2022, 05:31:36 AM

Now let's prepare the configuration file. Create a text file named bitcoin_testnet.conf in ~/bitcoin_testnet/ and put these content in it:

I use this:

Code:

testnet=1
txindex=0
server=1
[test]
rpcport=5000
rpcallowip=172.0.0.1
rpcuser=USESR
rpcpassword=PASS
rpcbind=0.0.0.0
prune=550

Quote from: nullama on September 29, 2022, 05:31:36 AM

Now, in theory we should be ready, but we need one extra change. Open the file cgminer.c with your favorite text editor and change this line:

Code:

if (opt_btc_address[0] != '1') {

To this:

Code:

if (opt_btc_address[0] != '1' && opt_btc_address[0] != 'm' && opt_btc_address[0] != 'n'  ) {

I think I can skip this because the code on github is updated already:

Code:

      switch (opt_btc_address[0]) {
            case '1':
            case 'm':
            case 'n':
                  break;
            default:
                  applog(LOG_ERR, "Bitcoin address %s is NOT a P2PKH address, unable to mine solo on %s",
                         opt_btc_address, pool->rpc_url);
                  goto out;
      }

.

Quote from: nullama on September 29, 2022, 05:31:36 AM

Create a text file named ~/bitcoin_testnet/cgminer_testnet.conf with these contents:

I use this (last comma removed, thanks n0nce)

Code:

{
"pools" : [
        {
                "url" : "http://172.0.0.1:5000",
                "user" : "USER",
                "pass" : "PASS"
        }
],

"btc-address": "moZKMsGTNSd3Ngu5i6RN7CC7PHaQ5wd5ms",

"gekko-compacf-freq" : "400",
"gekko-compacf-detect" : true,
"gekko-start-freq" : "300",
"gekko-mine2" : true,
"gekko-tune2" : "60",

"suggest-diff" : "442",
"failover-only" : true
}

Quote from: nullama on September 29, 2022, 05:31:36 AM

And now you can simply run cgminer like this:

Code:

sudo /home/user/bitcoin_testnet/cgminer/cgminer -c /home/user/bitcoin_testnet/mine_testnet.conf

It doesn't work. I get:

Code:

[date] Started cgminer 4..12.1

A minute later:

Code:

Loaded configuration file ../cgminer_testnet.conf
Probing for an alive pool
No servers were found that could be used to get work from.
Please check the details from the list below of the servers you have input
Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers
Pool: 0 URL: http://172.0.0.1:5000 User: USER Password: PASS
Press any key to exit, or cgminer will wait indefinitely for an alive pool.

2 minutes later:

Code:

No Stratum, GBT or Solo support in pool 0 http://172.0.0.1:500 unable to use

Why can't cgminer connect to Bitcoin Core? What do I have to change?

Nexus9090

member

Activity: 249

Merit: 83

So many numbers and so little time

Quote from: nullama on July 09, 2024, 07:29:46 AM

Quote from: Nexus9090 on May 29, 2024, 06:22:05 AM

~snip~
I merged the changes from https://github.com/cmmodtools/cgminer into the last maintained version of cgminer 4.12.1 https://github.com/kanoi/cgminer/ and getting it to build

Nice, I wonder if kano would be OK bringing those changes upstream.

At least for me, @kano branch of cgminer is the one that I use whenever I build cgminer after CKolivas stopped development.

Hopefully there is only one branch with all the required changes.

The changes aren't that difficult to do if you're careful patching them into the correct locations. If I recall most of it is in cgminer.c and there's only a handfull of functions that are affected.

I'm no expert on driving GIT otherwise I'd create my own branch with the adaptations already done.

I don't know if Kano is interested in porting in the GBT mods from cmmodtools, they released these updates quite a long time ago and its never made it back into the master branch.

Topic: [Guide] Solo mine testnet bitcoins with cgminer, Bitcoin Core, and a Compac F (Read 1805 times)