Version 1.3.2 released!

This is a bugfix release. No change in speed expected!

[1.3.2] Support older versions of fgrlx again.
[1.3.2] Fix abort when failing to list devices of platform.
[1.3.2] Fix no reconnect after 'No such host' errors.
[1.3.2] Add --benchmark options.

330h/s sounds low for the fury. Is this on windows or linux?

1.3.1 has a bug in the automatic platform detection. If you see this error, version 1.3.1 does not work and you need to use 1.3.0 and manually specify the platform with -c.

Reduce the intensity by setting "-i 4. This should reduce the required virtual memory. It should not be much slower.

Try upgrading fgrlx 15.30.

Version 1.3.0 released!

• Further device specific optimizations bringing up to 30% increase in hash rate!
• Fix crahes with optimized kernel under Windows.

Important: Version 1.3.0 needs GPU_FORCE_64BIT_PTR=1

4rd and 3rd GCN generation cards (Nano, RX4*0) currently run slower on windows than linux. Therefore I recommend to use linux with fglrx (Nano) or amdgpu-pro (RX4*0) for those cards!


New speeds (stock card, linux):
R9 Nano: 390 S/s
R9 290X: 285 S/s
RX 480: 260 S/s

Version 1.2.0 released!

Change log:

• Fix memory leek and potential race condition.
• Improved speed, 5-15% higher hash rate, depending on the device.

This version brings kernels customized for specific devices. Currently, GCN1.1 and GCN1.2 devices are supported that use the fglrx driver. For some of those devices the new kernels are not used automatically. If you see the message "Use 'experimental-kernel' flag to unlock a more optimized version that is still experimental for this device." it means the device should be supported but it has not been tested yet. To try the new kernel just add --experimental-kernel flag to the command line.

I might add the option to specify the pool certificate fingerprint on the command line. This would allow you to mine on a pool that uses self-signed certificates in a mostly secure way.

Thanks for the reminder. I thought I had done this already. It is updated now. Please add Optiminer to the list of miners at supernova.

Nanopool uses a self-signed certificate. Optminner does not accept this as it gives this it cannot verify that there is no man-in-the-middle attack.

Optiminer/Zcash 1.1.0 released https://github.com/Optiminer/OptiminerZcash

Improved hash rates!

Yeah, I should put up a page describing the JSON format. But it should be pretty self-explaining. With -m you specify the port where the HTTP server listens on. The miner's HTTP server serves a simple JSON response (on GET /):
{
   "uptime": 121,
   "share": {
      "rejected": 0,
      "accepted": 12
   },
   "solution_rate": {
      "Total": {
         "60s": 511.416667,
         "5s": 494
      },
      "GPU0": {
         "60s": 227.7,
         "5s": 219.2
      },
      "GPU1": {
         "60s": 283.633333,
         "5s": 274.8
      }
   },
   "iteration_rate": {
      "Total": {
         "60s": 271.7,
         "5s": 270
      },
      "GPU0": {
         "60s": 120.4,
         "5s": 118.8
      },
      "GPU1": {
         "60s": 151.3,
         "5s": 151.2
      }
   },
   "stratum": {
      "target": "0020c49ba5e353f7ced916872b020c49ba5e353f7ced916872b020c49ba5e353",
      "port": 3443,
      "host": "eu1-zcash.flypool.org",
      "connection_failures": 0,
      "connected": true
   }
}

Would be great if you can add support for Optiminer to your tool.

It was clearly stated on the web page that the miner had a fee. And the shown rates were with fee deducted, so no user was tricked into anything. Code is not based on anything other, I wrote it myself from scratch.

It's up again! The pool had problems connecting to the hodlcoin server.  I do not fully understand what happened... only a fresh setup repaired things. 

Yes, it is completely different code.

Set a lower intensity value: Try adding "-i 5" to the command line.

Version 0.5.0 has been released bringing additional 5-10% of hash rate!

First release that includes Windows!