[LOCKED] cpuminer-opt v3.12.3, open source optimized multi-algo CPU miner

[HexxoDev]

@hexxodev

I think I've found another bug in getwork. You may want to do this before modding the zcoin miner.
It's a one line change in cpu-miner.c line 289.

Code:

bool std_work_decode( const json_t *val, struct work *work)
{
    int i;
    int data_size   = algo_gate.work_data_size;
    int target_size = sizeof(work->target);
//    int adata_sz    = ARRAY_SIZE(work->data);
    int adata_sz    = data_size / 4;
    int atarget_sz  = ARRAY_SIZE(work->target);

Your first post about 330/height/8096 was not related to our problem.
(original miner fork)

What you just posted: may be.
I try to find time  to work on this.
Sorry, im doing this left handed right now.

I guess the size.

Look:
https://github.com/hexxcointakeover/hexxcoin/blob/master/src/rpcmining.cpp#L259

If memory serves me right, original miner wont work with zcoin(solo)

I can re test it.
No need for compile any miner.
Likely it would be only waste of time.
No one ever solo mined zcoin...

[joblo]

@hexxodev

I think I've found another bug in getwork. You may want to do this before modding the zcoin miner.
It's a one line change in cpu-miner.c line 289.

Code:

bool std_work_decode( const json_t *val, struct work *work)
{
    int i;
    int data_size   = algo_gate.work_data_size;
    int target_size = sizeof(work->target);
//    int adata_sz    = ARRAY_SIZE(work->data);
    int adata_sz    = data_size / 4;
    int atarget_sz  = ARRAY_SIZE(work->target);

Your first post about 330/height/8096 was not related to our problem.

What you just posted: may be.
I try to find time  to work on this.
Sorry, im doing this left handed right now.

I guess the size.

Look:
https://github.com/hexxcointakeover/hexxcoin/blob/master/src/rpcmining.cpp#L259

If memory serves me right, original miner wont work with zcoin(solo)

Actually just a couple of lines lower...

Code:

        for (int i = 0; i < 128/4; i++)
((unsigned int*)pdata)[i] = ByteReverse(((unsigned int*)pdata)[i]);

In my code it was using the size of the struct instead of the size of the algo's data.
The struct is bigger because it needs to support algos that have bigger data.

Ignore the zcoin mod stuff for now. You're right it has nothing to do with the getwork problem.
I was thinking of using it to look at the problem from a different angle. It's always easier if there
is a working model to compare with.

[HexxoDev]

Im going to test that line updated.
1 hour...

That was something i really missed,
i saw it but forgot.

These all bugs lead upto Zcoin, Vertcoin..

Edit:
Done and testing

Edit; 128/132 no help

im going to sleep.

[joblo]

Im going to test that line updated.
1 hour...

That was something i really missed,
i saw it but forgot.

These all bugs lead upto Zcoin, Vertcoin..

Edit:
Done and testing

Edit; 128/132 no help

im going to sleep.

We're making progress faster than I expected. 128 is the correct data size.

I've found another major miss in the code, this time in cpu-miner.c line 1678.
Add one line...

Code:

            if (have_stratum)
             {
                pthread_mutex_unlock(&g_work_lock);
                continue;
             }
// add the following line
             algo_gate.get_new_work( &work, &g_work, thr_id, &end_nonce, true );

             pthread_mutex_unlock( &g_work_lock );
          }

Edit: Please add  "-D -P" options to command line to provide more output

[matejbilahora]

For information about ryzen cpu, 16 cores loaded

[HexxoDev]

Code:

[2017-03-12 13:51:58] 1 miner threads started, using 'lyra2z330' algorithm.
[2017-03-12 13:51:58] JSON protocol request:
{"method": "getblocktemplate", "params": [{"capabilities": ["coinbasetxn", "coinbasevalue", "longpoll", "workid"]}], "id
":0}


* Rebuilt URL to: http://127.0.0.1:29200/
* timeout on name lookup is not supported
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 29200 (#0)
* Server auth using Basic with user 'xxxx'
> POST / HTTP/1.1
Authorization: Basic TUFLRVVQWU9VUk9XTlVTRVI1NDY3NDU2NDVOQU1FOk1BS0VVUFk0NTY0NTY0NTY0T1VST1dOUEFTU1dPUkQ=
Host: 127.0.0.1:29200
Accept: */*
Accept-Encoding: deflate, gzip
Content-Type: application/json
Content-Length: 126
User-Agent: cpuminer-opt/3.5.13
X-Mining-Extensions: longpoll reject-reason
Expect: 100-continue

* Done waiting for 100-continue
< HTTP/1.1 200 OK
< Date: Sun, 12 Mar 2017 11:51:59 +0000
< Connection: keep-alive
< Content-Length: 486
< Content-Type: application/json
< Server: Hexxcoin-json-rpc/v3.0.0.9
<
* Connection #0 to host 127.0.0.1 left intact
[2017-03-12 13:51:59] JSON protocol response:
{
   "error": null,
   "result": {
      "version": 2,
      "target": "000000c636000000000000000000000000000000000000000000000000000000",
      "previousblockhash": "9544851be86616cf93bb72a6f616ae8e2a93c4ea7a76501fb8de62f5625e448d",
      "coinbasevalue": 1250000000,
      "sizelimit": 4000000,
      "transactions": [],
      "coinbaseaux": {
         "flags": "062f503253482f"
      },
      "mutable": [
         "time",
         "transactions",
         "prevblock"
      ],
      "mintime": 1489318795,
      "height": 20465,
      "curtime": 1489319519,
      "noncerange": "00000000ffffffff",
      "sigoplimit": 40000,
      "bits": "1e00c636"
   },
   "id": 0
}
[2017-03-12 13:51:59] Current block is 20465
[2017-03-12 13:51:59] No payout address provided, switching to getwork
[2017-03-12 13:51:59] JSON protocol request:
{"method": "getwork", "params": [], "id":0}


* Rebuilt URL to: http://127.0.0.1:29200/
* Found bundle for host 127.0.0.1: 0xa0abc0
* Re-using existing connection! (#0) with host 127.0.0.1
* Connected to 127.0.0.1 (127.0.0.1) port 29200 (#0)
* Server auth using Basic with user 'xxxx'
> POST / HTTP/1.1
Authorization: Basic TUFLRVVQWU9VUk9XTlVTRVI1NDY3NDU2NDVOQU1FOk1BS0VVUFk0NTY0NTY0NTY0T1VST1dOUEFTU1dPUkQ=
Host: 127.0.0.1:29200
Accept: */*
Accept-Encoding: deflate, gzip
Content-Type: application/json
Content-Length: 45
User-Agent: cpuminer-opt/3.5.13
X-Mining-Extensions: longpoll reject-reason
Expect: 100-continue

* Done waiting for 100-continue
< HTTP/1.1 200 OK
< Date: Sun, 12 Mar 2017 11:52:00 +0000
< Connection: keep-alive
< Content-Length: 592
< Content-Type: application/json
< Server: Hexxcoin-json-rpc/v3.0.0.9
<
* Connection #0 to host 127.0.0.1 left intact
[2017-03-12 13:52:00] JSON protocol response:
{
   "error": null,
   "result": {
      "data": "00000002625e448db8de62f57a76501f2a93c4eaf616ae8e93bb72a6e86616cf9544851ba458635750186a25ca698fba5e7072e0f
66db6c717fc5ec42e57b8bd7df17a5258c536601e00c6360000000000000080000000000000000000000000000000000000000000000000000000000
0000000000000000000000080020000",
      "midstate": "06cb9fc40aeca1a1b37d1feb82d99c0b7798bdacd6d221bc003a59db78c2f015",
      "hash1": "00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000
000000000000000000010000",
      "target": "00000000000000000000000000000000000000000000000000000036c6000000"
   },
   "id": 0
}
[2017-03-12 13:52:00] got new work in 1341.60 ms
[2017-03-12 13:52:00] JSON protocol request:
{"method": "getmininginfo", "params": [], "id":8}


* Rebuilt URL to: http://127.0.0.1:29200/
* Found bundle for host 127.0.0.1: 0xa0abc0
* Re-using existing connection! (#0) with host 127.0.0.1
* Connected to 127.0.0.1 (127.0.0.1) port 29200 (#0)
* Server auth using Basic with user 'xxxx'
> POST / HTTP/1.1
Authorization: Basic TUFLRVVQWU9VUk9XTlVTRVI1NDY3NDU2NDVOQU1FOk1BS0VVUFk0NTY0NTY0NTY0T1VST1dOUEFTU1dPUkQ=
Host: 127.0.0.1:29200
Accept: */*
Accept-Encoding: deflate, gzip
Content-Type: application/json
Content-Length: 51
User-Agent: cpuminer-opt/3.5.13
X-Mining-Extensions: longpoll reject-reason
Expect: 100-continue

* Done waiting for 100-continue
< HTTP/1.1 200 OK
< Date: Sun, 12 Mar 2017 11:52:01 +0000
< Connection: keep-alive
< Content-Length: 231
< Content-Type: application/json
< Server: Hexxcoin-json-rpc/v3.0.0.9
<
* Connection #0 to host 127.0.0.1 left intact
[2017-03-12 13:52:01] JSON protocol response:
{
   "error": null,
   "result": {
      "blocks": 20464,
      "genproclimit": -1,
      "hashespersec": 0,
      "currentblocksize": 1000,
      "currentblocktx": 0,
      "difficulty": 0.0050562100000000002,
      "errors": "",
      "generate": false,
      "networkhashps": 168115,
      "testnet": false,
      "pooledtx": 0
   },
   "id": 8
}
[2017-03-12 13:52:02] CPU #0: 2 H, 128.21 H/s
[2017-03-12 13:52:02] JSON protocol request:
{"method": "getwork", "params": [], "id":0}

I must move to linux to test that line you added.
Takes some time..

[joblo]

Code:

[2017-03-12 13:51:58] 1 miner threads started, using 'lyra2z330' algorithm.
[2017-03-12 13:51:58] JSON protocol request:
{"method": "getblocktemplate", "params": [{"capabilities": ["coinbasetxn", "coinbasevalue", "longpoll", "workid"]}], "id
":0}


* Rebuilt URL to: http://127.0.0.1:29200/
* timeout on name lookup is not supported
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 29200 (#0)
* Server auth using Basic with user 'xxxx'
> POST / HTTP/1.1
Authorization: Basic TUFLRVVQWU9VUk9XTlVTRVI1NDY3NDU2NDVOQU1FOk1BS0VVUFk0NTY0NTY0NTY0T1VST1dOUEFTU1dPUkQ=
Host: 127.0.0.1:29200
Accept: */*
Accept-Encoding: deflate, gzip
Content-Type: application/json
Content-Length: 126
User-Agent: cpuminer-opt/3.5.13
X-Mining-Extensions: longpoll reject-reason
Expect: 100-continue

* Done waiting for 100-continue
< HTTP/1.1 200 OK
< Date: Sun, 12 Mar 2017 11:51:59 +0000
< Connection: keep-alive
< Content-Length: 486
< Content-Type: application/json
< Server: Hexxcoin-json-rpc/v3.0.0.9
<
* Connection #0 to host 127.0.0.1 left intact
[2017-03-12 13:51:59] JSON protocol response:
{
   "error": null,
   "result": {
      "version": 2,
      "target": "000000c636000000000000000000000000000000000000000000000000000000",
      "previousblockhash": "9544851be86616cf93bb72a6f616ae8e2a93c4ea7a76501fb8de62f5625e448d",
      "coinbasevalue": 1250000000,
      "sizelimit": 4000000,
      "transactions": [],
      "coinbaseaux": {
         "flags": "062f503253482f"
      },
      "mutable": [
         "time",
         "transactions",
         "prevblock"
      ],
      "mintime": 1489318795,
      "height": 20465,
      "curtime": 1489319519,
      "noncerange": "00000000ffffffff",
      "sigoplimit": 40000,
      "bits": "1e00c636"
   },
   "id": 0
}
[2017-03-12 13:51:59] Current block is 20465
[2017-03-12 13:51:59] No payout address provided, switching to getwork
[2017-03-12 13:51:59] JSON protocol request:
{"method": "getwork", "params": [], "id":0}


* Rebuilt URL to: http://127.0.0.1:29200/
* Found bundle for host 127.0.0.1: 0xa0abc0
* Re-using existing connection! (#0) with host 127.0.0.1
* Connected to 127.0.0.1 (127.0.0.1) port 29200 (#0)
* Server auth using Basic with user 'xxxx'
> POST / HTTP/1.1
Authorization: Basic TUFLRVVQWU9VUk9XTlVTRVI1NDY3NDU2NDVOQU1FOk1BS0VVUFk0NTY0NTY0NTY0T1VST1dOUEFTU1dPUkQ=
Host: 127.0.0.1:29200
Accept: */*
Accept-Encoding: deflate, gzip
Content-Type: application/json
Content-Length: 45
User-Agent: cpuminer-opt/3.5.13
X-Mining-Extensions: longpoll reject-reason
Expect: 100-continue

* Done waiting for 100-continue
< HTTP/1.1 200 OK
< Date: Sun, 12 Mar 2017 11:52:00 +0000
< Connection: keep-alive
< Content-Length: 592
< Content-Type: application/json
< Server: Hexxcoin-json-rpc/v3.0.0.9
<
* Connection #0 to host 127.0.0.1 left intact
[2017-03-12 13:52:00] JSON protocol response:
{
   "error": null,
   "result": {
      "data": "00000002625e448db8de62f57a76501f2a93c4eaf616ae8e93bb72a6e86616cf9544851ba458635750186a25ca698fba5e7072e0f
66db6c717fc5ec42e57b8bd7df17a5258c536601e00c6360000000000000080000000000000000000000000000000000000000000000000000000000
0000000000000000000000080020000",
      "midstate": "06cb9fc40aeca1a1b37d1feb82d99c0b7798bdacd6d221bc003a59db78c2f015",
      "hash1": "00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000
000000000000000000010000",
      "target": "00000000000000000000000000000000000000000000000000000036c6000000"
   },
   "id": 0
}
[2017-03-12 13:52:00] got new work in 1341.60 ms
[2017-03-12 13:52:00] JSON protocol request:
{"method": "getmininginfo", "params": [], "id":8}


* Rebuilt URL to: http://127.0.0.1:29200/
* Found bundle for host 127.0.0.1: 0xa0abc0
* Re-using existing connection! (#0) with host 127.0.0.1
* Connected to 127.0.0.1 (127.0.0.1) port 29200 (#0)
* Server auth using Basic with user 'xxxx'
> POST / HTTP/1.1
Authorization: Basic TUFLRVVQWU9VUk9XTlVTRVI1NDY3NDU2NDVOQU1FOk1BS0VVUFk0NTY0NTY0NTY0T1VST1dOUEFTU1dPUkQ=
Host: 127.0.0.1:29200
Accept: */*
Accept-Encoding: deflate, gzip
Content-Type: application/json
Content-Length: 51
User-Agent: cpuminer-opt/3.5.13
X-Mining-Extensions: longpoll reject-reason
Expect: 100-continue

* Done waiting for 100-continue
< HTTP/1.1 200 OK
< Date: Sun, 12 Mar 2017 11:52:01 +0000
< Connection: keep-alive
< Content-Length: 231
< Content-Type: application/json
< Server: Hexxcoin-json-rpc/v3.0.0.9
<
* Connection #0 to host 127.0.0.1 left intact
[2017-03-12 13:52:01] JSON protocol response:
{
   "error": null,
   "result": {
      "blocks": 20464,
      "genproclimit": -1,
      "hashespersec": 0,
      "currentblocksize": 1000,
      "currentblocktx": 0,
      "difficulty": 0.0050562100000000002,
      "errors": "",
      "generate": false,
      "networkhashps": 168115,
      "testnet": false,
      "pooledtx": 0
   },
   "id": 8
}
[2017-03-12 13:52:02] CPU #0: 2 H, 128.21 H/s
[2017-03-12 13:52:02] JSON protocol request:
{"method": "getwork", "params": [], "id":0}

I must move to linux to test that line you added.
Takes some time..

The protocol dump looks ok, you can drop the -P option.

[joblo]

Closer
Atleast there is rejected after your line added.

[2017-03-12 19:24:37] 1 miner threads started, using 'lyra2z330' algorithm.
[2017-03-12 19:24:38] Current block is 1
[2017-03-12 19:24:38] No payout address provided, switching to getwork
[2017-03-12 19:25:07] CPU #0: 1086 H, 40.05 H/s
[2017-03-12 19:25:09] Rejected 1/1 (100.0%), 1086 H, 40.05 H/s, 0C
[2017-03-12 19:25:16] CPU #0: 201 H, 41.92 H/s
[2017-03-12 19:25:23] CPU #0: 210 H, 42.57 H/s
[2017-03-12 19:25:30] CPU #0: 213 H, 42.59 H/s
[2017-03-12 19:25:35] CPU #0: 102 H, 41.72 H/s
[2017-03-12 19:25:37] Rejected 2/2 (100.0%), 102 H, 41.72 H/s, 0C

Good work. It apears to be hashing properly but there is still a problem with the data,
wrong block number. Submitting a hash based on the wrong data will be rejected.

If optiminer, modified for lyra2z330, crashes on solo mining it doesn't make for a good
comparison. I may revisit this idea using cpuminer-multi if I get stuck but for now I'll
focus on verifying the data.

If I can't find anything else by analyzing the code I may build a debug load with some
extra data collection.

I'll update after analyzing the code some more.

Edit: In previous test block number was correct. Did you test differently? The code change should
not have affected this.

[ol92]

Anyone have result with Ryzen and Hexxcoin ?   .

I think it would be nice if some could compile new version incl. new ryzen cpu. I am trying to get it to work, but somehow ryzen is not so good as intel cpus for mining.
...

Hello,
Could you try with 4 threads, with affinity setted by task managers on physicals cores, two by CCX. You may try with HT disabled.
For many algo, max performance is obtained with a good choice of threads different than max number of virtual cores/physical cores.

On my 6900k@4ghz with DDR3200, I could reach around 1900 around 4-6 threads.
With a xeon 2696V3 (18 cores) max on hexxcoin is 3200 with 7 cores and some kind of turbo boost hack and bclk @140hz: 3,3-3.950 ghz (and HT disabled to have higher turbo boost).

[joblo]

Anyone have result with Ryzen and Hexxcoin ?   .

I think it would be nice if some could compile new version incl. new ryzen cpu. I am trying to get it to work, but somehow ryzen is not so good as intel cpus for mining.
...

Hello,
Could you try with 4 threads, with affinity setted by task managers on physicals cores, two by CCX. You may try with HT disabled.
For many algo, max performance is obtained with a good choice of threads different than max number of virtual cores/physical cores.

On my 6900k@4ghz with DDR3200, I could reach around 1900 around 4-6 threads.
With a xeon 2696V3 (18 cores) max on hexxcoin is 3200 with 7 cores and some kind of turbo boost hack and bclk @140hz: 3,3-3.950 ghz (and HT disabled to have higher turbo boost).

Lyra2z330 shouldn't drop in performance with too many threads the way cryptonight does. It should remain relatively steady once
it reaches it's peak.

As for compiling for Ryzen there are 2 points: compilers would first need to be updated with support for Ryzen and Ryzen contains
no new technology, it's just catching up to Intel with AVX2 (still not clear on their implementation) and hyperthreading so there's
no need for special compilation.

As with many AMD architectures compiling for native architecture is probably not the best choice, core-aes-avx2 is probably best.

[joblo]

I haven't found any more getwork bugs, it now appears functionaly identical to cpuminer-multi.
My next step is to confirm getwork works with multi, if it doesn't I have no reference to use.
But first i'll have to implement lyra2z330. Will update when available.

[HexxoDev]

I haven't found any more getwork bugs, it now appears functionaly identical to cpuminer-multi.
My next step is to confirm getwork works with multi, if it doesn't I have no reference to use.
But first i'll have to implement lyra2z330. Will update when available.

I give it a try when you are ready.
It is not only about lyra2z330, but then also other algos can have a decent miner for solo.

[ol92]

Anyone have result with Ryzen and Hexxcoin ?   .

I think it would be nice if some could compile new version incl. new ryzen cpu. I am trying to get it to work, but somehow ryzen is not so good as intel cpus for mining.
...

Hello,
Could you try with 4 threads, with affinity setted by task managers on physicals cores, two by CCX. You may try with HT disabled.
For many algo, max performance is obtained with a good choice of threads different than max number of virtual cores/physical cores.

On my 6900k@4ghz with DDR3200, I could reach around 1900 around 4-6 threads.
With a xeon 2696V3 (18 cores) max on hexxcoin is 3200 with 7 cores and some kind of turbo boost hack and bclk @140hz: 3,3-3.950 ghz (and HT disabled to have higher turbo boost).

Lyra2z330 shouldn't drop in performance with too many threads the way cryptonight does. It should remain relatively steady once
it reaches it's peak.

As for compiling for Ryzen there are 2 points: compilers would first need to be updated with support for Ryzen and Ryzen contains
no new technology, it's just catching up to Intel with AVX2 (still not clear on their implementation) and hyperthreading so there's
no need for special compilation.

As with many AMD architectures compiling for native architecture is probably not the best choice, core-aes-avx2 is probably best.

This is note what I observed with my tests (maybe because I have cpu with large cache).
With the 6900k and the xeon E5 2696V3 (= 2699V3), it seems there is a sweet spot probably related to cache size and to the memory bandwith available which can increase with threads till some optimal value (4? I suppose with quad channel): 4-6 for the 6900k (20M cache) 7 for the xeon (45m of cache, there is some turbo boost effect for the xeon with fewer threads, but the 6900k was oc @4ghz for all cores).

[joblo]

I haven't found any more getwork bugs, it now appears functionaly identical to cpuminer-multi.
My next step is to confirm getwork works with multi, if it doesn't I have no reference to use.
But first i'll have to implement lyra2z330. Will update when available.

I give it a try when you are ready.
It is not only about lyra2z330, but then also other algos can have a decent miner for solo.

Exactly. The getwork code is identical for every algo except cryptonight cryptolight. If I can get
getwork working on lyra2z330 it should also work on those other algos who support getwork.

GBT will be another issue and will require a similar iterative process to get it working.

Your testing is very much appreciated

[joblo]

I haven't found any more getwork bugs, it now appears functionaly identical to cpuminer-multi.
My next step is to confirm getwork works with multi, if it doesn't I have no reference to use.
But first i'll have to implement lyra2z330. Will update when available.

I give it a try when you are ready.
It is not only about lyra2z330, but then also other algos can have a decent miner for solo.

Exactly. The getwork code is identical for every algo except cryptonight cryptolight. If I can get
getwork working on lyra2z330 it should also work on those other algos who support getwork.

GBT will be another issue and will require a similar iterative process to get it working.

Your testing is very much appreciated

First lyra2z330 solo block with 3.5.14!
Still, not yet used original HexxCoin wallet..

That's excellent news. It's looking like the miner side is working and it's just a wallet issue now.
That means it should work with almost any coin who's wallet already supports getwork.

Keep me updated on your progress. The next release will be 3.6.0 with getwork support.

[giagge]

Guys anyone with ryzen , what is hashrate with xmr , zcoin , hexxcoin ? .

[felixbrucker]

That's excellent news. It's looking like the miner side is working and it's just a wallet issue now.
That means it should work with almost any coin who's wallet already supports getwork.

Keep me updated on your progress. The next release will be 3.6.0 with getwork support.

i have thought about writing a small tool to setup multiple wallets and only mine when nethashrate is below a certain limit
this is intended for me walking through the ann section, finding a new coin with no pools which just launched, setting it up in the tool and boom, miner starts working there till there are enough other people so its unlikely to be profitable

awesomeminer might be able to do that already im not sure, but i want it to be able to run on linux as well

will see if this project is possible in a short timeframe and if mining even works, so im glad getwork/gbt is being worked on

edit: im interested in testing as well, i have noticed the api hashrate isnt updated when using getwork it seems, it always returns 0

[joblo]

That's excellent news. It's looking like the miner side is working and it's just a wallet issue now.
That means it should work with almost any coin who's wallet already supports getwork.

Keep me updated on your progress. The next release will be 3.6.0 with getwork support.

i have thought about writing a small tool to setup multiple wallets and only mine when nethashrate is below a certain limit
this is intended for me walking through the ann section, finding a new coin with no pools which just launched, setting it up in the tool and boom, miner starts working there till there are enough other people so its unlikely to be profitable

awesomeminer might be able to do that already im not sure, but i want it to be able to run on linux as well

will see if this project is possible in a short timeframe and if mining even works, so im glad getwork/gbt is being worked on

edit: im interested in testing as well, i have noticed the api hashrate isnt updated when using getwork it seems, it always returns 0

Getwork doesn't work, yet, wait for 3.6.0.

[felixbrucker]

That's excellent news. It's looking like the miner side is working and it's just a wallet issue now.
That means it should work with almost any coin who's wallet already supports getwork.

Keep me updated on your progress. The next release will be 3.6.0 with getwork support.

i have thought about writing a small tool to setup multiple wallets and only mine when nethashrate is below a certain limit
this is intended for me walking through the ann section, finding a new coin with no pools which just launched, setting it up in the tool and boom, miner starts working there till there are enough other people so its unlikely to be profitable

awesomeminer might be able to do that already im not sure, but i want it to be able to run on linux as well

will see if this project is possible in a short timeframe and if mining even works, so im glad getwork/gbt is being worked on

edit: im interested in testing as well, i have noticed the api hashrate isnt updated when using getwork it seems, it always returns 0

Getwork doesn't work, yet, wait for 3.6.0.

i have tested with the modifications mentioned, it works!

hashrate gets displayed via api after some time (i just went shopping and returned to block found and api working)







until 3.6.0 is released i will continue testing with this modified version, maybe i find some bugs when using other wallets/coins

regarding cryptonight/cryptolight: if i understood correctly their getwork and/or gbt code is nonexistent and/or different, so coins utilizing this algo might very likely not work with solo mining?

edit: the hashrate api bug is no bug, i just noticed its the same with stratum, only after the first submitted share the api hashrate gets updated, with getwork and solomining that can take a while, maybe the api hashrate can be updated even when no shares got submitted yet?

[joblo]

Getwork doesn't work, yet, wait for 3.6.0.

i have tested with the modifications mentioned, it works!

regarding cryptonight/cryptolight: if i understood correctly their getwork and/or gbt code is nonexistent and/or different, so coins utilizing this algo might very likely not work with solo mining?

Did you get the wallet fixes?

Cryptonight doesn't support gbt and the miner will automatically disable it. In addition the getwork code, all the rpc code, is
different from all other algos, so you presumption is correct.

It is my hope that any other coin that supports getwork should now work.