[ANN] Sharecoin [SHC] - Mining that doubles as Verifiable Randomness

[Share_Coin]

Sharecoin (SHC) - a Bitcoin fork that puts your GPU's mining work to a second use

Hey all,

I've been building something in my spare time and figured this is the right place to finally put it in front of people who'd actually know what to make of it.

Sharecoin is a real fork of Bitcoin Core - not a whitepaper, not a simulation, the actual C++ source, forked and building clean. The only meaningful change is the mining algorithm: swapped from SHA-256d to ProgPoW/KawPow (the same one Ravencoin uses), so it's minable on ordinary GPUs instead of needing ASICs. Everything else - the wallet, the P2P network, the RPC interface, the scripting - is untouched upstream Bitcoin Core. If you've run a Bitcoin Core node before, you already know how to run this one.

Here's the part I actually care about, though, more than the coin itself:

Every GPU mining a ProgPoW block produces a mix_hash - a number that costs real compute to produce and can't be predicted or faked in advance. Normally that number just gets thrown away once it's done its job of proving the block. Sharecoin doesn't throw it away. There's a new RPC, getrandombeacon, that combines the mix_hash values from a run of already-confirmed blocks into a public, verifiable random number - the kind of thing you need any time you're picking a winner fairly: a raffle, a lottery drawing, deciding who goes first in a game, that sort of thing. Normally that means trusting whoever's running the drawing not to rig it, or trusting some backend server behind the scenes. With this, nobody has to trust me, or a company, or a "random number as a service" - the randomness is right there in blocks anyone can independently verify.

That's the actual use case I'm hoping people see the point of: GPUs are already burning real electricity to secure the chain. This just makes sure that work produces something useful beyond itself.

What this is NOT: it's not a pitch for the next 1000x coin, there's no presale, and I'm not asking anyone for money. It's an open-source, MIT-licensed project I'd like other people to actually use, mine, poke holes in, and build on. If the randomness beacon is useful to someone building something small - picking a winner for a giveaway, drawing raffle numbers, anything where people need to trust the result was fair - that alone would make this worth having built.

Everything you need is on GitHub: github.com/TVHeroes/sharecoin. Grab the wallet or the miner, run it, and you're straight on the live network - nothing else to set up.

Still early, still rough around the edges in places, and I'd genuinely rather hear "this part doesn't work" than silence. Happy to answer anything about how it's built or why.

[weesdr]

I tried running sharecoind on linux but the node is unable to sync. First error I got was error about disk space, it requires 856GB of data. Why does the new project require such a big storage space? I managed to resolve the first error but came across the second error below. So how do I sync my node?


2026-07-20T17:30:09Z [warning] Disk space for "/root/.sharecoin/blocks" may not accommodate the block files. Approximately 856 GB of data will be stored in this directory.
Warning: Disk space for "/root/.sharecoin/blocks" may not accommodate the block files. Approximately 856 GB of data will be stored in this directory.
2026-07-20T17:30:09Z initload thread start

---------------------------------

2026-07-20T17:35:01Z [error] Errors in block header at FlatFilePos(nFile=0, nPos=8) while reading block
2026-07-20T17:35:01Z [error] A fatal internal error occurred, see debug.log for details: Failed to read block.
Error: A fatal internal error occurred, see debug.log for details: Failed to read block.
2026-07-20T17:35:01Z [error] A fatal internal error occurred, see debug.log for details: Chainstate [ibd] @ height -1 (null) Failed to connect best block (Failed to read block.)
Error: A fatal internal error occurred, see debug.log for details: Chainstate [ibd] @ height -1 (null) Failed to connect best block (Failed to read block.)
2026-07-20T17:35:01Z Failed to open mempool file. Continuing anyway.

Also, the pool stormforge.tail0b8084.ts.net:10000 isn't working

[Share_Coin]

Thank you, I need these reports, i will fix asap and reply.
Should be fixed now, check Github.

[weesdr]

Pool "stormforge.tail0b8084.ts.net:10000" isn't working. Can you check?

[Share_Coin]

Thanks for the report, just went and checked this myself. Node and pool are both up and working right now: I connected a real miner to stormforge.tail0b8084.ts.net:10000 and it authorized and got jobs normally, and I separately re-downloaded the actual Linux package fresh and ran through the whole thing (sync, wallet, address) end to end with no issues.

Best guess for what you hit: I did several live updates to the network tonight (a few consensus fixes), each one needing a brief restart of the node and pool. If you tried connecting during one of those windows, you'd have gotten a real connection failure right then, even though it's healthy now.

Two things worth trying: just reconnect now, and if it's been a while since you grabbed the Linux package, re-download it. There was a real bug in the bundled instructions earlier (missing -regtest flag, which makes it try to sync real Bitcoin mainnet instead of Sharecoin's own network) that's since been fixed. Let me know if it's still not working after that and I'll dig further.

[weesdr]

I'm using T-rex miner and getting this error.

20260720 20:29:02 ERROR: No connection with stormforge.tail0b8084.ts.net:10000, retry after 10 seconds
20260720 20:29:12 Using protocol: stratum3.
20260720 20:29:12 WARN: failed to stratum2-subscribe on stormforge.tail0b8084.ts.net:10000: can't parse json:
* Line 1, Column 1
  Syntax error: value, object or array expected.


20260720 20:29:12 ERROR: No connection with stormforge.tail0b8084.ts.net:10000, retry after 10 seconds
20260720 20:29:22 Using protocol: stratum3.
20260720 20:29:22 WARN: failed to stratum2-subscribe on stormforge.tail0b8084.ts.net:10000: can't parse json:
* Line 1, Column 1
  Syntax error: value, object or array expected.


This is my command
./t-rex -a kawpow -o stratum+tcp://stormforge.tail0b8084.ts.net:10000 -u wallet_address -p x

I also redownloaded linux node, I'm still getting error
2026-07-20T20:28:56Z [warning] Disk space for "/root/.sharecoin/blocks" may not accommodate the block files. Approximately 856 GB of data will be stored in this directory.
Warning: Disk space for "/root/.sharecoin/blocks" may not accommodate the block files. Approximately 856 GB of data will be stored in this directory.

[Share_Coin]

Checked this directly. The server side is working, a raw stratum subscribe request gets a valid JSON-RPC response from the proxy right now.

What I think is happening with T-rex: your log shows it trying "stratum3" and "stratum2-subscribe", meaning T-rex is auto-negotiating between several stratum protocol dialects (plain Stratum V1, EthereumStratum/2.0, etc.). This pool's proxy only speaks plain Stratum V1, the same dialect kawpowminer uses and the only one this project's actually been tested against. If T-rex's auto-negotiation tries a different dialect first and gets back a response in the wrong format for what it's expecting, that would produce exactly the "can't parse json" error you're seeing, it's not that the response is malformed, it's parsing our valid V1 response as if it were a different protocol.

Worth checking T-rex's own docs/GitHub for a flag to force plain Stratum V1 instead of auto-negotiating, that should get you connected. In the meantime, kawpowminer is the one this pool's confirmed working against if you want something running now while you sort that out.

On the disk space warning: if you're still seeing that after redownloading, it means whatever command you're actually running is still missing -regtest, redownloading the package doesn't fix it by itself since the fix was in the documented commands, not something the binary enforces on its own. Can you paste the exact command you're running? Happy to spot the issue directly.

[yunta]

root@954e89324315a220:/sharecoin/bitcoin-source/build# ./bin/sharecoind \
-datadir=/tmp/sharetest
2026-07-20T20:41:33Z Sharecoin Core version v31.99.0-05056664272b-dirty (release build)
2026-07-20T20:41:33Z Log output may contain privacy-sensitive information. Be cautious when sharing logs.
2026-07-20T20:41:33Z Using the 'x86_shani(1way;2way)' SHA256 implementation
2026-07-20T20:41:33Z Using RdSeed as an additional entropy source
2026-07-20T20:41:33Z Using RdRand as an additional entropy source
2026-07-20T20:41:33Z Default data directory /root/.sharecoin
2026-07-20T20:41:33Z Using data directory /tmp/sharetest
2026-07-20T20:41:33Z Config file: /tmp/sharetest/sharecoin.conf (not found, skipping)
2026-07-20T20:41:33Z Command-line arg: datadir="/tmp/sharetest"
2026-07-20T20:41:33Z Using at most 125 automatic connections (1024 file descriptors available)
2026-07-20T20:41:33Z scheduler thread start
2026-07-20T20:41:33Z Binding RPC on address ::1 port 8332
2026-07-20T20:41:33Z Binding RPC on address 127.0.0.1 port 8332
2026-07-20T20:41:33Z Generated RPC authentication cookie /tmp/sharetest/.cookie
2026-07-20T20:41:33Z Permissions used for cookie: rw-------
2026-07-20T20:41:33Z Using random cookie authentication.
2026-07-20T20:41:33Z Starting HTTP server with 16 worker threads
2026-07-20T20:41:33Z http.00 thread start
2026-07-20T20:41:33Z http.01 thread start
2026-07-20T20:41:33Z http.02 thread start
2026-07-20T20:41:33Z http.03 thread start
2026-07-20T20:41:33Z http.04 thread start
2026-07-20T20:41:33Z http.05 thread start
2026-07-20T20:41:33Z http.06 thread start
2026-07-20T20:41:33Z http.07 thread start
2026-07-20T20:41:33Z http.08 thread start
2026-07-20T20:41:33Z http.09 thread start
2026-07-20T20:41:33Z http.10 thread start
2026-07-20T20:41:33Z http.11 thread start
2026-07-20T20:41:33Z http.12 thread start
2026-07-20T20:41:33Z http.14 thread start
2026-07-20T20:41:33Z http.13 thread start
2026-07-20T20:41:33Z http.15 thread start
2026-07-20T20:41:33Z http thread start
2026-07-20T20:41:33Z Using wallet directory /tmp/sharetest
2026-07-20T20:41:33Z Using SQLite Version 3.37.2
2026-07-20T20:41:33Z init message: Verifying wallet(s)…
2026-07-20T20:41:33Z Using /16 prefix for IP bucketing
2026-07-20T20:41:33Z init message: Loading P2P addresses…
2026-07-20T20:41:33Z Creating peers.dat because the file was not found ("/tmp/sharetest/peers.dat")
2026-07-20T20:41:33Z init message: Loading banlist…
2026-07-20T20:41:33Z Recreating the banlist database
2026-07-20T20:41:33Z SetNetworkActive: true
2026-07-20T20:41:33Z /tmp/sharetest/fee_estimates.dat is not found. Continue anyway.
2026-07-20T20:41:33Z Cache configuration:
2026-07-20T20:41:33Z * Using 2.0 MiB for block index database
2026-07-20T20:41:33Z * Using 8.0 MiB for chain state database
2026-07-20T20:41:33Z * Using 1014.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2026-07-20T20:41:33Z Script verification uses 15 additional threads
2026-07-20T20:41:33Z Using obfuscation key for blocksdir *.dat files (/tmp/sharetest/blocks): '2a1676dce80aed1f'
2026-07-20T20:41:33Z Opening LevelDB in /tmp/sharetest/blocks/index
2026-07-20T20:41:33Z Opened LevelDB successfully
2026-07-20T20:41:33Z Using obfuscation key for /tmp/sharetest/blocks/index: 0000000000000000
2026-07-20T20:41:33Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2026-07-20T20:41:33Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2026-07-20T20:41:33Z init message: Loading block index…
2026-07-20T20:41:33Z Assuming ancestors of block 00000000000000000000ccebd6d74d9194d8dcdc1d177c478e094bfad51ba5ac have valid signatures.
2026-07-20T20:41:33Z Setting nMinimumChainWork=0000000000000000000000000000000000000001128750f82f4c366153a3a030
2026-07-20T20:41:33Z Loading block index db: last block file = 0
2026-07-20T20:41:33Z Loading block index db: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2026-07-20T20:41:33Z Checking all blk files are present...
2026-07-20T20:41:33Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2026-07-20T20:41:33Z Opening LevelDB in /tmp/sharetest/chainstate
2026-07-20T20:41:33Z Opened LevelDB successfully
2026-07-20T20:41:33Z Wrote new obfuscation key for /tmp/sharetest/chainstate: ad493afc122fa449
2026-07-20T20:41:33Z Using obfuscation key for /tmp/sharetest/chainstate: ad493afc122fa449
2026-07-20T20:41:33Z prevout.00 thread start
2026-07-20T20:41:33Z prevout.01 thread start
2026-07-20T20:41:33Z prevout.02 thread start
2026-07-20T20:41:33Z prevout.03 thread start
2026-07-20T20:41:33Z prevout.04 thread start
2026-07-20T20:41:33Z prevout.05 thread start
2026-07-20T20:41:33Z prevout.06 thread start
2026-07-20T20:41:33Z Block input prevout fetching uses 8 additional threads
2026-07-20T20:41:33Z prevout.07 thread start
2026-07-20T20:41:33Z init message: Verifying blocks…
2026-07-20T20:41:33Z Block index and chainstate loaded
2026-07-20T20:41:33Z Setting NODE_NETWORK in non-prune mode
2026-07-20T20:41:33Z [warning] Disk space for "/tmp/sharetest/blocks" may not accommodate the block files. Approximately 856 GB of data will be stored in this directory.
Warning: Disk space for "/tmp/sharetest/blocks" may not accommodate the block files. Approximately 856 GB of data will be stored in this directory.
2026-07-20T20:41:33Z initload thread start
2026-07-20T20:41:33Z [error] Errors in block header at FlatFilePos(nFile=0, nPos=8) while reading block
2026-07-20T20:41:33Z [error] A fatal internal error occurred, see debug.log for details: Failed to read block.
Error: A fatal internal error occurred, see debug.log for details: Failed to read block.
2026-07-20T20:41:33Z [error] A fatal internal error occurred, see debug.log for details: Chainstate [ibd] @ height -1 (null) Failed to connect best block (Failed to read block.)
Error: A fatal internal error occurred, see debug.log for details: Chainstate [ibd] @ height -1 (null) Failed to connect best block (Failed to read block.)
2026-07-20T20:41:33Z http.00 thread exit
2026-07-20T20:41:33Z http.09 thread exit
2026-07-20T20:41:33Z Failed to open mempool file. Continuing anyway.
2026-07-20T20:41:33Z initload thread exit
2026-07-20T20:41:33Z http.13 thread exit
2026-07-20T20:41:33Z http.04 thread exit
2026-07-20T20:41:33Z Shutdown in progress...
2026-07-20T20:41:33Z http.12 thread exit
2026-07-20T20:41:33Z http.14 thread exit
2026-07-20T20:41:33Z http.03 thread exit
2026-07-20T20:41:33Z http.15 thread exit
2026-07-20T20:41:33Z http.10 thread exit
2026-07-20T20:41:33Z http.07 thread exit
2026-07-20T20:41:33Z http.06 thread exit
2026-07-20T20:41:33Z http.08 thread exit
2026-07-20T20:41:33Z http.05 thread exit
2026-07-20T20:41:33Z http.11 thread exit
2026-07-20T20:41:33Z http.01 thread exit
2026-07-20T20:41:33Z http.02 thread exit
2026-07-20T20:41:33Z http thread exit
2026-07-20T20:41:33Z scheduler thread exit
2026-07-20T20:41:33Z prevout.01 thread exit
2026-07-20T20:41:33Z prevout.05 thread exit
2026-07-20T20:41:33Z prevout.00 thread exit
2026-07-20T20:41:33Z prevout.06 thread exit
2026-07-20T20:41:33Z prevout.02 thread exit
2026-07-20T20:41:33Z prevout.07 thread exit
2026-07-20T20:41:33Z prevout.04 thread exit
2026-07-20T20:41:33Z prevout.03 thread exit
2026-07-20T20:41:33Z Shutdown done


why

[Share_Coin]

Found it, and this is a real gap on my end, not something wrong with your build. You ran sharecoind without -regtest, so it defaulted to real Bitcoin mainnet, and in this fork specifically that can't ever start: mainnet's genesis block was mined for real Bitcoin's original SHA-256d algorithm, and this fork checks proof-of-work with ProgPoW everywhere, including mainnet. That genesis can never pass validation here, so it crashes immediately instead of just running slow or wrong. Not corruption, not a bug in your build.

Try: ./bin/sharecoind -regtest -datadir=/tmp/sharetest

I've also fixed the docs, the main README and DETAILS.md never actually showed -regtest in a literal command before, which is on me. Sorry for the runaround, and thanks for the bugtesting!

[yunta]

 i 21:17:03 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 21:17:03 kawpowminer No connection. Suspend mining ...
 i 21:17:03 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 21:17:04 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 21:17:04 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 21:17:04 kawpowminer No connection. Suspend mining ...
 i 21:17:04 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 m 21:17:04 kawpowminer 0:00 A0 0.00 h -
 i 21:17:05 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 21:17:05 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 21:17:05 kawpowminer No connection. Suspend mining ...
 i 21:17:05 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 21:17:05 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 21:17:05 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 21:17:05 kawpowminer No connection. Suspend mining ...
 i 21:17:05 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 m 21:17:06 kawpowminer 0:00 A0 0.00 h -
 i 21:17:06 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 21:17:06 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 21:17:06 kawpowminer No connection. Suspend mining ...
 i 21:17:06 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 21:17:07 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 21:17:07 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 21:17:07 kawpowminer No connection. Suspend mining ...
 i 21:17:07 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 21:17:08 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 21:17:08 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 21:17:08 kawpowminer No connection. Suspend mining ...
 i 21:17:08 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 m 21:17:08 kawpowminer 0:00 A0 0.00 h -
 i 21:17:09 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 21:17:09 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000


why

[Share_Coin]

Can you share your command line?
Obv clear out your wallet address.

[yunta]

root@954e89324315a220:/linux-ubuntu20-cuda11-1.2.4# ./kawpowminer -P stratum+tcp://mxBZQHoJBDTHHdK4vT2rXhJD3EqJRBg2VR.worker1@stormforge.tail0b8084.ts.net:10000 --cu-grid-size 1 --cu-streams 1 --display-interval 2


kawpowminer 1.2.4+commit.d0e002e6
Build: linux/release/gnu

 i 21:25:33 kawpowminer Configured pool stormforge.tail0b8084.ts.net:10000
 i 21:25:33 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 21:25:34 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 21:25:34 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 21:25:34 kawpowminer No connection. Suspend mining ...
 i 21:25:34 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
^C i 21:25:35 main      Got interrupt ...
 i 21:25:35 main      Disconnected from stormforge.tail0b8084.ts.net:10000
 i 21:25:35 main      Terminated!


root@954e89324315a220:/linux-ubuntu20-cuda11-1.2.4#

[Share_Coin]

What stands out in your log: it goes straight from "Selected pool" to "Connection remotely closed" in about a second, and never shows "Established connection to...", a line every one of my own successful connections always prints first. That points to the TCP connection itself failing to complete, not a stratum/protocol issue.

I noticed your prompt shows you're running inside a Docker container. My best guess at this point is something about that container's networking, NAT, firewall rules, or DNS resolution specific to that environment, rather than anything on the server side. Worth trying either from outside the container directly on the host, or checking if there's any outbound network restriction on it. Let me know what you find, happy to keep digging if that's not it.

[yunta]

I only have an offline wallet right now. If I use this offline wallet address in the mining program, how can I check whether the mining rewards have been received?你这个矿池有很大的问题，根本用不了。我这边vast的机器访问其他矿池都没问题。我换了多个平台了，玩不了哦
 02:24:10 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:10 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:10 kawpowminer No connection. Suspend mining ...
 i 02:24:10 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 02:24:11 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:11 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:11 kawpowminer No connection. Suspend mining ...
 i 02:24:11 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 m 02:24:11 kawpowminer Not connected
 i 02:24:11 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:11 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:11 kawpowminer No connection. Suspend mining ...
 i 02:24:11 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 02:24:12 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:12 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:12 kawpowminer No connection. Suspend mining ...
 i 02:24:12 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 02:24:13 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:13 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:13 kawpowminer No connection. Suspend mining ...
 i 02:24:13 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 02:24:13 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:13 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:13 kawpowminer No connection. Suspend mining ...
 i 02:24:13 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 m 02:24:13 kawpowminer Not connected
 i 02:24:14 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:14 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:14 kawpowminer No connection. Suspend mining ...
 i 02:24:14 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 02:24:14 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:14 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:14 kawpowminer No connection. Suspend mining ...

[Share_Coin]

I only have an offline wallet right now. If I use this offline wallet address in the mining program, how can I check whether the mining rewards have been received?

You will have to sync the wallet, it's very fast.

I can check you balance on the blockchain for now. It's possible to make a website to check, like how blockchain.com does for bitcoin.

----------


Set up an alternate path for you to test, using Cloudflare's tunnel infrastructure instead of Tailscale's, different network entirely, worth trying if something's blocking the Tailscale route specifically. It needs one extra step on your end though: download cloudflared into your container, then run this in the background:

./cloudflared access tcp --hostname nine-close-santa-purposes.trycloudflare.com -L 127.0.0.1:28900

Then point kawpowminer at 127.0.0.1:28900 instead of the usual hostname, everything else about your command stays the same. If this connects where the direct route didn't, that confirms it's a routing issue specific to reaching Tailscale, not your setup or our pool. Let me know either way.

The download command needed inside the container first:

curl -L --output cloudflared https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64
chmod +x cloudflared
./cloudflared access tcp --hostname nine-close-santa-purposes.trycloudflare.com -L 127.0.0.1:28900 &

你这个矿池有很大的问题，根本用不了。我这边vast的机器访问其他矿池都没问题。我换了多个平台了，玩不了哦
 02:24:10 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:10 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:10 kawpowminer No connection. Suspend mining ...
 i 02:24:10 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 02:24:11 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:11 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:11 kawpowminer No connection. Suspend mining ...
 i 02:24:11 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 m 02:24:11 kawpowminer Not connected
 i 02:24:11 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:11 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:11 kawpowminer No connection. Suspend mining ...
 i 02:24:11 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 02:24:12 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:12 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:12 kawpowminer No connection. Suspend mining ...
 i 02:24:12 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 02:24:13 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:13 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:13 kawpowminer No connection. Suspend mining ...
 i 02:24:13 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 02:24:13 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:13 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:13 kawpowminer No connection. Suspend mining ...
 i 02:24:13 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 m 02:24:13 kawpowminer Not connected
 i 02:24:14 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:14 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:14 kawpowminer No connection. Suspend mining ...
 i 02:24:14 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 02:24:14 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 02:24:14 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 02:24:14 kawpowminer No connection. Suspend mining ...

Could you run two quick checks and paste back the output? Trying to narrow down exactly where the connection is failing.

First, check DNS resolution:
nslookup stormforge.tail0b8084.ts.net
Compare what you get against these (the real addresses it should resolve to):
2a00:dd80:3a::131
2a00:dd80:3a::336
2a00:dd80:3a::49d
176.58.88.82
176.58.92.199
176.58.88.108

Second, a traceroute:
traceroute stormforge.tail0b8084.ts.net
(if that's not installed: apt-get install -y traceroute, or try tracepath stormforge.tail0b8084.ts.net instead, doesn't need root)

What I'm looking for: if the addresses from nslookup don't match the ones above, that's DNS-level interference, something's rewriting the answer before it reaches you. If they match but the traceroute dies or times out at the same hop every time, that points to something in the network path itself. Worth knowing either way, though a clean traceroute wouldn't fully rule things out either, it uses different packet types than the actual connection, so it's a narrowing tool, not a definitive answer.

OK I have found the bug, everything should now connect fine, it was a routing issue, please try again and let me know.



Can any other users help me check and debug this, the node is up fine and even now has a backup running.

Just download the release version (windows or linux), drop in the kapowminer and dlls into the same directory as the start-mining.bat and then run it with the address you receive from the wallet app.
To get an address, simply run start-wallet.bat and create a new wallet.

[yunta]

oot@00ed24c6578f:/miner# cd linux-ubuntu20-cuda11-1.2.4/
root@00ed24c6578f:/miner/linux-ubuntu20-cuda11-1.2.4# ./kawpowminer -P stratum+tcp://mxBZQHoJBDTHHdK4vT2rXhJD3EqJRBg2VR.worker1@stormforge.tail0b8084.ts.net:10000 --cu-grid-size 1 --cu-streams 1 --display-interval 2


kawpowminer 1.2.4+commit.d0e002e6
Build: linux/release/gnu

No OpenCL platforms found
 i 12:57:10 kawpowminer Configured pool stormforge.tail0b8084.ts.net:10000
 i 12:57:10 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 12:57:10 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 12:57:10 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 12:57:10 kawpowminer No connection. Suspend mining ...
 i 12:57:10 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 12:57:10 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 12:57:10 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 12:57:10 kawpowminer No connection. Suspend mining ...
 i 12:57:10 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 12:57:10 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net
 i 12:57:10 kawpowminer Disconnected from stormforge.tail0b8084.ts.net:10000
 i 12:57:10 kawpowminer No connection. Suspend mining ...
 i 12:57:10 kawpowminer Selected pool stormforge.tail0b8084.ts.net:10000
 i 12:57:11 kawpowminer Connection remotely closed by stormforge.tail0b8084.ts.net


same!

[weesdr]

Pool isn't working no matters if I use T-rex, Rigel, NBMiner, Gminer...They all have the same issue of connecting to the pool

[Share_Coin]

Pool isn't working no matters if I use T-rex, Rigel, NBMiner, Gminer...They all have the same issue of connecting to the pool

Sorry, when I do bugfixes, the details are on the github.

I've moved the network to a new address:

./kawpowminer -P stratum+tcp://YOUR_ADDRESS.worker1@sharecoin.duckdns.org:10000 --cu-grid-size 1 --cu-streams 1 --display-interval 2

Same otherwise — just swap in your own wallet address. There's also automatic failover behind this address now, so if it's ever briefly unreachable, it should recover on its own within under a minute.

Sorry for the runaround — appreciate you sticking with it. Let me know if this connects cleanly for you now.