GMiner v3.44 Dero/Karlsen/Radiant/Ergo+IronFish+ZIL/KAWPOW/Equihash/Cortex

[Zminer777]

GMiner v2.11 available for download

v2.11
+ support BeamHashIII algorithm for Nvidia GPUs (for auto-switching use algo --beamhash)
+ improved Cuckatoo32 performance (up to 5%-8% dependent on GPU)
+ lowered fee for Cuckatoo32 algorithm to 2%

Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta

Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases/tag/2.11

[rgsnedds]

GMiner v2.11 available for download

v2.11
+ support BeamHashIII algorithm for Nvidia GPUs (for auto-switching use algo --beamhash)
+ improved Cuckatoo32 performance (up to 5%-8% dependent on GPU)
+ lowered fee for Cuckatoo32 algorithm to 2%

Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta

Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases/tag/2.11

my pools are ready to switch at

https://minebeam.raskul.com (US)
https://pool.raskul.com (UK)

[DanGB]

+ support BeamHashIII algorithm for Nvidia GPUs (for auto-switching use algo --beamhash)

I just tested the newest gminer update.  I pointed it to a test pool that is already past block 777777 (so on BeamHashIII) and got 18-19 Sol/s with my 1070ti's (using the same Afterburner settings as with BeamHashII).  Now the interesting thing is that I then pointed it to my node (so still BeamHashII) to solo mine and I was getting 18-19 Sol/s on there too.  I then ran against my node the previous gminer version that I had been running and it got 40+ Sol/s as I expected (again, no changes in Afterburner settings).  Any idea why I am seeing very low hashrate while mining BeamHashII with this latest version?

[Kringel]

+ improved Cuckatoo32 performance (up to 5%-8% dependent on GPU)

Now the difference between the C32 hashrate shown by gminer and that one reported by the pool became even bigger; with 1070s it's about 25% (at least on Nicehash servers). Basically, since you started declaring improved C32 hashrate back in April the actual hashrate stays more or less the same, only numbers reported by the miner "improve".

[joseph32]

+ improved Cuckatoo32 performance (up to 5%-8% dependent on GPU)

Now the difference between the C32 hashrate shown by gminer and that one reported by the pool became even bigger; with 1070s it's about 25% (at least on Nicehash servers). Basically, since you started declaring improved C32 hashrate back in April the actual hashrate stays more or less the same, only numbers reported by the miner "improve".

Same here and also reported weeks ago. Tested 12 hours with a 1080Ti-Rig.

Reported hashrate by GMiner = 4.90 G/s.
Real hashrate @ Nicehash = 4.52 G/s.

[jmart123]

Just tested BeamHash as well.  Gminer ver 2.05 gets 40 sols and ver 2.11 only gets 17 sols.  Test was with a 1070 using same card settings.  Tried both beamHashII on regular pool and BeamHashIII on test pool.  Hope this gets resolved before the Beam fork.

[DanGB]

+ support BeamHashIII algorithm for Nvidia GPUs (for auto-switching use algo --beamhash)

I just tested the newest gminer update.  I pointed it to a test pool that is already past block 777777 (so on BeamHashIII) and got 18-19 Sol/s with my 1070ti's (using the same Afterburner settings as with BeamHashII).  Now the interesting thing is that I then pointed it to my node (so still BeamHashII) to solo mine and I was getting 18-19 Sol/s on there too.  I then ran against my node the previous gminer version that I had been running and it got 40+ Sol/s as I expected (again, no changes in Afterburner settings).  Any idea why I am seeing very low hashrate while mining BeamHashII with this latest version?

We figured out what the issue is.  If you test BeamHashIII on a test pool and it is past block 777777, gminer creates a 0k file in the miner folder.  With this file there, gminer will continue to run on BeamHashIII even if you go back to a regular mainnet pool that has not yet hit block 777777.  To get your hashrate back and to have it actually mine on BeamHashII again, you must delete that 0k file.

[psiz]

beamhash-3 :   nicehash:    share rejected     share above target

[aazmega]

GMiner v2.11 available for download

v2.11
+ support BeamHashIII algorithm for Nvidia GPUs (for auto-switching use algo --beamhash)
+ improved Cuckatoo32 performance (up to 5%-8% dependent on GPU)
+ lowered fee for Cuckatoo32 algorithm to 2%

Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta

Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases/tag/2.11

using a last ver, mining with rx470 4G at simplemining OS at leafpool. Getting all incorrect shares. With and without OC.

[Wotan Wipeout]

Leafpool works, nicehash not. Share above Target. (BeamV3)

[Etherion]

i get this on nicehash

 Share Rejected: Share above target

[narousberg]

i get this on nicehash

 Share Rejected: Share above target

Same problem.

[Etherion]

Looks like gminer auto switch for beam algo does not work on nicehash. it mines the old algo. if you mine to a pool that is passed the 777777 block and then mine on Nicehash it mines the new algo. Due to the 0 file

[Wotan Wipeout]

It seems I (and maybe more people) read the description wrong.

v2.11
+ support BeamHashIII algorithm for Nvidia GPUs (for auto-switching use algo --beamhash)
+ improved Cuckatoo32 performance (up to 5%-8% dependent on GPU)
+ lowered fee for Cuckatoo32 algorithm to 2%

To mine BeamV3 the -algo is BeamhashIII

I did --beamhash and this results in invalid shares.

Greetings

Wotan

[narousberg]

It seems I (and maybe more people) read the description wrong.

v2.11
+ support BeamHashIII algorithm for Nvidia GPUs (for auto-switching use algo --beamhash)
+ improved Cuckatoo32 performance (up to 5%-8% dependent on GPU)
+ lowered fee for Cuckatoo32 algorithm to 2%

To mine BeamV3 the -algo is BeamhashIII

I did --beamhash and this results in invalid shares.

Greetings

Wotan

Thanks, its works.

[bugnotme]

GMiner v2.11 available for download

v2.11
+ support BeamHashIII algorithm for Nvidia GPUs (for auto-switching use algo --beamhash)
+ improved Cuckatoo32 performance (up to 5%-8% dependent on GPU)
+ lowered fee for Cuckatoo32 algorithm to 2%

Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta

Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases/tag/2.11

1060 3GB fails on BeamHashIII algo, while MiniZ miner performs well. Need to be fixed asap.

[d0n4ald]

GMiner v2.11 available for download

v2.11
+ support BeamHashIII algorithm for Nvidia GPUs (for auto-switching use algo --beamhash)
+ improved Cuckatoo32 performance (up to 5%-8% dependent on GPU)
+ lowered fee for Cuckatoo32 algorithm to 2%

Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta

Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases/tag/2.11

I updated to this version and am getting 25.7 sol using 1080TI (75% TDP, +175 Core, +700Mem)

is this normal? i was mining before with version 1.65 and getting around 50 sol.

[Zminer777]

GMiner v2.12 available for download

v2.12
+ improved performance for BeamHashIII algorithm (+2%-10% dependent on GPU)
+ removed auto-switching to BeamHashIII

Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta

Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases/tag/2.12

[bugnotme]

v2.12
+ improved performance for BeamHashIII algorithm (+2%-10% dependent on GPU)

1070ti - 0% improved performance, the same rate as before (~18.5 sol/s)
1060 3gb - still "out of memory" error, using miniZ got about 8.5 sol/s from card

[Zminer777]

GMiner v2.13 available for download

v2.13
+ support Qitmeer hardfork (cuckaroom29 Qitmeer algorithm)

Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta

Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases/tag/2.13