Solo mine testnet bitcoins with S9 | Bitcointalksearch.org

Demontager

jr. member

Activity: 71

Merit: 6

Quote from: BitcoinSoloMiner on November 06, 2024, 10:15:44 AM

I dont think 20 minutes would be enough to accurately calculate the miners true avg hashrate, you need 24-48hour+ at a place like antpool

Nice, my question about Antminer S9 Solo tbtc mining now having separate thread. Actually all works good, since my miner already seen many days of mining before now it's not suitable for mining real btc because having many unstable chips, however it's enough for mining tbtc if miner power reduced.

For everyone, just short clarifications

Basically you need to follow original thread - Solo mine testnet bitcoins with cgminer, Bitcoin Core, and a Compac F https://bitcointalk.org/index.php?topic=5415335.60 but you dont need to setup cgminer, because Antminer has its own, which should be configured via antminer web interface.
Then you need to setup own pool with https://github.com/benjamin-wilson/public-pool

BitcoinSoloMiner

member

Activity: 152

Merit: 25

I dont think 20 minutes would be enough to accurately calculate the miners true avg hashrate, you need 24-48hour+ at a place like antpool

Demontager

jr. member

Activity: 71

Merit: 6

Quote from: ABCbits on November 04, 2024, 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.

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

jr. member

Activity: 71

Merit: 6

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

jr. member

Activity: 71

Merit: 6

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

jr. member

Activity: 71

Merit: 6

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.

Demontager

jr. member

Activity: 71

Merit: 6

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

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

jr. member

Activity: 71

Merit: 6

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

jr. member

Activity: 71

Merit: 6

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

Topic: Solo mine testnet bitcoins with S9 (Read 96 times)