It's not me spreading the misinformation.

1. Changing the port does not mean the API is disabled.

2. Not documenting the default port does not mean the API does not exist.

3. Removing command line options that adjust API behavior does not mean the API does not exist either.

4. Changing API output format does not mean monitoring software can't use it. That's utter bullcrap. It's not like miner API output has a standard. ccminer, dstm, ethminer, excavator, zecminer, ... - they ALL use different API output formats. The monitoring software needs to handle that. In fact, the ONLY difference between hsrminer's and ccminer's output is that you need to find the SPEED key instead of KHS for hashrate, and the POWER_CONSUMPTION key instead of POWER for power usage. The API call, the key separator, the value separator, the line separator, the terminating symbol, pretty much EVERYTHING else is the same. If your "monitoring software" can't figure this out, then it's your monitoring software that's crippled, not hsrminer. If you can't realize this on your own, then I sure as hell don't want YOU to touch any of my miner executables, because that's incompetency beyond repair.

5. You even sent me a private message that you "added" an API to your "fork". I already addressed that you can't "add" something that already exists. But now let's address the fork bullcrap too. Forking means you alter the code. But hsrminer's code is not published. I pointed this out in PM already, to which you responded you "reverse engineered it". Except reverse engineering means "patching" at best, not "forking". You just mess around in the binary and pretend you're some crazy genius, while in fact you just changed some existing parameters. Like "if I change intensity, hashrate increases :O". No shit. And so does stability decrease, but never mind that. And you changed the devfee address, of course.

All I see is you spreading CONSTANT fud because you're butthurt about hsrminer. But I have no idea how anyone here can take you seriously when you have so many factual errors all the time.

To begin with, hsrminer does have an API.

So just check for a newer release?

https://github.com/ocminer/suprminer/releases/

You guys are unbelievable.

RudeHash 8.0 released with Pigeon support, mine away folks!

Dude you already have 2 AMD miners for Windows.

I don't know. They added the DNS seed fix on their own (like 1 day later), then released binaries. But they didn't publish the source code changes for it (the new release has the old sources attached to it), so I don't know what else changed But the CPU mining part sure did not.

Because lazy. My build disables CPU mining by default, along with other fixes:

https://github.com/gradinkov/pigeoncoin/releases/tag/0.15.99.0-gradinkov3

Submitted my patches long ago, no one gives any input on them, just ignore them.

Note to self: apparently it works with -T flag meaning pdcurses is broken, should rebuild on my own sometime. Thanks Ellife!

That doesn't make any sense, all DLLs and exes are 32 bit. Just inspected them all manually.

Anyhow, tried to build with older ADL SDK, you could give it  a go:

https://github.com/gradinkov/sgminer-x16s/releases/tag/gradinkov2

Just posted a few comments above, READ guys, don't just write. But others reported it to be broken. You may still give it a try tho.

I've built sgminer-x16s on Windows, it's completely untested because I don't have AMD hardware. Could anyone try it out and report back?

https://github.com/gradinkov/sgminer-x16s/releases/tag/gradinkov1

Either Help / Debug window / Console, then:


or download the wallet that has this built-in:

https://github.com/gradinkov/pigeoncoin/releases/tag/0.15.99.0-gradinkov2

FYI fresh outta oven:

https://github.com/ocminer/sgminer-x16s

No binaries yet.

Edit: oh ocminer I hate you, 40 seconds late

? the chance has been given. Is it the Pigeon devs' fault if noone comes up with an AMD miner? The algo is there for anyone to implement. Or should NV miner devs wait until AMD devs get their act together? Or... ?

AMD GPUs have always (=last 10 years) been sub-par, but the fanboys refused to realize this because they thought a GPU that's great on ONE algo (eth) is a better choice than a GPU that's great on EVERYTHING EXCEPT THAT ONE algo.

So after making bad decisions, please, by my guest, to cry me a river.

Patched wallet with added DNS seeds and secure, up-to-date OpenSSL:

https://github.com/gradinkov/pigeoncoin/releases/tag/0.15.99.0-gradinkov2

No you don't need to install CUDA 9.1, only a current NV driver.

Pigeon @ BSOD pool added to RudeHash development version.

My bad, thanks for the correction!

For wallet sync issues, put this into appdata\roaming\pigeon\pigeon.conf:

Run 2 instances, e.g.