Closed timhaire closed 7 years ago
I'll look into it but I believe the pool was closed. https://vcash.miningpoolhub.com/
timhaire is pointing to the Verge-Scrypt (scrypt algo) port with vanilla algo. @timhaire did you get any shares accepted during testing?
I don't have the logs anymore as I made a number of updates since that post, but yes.
On Wed, Jun 28, 2017 at 5:29 AM, fonyo notifications@github.com wrote:
timhaire is pointing to the Verge-Scrypt (scrypt algo) port with vanilla algo. @timhaire https://github.com/timhaire did you get any shares accepted during testing?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aaronsace/MultiPoolMiner/issues/137#issuecomment-311607298, or mute the thread https://github.com/notifications/unsubscribe-auth/Ab0TnIq9RRfx7R30oriV5LM4o7khjJf4ks5sIh0FgaJpZM4NvOS6 .
-- Florida Institute of Technology Doctoral Candidate Biological Sciences - Cell and Molecular, 2017
@timhaire I don't know much about Verge-scrypt or the vanilla algo, but Verge seems to be using the scrypt algorithm and you are mining it with vanilla (Blake xx)? How is this possible?
After spending a while trying to figure out the issue I've decided to see what you suggest. I keep getting:
cpuminer-multi 1.3.1 by tpruvot@github BTC donation address: 1FhDPLPpw18X4srecguG3MxJYe4a1JsZnd (tpruvot)
[2017-06-03 18:43:59] Starting Stratum on stratum+tcp://us-east.hub.miningpoolhub.com:20533 [2017-06-03 18:43:59] 8 miner threads started, using 'vanilla' algorithm. [2017-06-03 18:44:02] stratum_recv_line failed [2017-06-03 18:44:02] ...retry after 10 seconds [2017-06-03 18:44:15] stratum_recv_line failed [2017-06-03 18:44:15] ...retry after 10 seconds [2017-06-03 18:44:29] stratum_recv_line failed [2017-06-03 18:44:29] ...retry after 10 seconds
for 0.00 PH/s 00 Days 00 Hours 00 Minutes Once Bin\CPU-TPruvot\cpuminer-gw64-corei7.exe -a vanilla -o stratum+tcp://us-east.hub.miningpoolhub.com:20533 -u _ -p x
I can get it to work fine manually with a bat file.
\MultiPoolMinerV2.5.2\Bin\CPU-TPruvot>cpuminer-gw64-corei7 -a vanilla -o stratum+tcp://hub.miningpoolhub.com:20523 -u -p x cpuminer-multi 1.3.1 by tpruvot@github BTC donation address: 1FhDPLPpw18X4srecguG3MxJYe4a1JsZnd (tpruvot)
[2017-06-03 18:45:19] Starting Stratum on stratum+tcp://hub.miningpoolhub.com:20523 [2017-06-03 18:45:19] 8 miner threads started, using 'vanilla' algorithm. [2017-06-03 18:45:19] Stratum difficulty set to 32768 [2017-06-03 18:45:19] vanilla block 1233256, diff 880.110 [2017-06-03 18:45:21] CPU #5: 3718 kH/s [2017-06-03 18:45:21] CPU #6: 3718 kH/s [2017-06-03 18:45:21] CPU #3: 3667 kH/s [2017-06-03 18:45:21] CPU #2: 3667 kH/s [2017-06-03 18:45:21] CPU #7: 3667 kH/s [2017-06-03 18:45:21] CPU #1: 3523 kH/s [2017-06-03 18:45:21] CPU #0: 3477 kH/s [2017-06-03 18:45:21] CPU #4: 3306 kH/s
I've been trying to figure it out as it was bugging me and was going through benchmarking again, so hopefully its only isolated to this particular algo. Any help is appreciated. It looks like there is a difference between the pool designations: bat - stratum+tcp://hub.miningpoolhub.com:20523 MPM - stratum+tcp://us-east.hub.miningpoolhub.com:20533
When implementing these changes in the bat file the issue is reproduced. It looks like the pool is misaligned to Vcash.