Solo Mining - Githubissues

crazyrigga commented 6 years ago

Hi, a little help please. I am living in a region where i got a lot of missing ping packets, timeouts and frequent disconnection from most of the chinese mining pools. Is there a way i can solo mine bcd with my nvidia rig.

crazyrigga commented 6 years ago

Well seems that BCD-qt wallet does not support "getwork" call. Ccminer can't get any mining work. Any other option to try??

ccconnor commented 6 years ago

Sorry for the late reply. The "getwork" interface is very old, we've removed it, you can try "getblocktemplate", if your software can't use it, you can also set up a stratum server, and then mine bcd with mining softwares that support stratrum, you can find mining softwares in other mining pools.

crazyrigga commented 6 years ago

Would you like to suggest any nomp pool compatible with bcd and easy to deploy.

ccconnor commented 6 years ago

I'm not sure nomp pool is compatible with bcd. You can try this https://github.com/eveybcd/stratum-mining

crazyrigga commented 6 years ago

Thank you for the help. I will look for possible solutions

juanpc2018 commented 6 years ago

this got me thinking... ccminer from vvpool does Not work with BCD Node Wallet...

bcd Node wallet fork was done after 0.10, when getwork was eliminated, because it was a security issue with a pool... getworktemplate was introduced to replace getwork command then stratum protocol was used intead with pools. https://en.bitcoin.it/wiki/Getwork https://en.bitcoin.it/wiki/Getblocktemplate https://en.bitcoin.it/wiki/Getwork_support https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list https://en.bitcoin.it/wiki/Stratum_mining_protocol https://en.bitcoin.it/wiki/Stratum

Displacing GBT The Stratum mining extensions were announced after the community had spent months developing a mostly superior open standard protocol for mining (getblocktemplate). Because stratum's mining extensions launched backed by a major mining pool, GBT adoption suffered, and decentralised mining is often neglected while stratum is deployed. Criticism Closed development The Stratum mining extensions have been criticized as having been developed behind closed doors without input from the wider development and mining community, resulting in various obvious problems that could have been addressed had it followed the standard BIP drafting process.

[2018-08-16 17:46:28] POOL 0: 192.168.137.141:7116 USER user -s 60
[2018-08-16 17:46:28] CUDA GPU 0 matches NVAPI GPU 0 by busId 1
[2018-08-16 17:46:28] NVAPI GPU monitoring enabled.
[2018-08-16 17:46:28] 1 miner thread started, using 'bcd' algorithm.
[2018-08-16 17:46:28] JSON-RPC call failed: Method not found
[2018-08-16 17:46:28] get_work failed, retry after 30 seconds

in the bitconf file. allowip, port, user, password, all ok.

seems ccminer does Not have --getblocktemplate or does Not have --no-getwork Calls getwork to BCD, but BCD responds: "No way, getwork is too old, forget it"

but there is a software: HTTP/getwork --to--> Stratum Bridge Proxy "Old Miner to Newer Pool, or maybe a New Node Wallet with Stratum?" https://github.com/slush0/stratum-mining-proxy https://mining.bitcoin.cz/media/download/mining_proxy.exe

Master was updated 6 Months Ago. dont know if the .exe also. GitHub Does Not have Compiled Releases..., the .exe is from outside. "at your own risk" ....................

`[2018-08-16 18:01:28] POOL 0: 192.168.137.141:7116 USER user -s 60 [2018-08-16 18:01:28] CUDA GPU 0 matches NVAPI GPU 0 by busId 1 [2018-08-16 18:01:28] NVAPI GPU monitoring enabled. [2018-08-16 18:01:28] 1 miner thread started, using 'bcd' algorithm. [2018-08-16 18:01:28] JSON protocol request: {"method":"getwork","params":[],"id":0}

Rebuilt URL to: http://192.168.137.141:7116/
Hostname was NOT found in DNS cache
Trying 192.168.137.141...
TCP_NODELAY set
Connected to 192.168.137.141 (192.168.137.141) port 7116 (#0)
Server auth using Basic with user 'user'

POST / HTTP/1.1 Authorization: Basic dXNlcjpwdw== Host: 192.168.137.141:7116 Accept-Encoding: deflate, gzip Content-Type: application/json Content-Length: 41 User-Agent: ccminer/alexis-1.0 X-Mining-Extensions: longpoll noncerange reject-reason X-Mining-Hashrate: 0

< HTTP/1.1 404 Not Found < Content-Type: application/json < Date: Thu, 16 Aug 2018 23:01:27 GMT < Content-Length: 76

HTTP error before end of send, stop sending <
Closing connection 0 [2018-08-16 18:01:28] JSON protocol response: { "error": { "code": -32601, "message": "Method not found" }, "result": null, "id": 0 }

[2018-08-16 18:01:28] JSON-RPC call failed: Method not found [2018-08-16 18:01:28] get_work failed, retry after 30 seconds [2018-08-16 18:01:58] JSON protocol request: {"method":"getwork","params":[],"id":0}

Rebuilt URL to: http://192.168.137.141:7116/
Hostname was found in DNS cache
Trying 192.168.137.141...
TCP_NODELAY set
Connected to 192.168.137.141 (192.168.137.141) port 7116 (#1)
Server auth using Basic with user 'user'

POST / HTTP/1.1 Authorization: Basic dXNlcjpwdw== Host: 192.168.137.141:7116 Accept-Encoding: deflate, gzip Content-Type: application/json Content-Length: 41 User-Agent: ccminer/alexis-1.0 X-Mining-Extensions: longpoll noncerange reject-reason X-Mining-Hashrate: 0

< HTTP/1.1 404 Not Found < Content-Type: application/json < Date: Thu, 16 Aug 2018 23:01:58 GMT < Content-Length: 76

HTTP error before end of send, stop sending <
Closing connection 1

juanpc2018 commented 6 years ago

mining_proxy.exe works, when used with vvpool stratum, ccminer.exe works when used with miner_proxy.exe problem is BCD-Node-Wallet

ccminer.exe -D -a bcd -o 192.168.137.162:7116 -u user -p pw --no-longpoll --no-stratum --no-extranonce
pause

mining_proxy.exe -o bcd.vvpool.com -p 5610 -oh 192.168.137.162 -gp 7116 -rt -cu 1B6jTBV51rU7yGkBhWvNQrx1iupWnbF6Vi.1234 -cp x
pause

ccminer.exe says gbt Not supported

[2018-08-16 18:37:56] gbt not supported, block height notices disabled
[2018-08-16 18:37:56] job 5b760ac3 target change: 3fffc0000 (0.3)
[2018-08-16 18:37:56] GPU#0: start=00000000 end=003fffff range=003fffff
[2018-08-16 18:37:57] GPU#0: Intensity set to 20, 1048576 cuda threads
[2018-08-16 18:37:58] GPU#0: PNY GTX 1060 6GB, 2245.12kH/s
[2018-08-16 18:37:58] GPU#0: start=00400000 end=0802f3c6 range=07c2f3c6
[2018-08-16 18:38:12] GPU#0: PNY GTX 1060 6GB, 9165.94kH/s
[2018-08-16 18:38:12] GPU#0: start=0802f3c7 end=200cd75f range=1809e398
[2018-08-16 18:38:17] found => 0aa983d5 d583a90a
[2018-08-16 18:38:17] GPU#0: PNY GTX 1060 6GB, 9099.51kH/s
[2018-08-16 18:38:17] [S/A/T]: 0/1/1, diff: 2.340, 9132.72kH/s yes!
[2018-08-16 18:38:17] GPU#0: start=00000000 end=208ad96c range=208ad96c
[2018-08-16 18:39:19] GPU#0: PNY GTX 1060 6GB, 8858.60kH/s
[2018-08-16 18:39:19] work time 62/60s nonce 208ad96c/ffffffff
[2018-08-16 18:39:19] GPU#0: start=00000000 end=1fae4ad8 range=1fae4ad8
[2018-08-16 18:39:25] found => 034096b2 b2964003
[2018-08-16 18:39:25] GPU#0: PNY GTX 1060 6GB, 8587.39kH/s
[2018-08-16 18:39:25] [S/A/T]: 0/2/2, diff: 0.339, 8927.86kH/s yes!
[2018-08-16 18:39:25] GPU#0: start=00000000 end=1eb5fd4c range=1eb5fd4c
[2018-08-16 18:39:41] found => 07d39f50 509fd307
[2018-08-16 18:39:41] GPU#0: PNY GTX 1060 6GB, 8520.84kH/s
[2018-08-16 18:39:41] [S/A/T]: 0/3/3, diff: 0.579, 8846.46kH/s yes!
[2018-08-16 18:39:41] GPU#0: start=00000000 end=1e79101c range=1e79101c
[2018-08-16 18:39:52] found => 05b6c9f6 f6c9b605
[2018-08-16 18:39:52] GPU#0: PNY GTX 1060 6GB, 8390.83kH/s
[2018-08-16 18:39:52] [S/A/T]: 0/4/4, diff: 0.325, 8770.52kH/s yes!
[2018-08-16 18:39:52] GPU#0: start=00000000 end=1e0209b8 range=1e0209b8

mining_proxy.exe

2018-08-16 18:42:52,299 INFO proxy getwork_listener._on_authorized # Worker '1B6
jTBV51rU7yGkBhWvNQrx1iupWnbF6Vi.1234' asks for new work
2018-08-16 18:43:26,641 INFO proxy client_service.handle_event # New job D317t0s
qU1y61DvdqxgV61P for prevhash 51258e1b, clean_jobs=False
2018-08-16 18:43:39,647 INFO proxy jobs.submit # Submitting f7e200d1
2018-08-16 18:43:39,648 WARNING proxy getwork_listener._on_submit # [0ms] Share
from '1B6jTBV51rU7yGkBhWvNQrx1iupWnbF6Vi.1234' accepted, diff 0
2018-08-16 18:43:39,657 INFO proxy getwork_listener._on_authorized # Worker '1B6
jTBV51rU7yGkBhWvNQrx1iupWnbF6Vi.1234' asks for new work
2018-08-16 18:43:45,924 INFO proxy jobs.submit # Submitting e211bd88
2018-08-16 18:43:45,926 WARNING proxy getwork_listener._on_submit # [0ms] Share
from '1B6jTBV51rU7yGkBhWvNQrx1iupWnbF6Vi.1234' accepted, diff 0
2018-08-16 18:43:45,930 INFO proxy getwork_listener._on_authorized # Worker '1B6
jTBV51rU7yGkBhWvNQrx1iupWnbF6Vi.1234' asks for new work
2018-08-16 18:43:47,361 INFO proxy jobs.submit # Submitting 7aef8fc5
2018-08-16 18:43:47,362 WARNING proxy getwork_listener._on_submit # [0ms] Share
from '1B6jTBV51rU7yGkBhWvNQrx1iupWnbF6Vi.1234' accepted, diff 0
2018-08-16 18:43:47,371 INFO proxy getwork_listener._on_authorized # Worker '1B6
jTBV51rU7yGkBhWvNQrx1iupWnbF6Vi.1234' asks for new work

juanpc2018 commented 6 years ago

Node-Wallet Solo Mining Not Working is a Common Problem with All Mutations / Forks of Bitcoin-Core...

for example: Credits CRDS has Argon2d Algo, internal wallet mining works, but Not external solo mining, but External Miner works with Stratum Pool... Problem is CRDS Credits Node Wallet, fork of Bitcoin code.

Bitcoin-Core developers were getting a bit crazy with the Updates. LOL. Jajajajaja

https://github.com/CRDS/Credits/ https://github.com/BeastPool/cpuminer-argon2d there is an older CRDS Fork, CRDS.io, New is CRDS.co https://github.com/Credits-CRDS/Credits

crazyrigga commented 6 years ago

I have run through the same problems and errors while trying to make it work. It seems like bcd developers were in a hurry to get large pools support so they totally ignored the solo gpu miners

crazyrigga commented 6 years ago

BTW Juanpc2018 sorry for being off topic would you like to share your o.c. settings for the gtx 1060. I only able to pull a max of 8600 kh out of my zotac gtx 1060 6gb

eveybcd / BitcoinDiamond

Solo Mining #64