miniZv2.3c Equihash144,5 125,4 210,9 150,5 192,7 Beam ProgPoW Ethash CFX KLS PYI

[rgsnedds]

Hi,

Any info on coming Beam fork support (june 28th)

Hi MrPlus,
We are currently taking care of the last details. The release will be out today....within the next hour or so.
Cheers

and
to offer a great pool for your devfee -

https://minebeam.raskul.com (USA)
or
https://pool.raskul.com (UK)

[1714752260]

1714752260

[1714752260]

1714752260

[miniZ]

Hi everyone,

A new version miniZ v1.6v is out with added support for the new Beam algorithm - BeamHash III (144,5-siphash) - a new algorithm introduced for Beam mining in the upcoming Beam hard fork at block height 777777, expected on 28 June 2020.

miniZ will automatically switch for the new algorithm. You can mine Beam the way you have been doing currently.

We will keep working to make miniZ better. Thank you all for your feedback!

Download miniZ v1.6v here.


Changelog:
* Added support for BeamHash III. (Hashrate below)
* Fixed --show-mode option that was only showing in combination with other options.
* Included another low memory mode for 1060 3GB on ZEL. (running with --oc2)
* Completely reworked the --ocX mechanism.
* Changed kernel calls for 150,5. Let us know if it improves your driver CPU usage.
* Better default kernels for GTX1070, on stock settings, for all algorithms.

Equihash - BeamHash III:
* GTX 1050 2GB ~3.3 Sol/s
* GTX 1050 Ti 4GB ~  6.6 Sol/s
* GTX 1060 3GB ~ 8.2 Sol/s
* GTX 1660 Ti 8GB ~ 15.7 Sol/s
* GTX 1070 8GB ~ 17.4 Sol/s
* GTX 1070 Ti 8GB ~ 19.6 Sol/s
* GTX 1080 8GB ~ 19.0 Sol/s
* GTX 1080 Ti 11GB ~ 28.3 Sol/s
* RTX 2070 8GB ~ 23.2 Sol/s


Few notes:

* When adjusting your GPUs settings do not forget to check if your GPU has oc1/oc2. If so it may boost your performance a little.
  These refer to specific kernels/modes that will run in your GPU, kernels that with we found to be good when overclocking the cards. Alternatively, you can also use an option for automatic tunning of the best kernel for your GPU and OC settings --ocX, now available in all algorithms.
  For updated information read the specific topic on FAQ page.
* On Download page you can find Cuda 10 version (Linux and Windows).


For additional information check our Usage or FAQ pages.

We wish you a fast and friendly mining experience!

[rgsnedds]

now that's exceptional dev work!

well done.

[cryptosize]

Is there any special parameter that we need to use for the BEAM algo auto-switch to work properly?

Currently my batch file looks like this:

Code:

miniZ.exe --url=ssl://XXX@beam.sunpool.top:3334 --par=150,5,3 --pers=Beam-PoW --extra --latency --fee-time=72 --ocX --show-mode

[miniZ]

Is there any special parameter that we need to use for the BEAM algo auto-switch to work properly?

Currently my batch file looks like this:

Code:

miniZ.exe --url=ssl://XXX@beam.sunpool.top:3334 --par=150,5,3 --pers=Beam-PoW --extra --latency --fee-time=72 --ocX --show-mode

Hi cryptosize,
Your batch file looks fine for the autoswitch to work, however to avoid confusion we recommend that you remove the --par option. In any case, it should work both ways.
Cheers

[miniZ]

now that's exceptional dev work!

well done.

Hi rgsnedds,
Thank you for your trust and support!
Cheers

[somaton]

1.6v is broken, not working here at all, all previous versions are fine. Back to 1.5u2:

************ miniZ v1.6v ************
Number of CUDA[10.0] devices found: 4
Config:         [192.7.conf]
Algo:           EQ[192,7]
Pool#0:         user[user] server[equihash192.mine.zergpool.com] port[2144] ssl[no] pers[auto]
Pool#1:         user[user] server[equihash192.eu.mine.zpool.ca] port[2192] ssl[no] pers[auto]
Temp. limit:    [90°C]
[FATAL  ] No capable GPUs found for this algo.
[INFO   ] Disconnecting from equihash192.mine.zergpool.com
[INFO   ]equihash192.mine.zergpool.com Stopping miner
[INFO   ] Miner monitor exited.
miniZ<192,7>[6:0:00:7855]: Selecting GPU#3[3] GeForce RTX 2080 SUPER
miniZ<192,7>[6:0:00:7855]: Selecting GPU#0[0] GeForce RTX 2080 SUPER
miniZ<192,7>[6:0:00:10848]: Selecting GPU#1[1] GeForce RTX 2080 Ti
miniZ<192,7>[8:0:00:10953]: Selecting GPU#2[2] GeForce GTX 1080 Ti
[INFO   ] Exited GPU#3
[INFO   ] Exited GPU#0
[INFO   ] Exited GPU#1
[INFO   ] Exited GPU#2
[INFO   ] Disconnecting from equihash192.eu.mine.zpool.ca
************ miniZ v1.6v ************
Number of CUDA[10.0] devices found: 4
Config:         [192.7.conf]
Algo:           EQ[192,7]
Pool#0:         user[user] server[equihash192.mine.zergpool.com] port[2144] ssl[no] pers[auto]
Pool#1:         user[user] server[equihash192.eu.mine.zpool.ca] port[2192] ssl[no] pers[auto]
Temp. limit:    [90°C]
[FATAL  ] No capable GPUs found for this algo.
[INFO   ] Disconnecting from equihash192.mine.zergpool.com
[INFO   ]equihash192.mine.zergpool.com Stopping miner
[INFO   ] Miner monitor exited.
miniZ<192,7>[6:0:00:7855]: Selecting GPU#0[0] GeForce RTX 2080 SUPER
miniZ<192,7>[6:0:00:7855]: Selecting GPU#3[3] GeForce RTX 2080 SUPER
miniZ<192,7>[8:0:00:10953]: Selecting GPU#2[2] GeForce GTX 1080 Ti
miniZ<192,7>[6:0:00:10848]: Selecting GPU#1[1] GeForce RTX 2080 Ti
[INFO   ] Exited GPU#0
[INFO   ] Exited GPU#3
[INFO   ] Exited GPU#2
[INFO   ] Exited GPU#1
[INFO   ] Disconnecting from equihash192.eu.mine.zpool.ca

[miniZ]

1.6v is broken, not working here at all, all previous versions are fine. Back to 1.5u2:

Hi somaton,
We've added a check to v1.6v version that looks like it is not working for you.
Because this is not essencial, we decided to remove it. Please find a fix for you on Download page (v1.6v2).

Let us know if this is OK now. Thank you for your feedback!
Cheers

[somaton]

miniZ: Hi, yep, 1.6v2 is working fine now, that was fast, thanks

[MrPlus]

Thanks for the great work!

All rejects on NiceHash for BeamV3 it seems.
Other miner working.

[miniZ]

miniZ: Hi, yep, 1.6v2 is working fine now, that was fast, thanks

Hi somaton,
Great!
Thank you for letting us know. This could have been an issue for others too.
Cheers

[miniZ]

Thanks for the great work!

All rejects on NiceHash for BeamV3 it seems.
Other miner working.

Hi MrPlus,
NiceHash does not provide blockheight information. In this case if the algo is not specified it will start mining 150,5,3 - BeamHash II.

If you are mining to stratum+tcp://beamv3.LOCATION.nicehash.com:3387 you will need to add --par=144,5s or --par=beam3.
In the next version miniZ should be able to detect the right algo.

Thank you for your support and feedback!

Cheers

[annapotpot]

Hi,

It is good to know!

For both speed and consumption there are differences, for that GPU. Although they are not the same, they look less dissimilar if one looks at efficiencies.

It is always better to let miniZ run for a bit, so that it can be closer to a steady state. The average tends to be pretty stable making it easier to compare.

Thank you for the feedback.

Does miniz uses the "forkheight2" value returned after logging in and then compare it to the returned block height on jobs or is it hardcoded for the 777777 blockheight for BEAM? I am testing it on a testnet pool and it is not using the correct algo for the testnet since the testnets blockheight is still below 777777.

[miniZ]

Does miniz uses the "forkheight2" value returned after logging in and then compare it to the returned block height on jobs or is it hardcoded for the 777777 blockheight for BEAM? I am testing it on a testnet pool and it is not using the correct algo for the testnet since the testnets blockheight is still below 777777.

Hi annapotpot,
Thank you for your question.
Because not all pools report the "forkheight2" value, we've decided to hardcode the blockheight.
In your case you'll need to add --par=144,5s or --par=beam3 to be able to test miniZ in the testnet pool.
Cheers

[Ziv1]

Hello miniZ.
W7 125.4 1063mb
- oc 2, works (2668mb).
Does it make sense to change the working version of 1.5t or wait for the version with a new smaller kernel (at least 2800mb)?
Thanks for the work.

[miniZ]

Hello miniZ.
W7 125.4 1063mb
- oc 2, works (2668mb).
Does it make sense to change the working version of 1.5t or wait for the version with a new smaller kernel (at least 2800mb)?
Thanks for the work.

Hi Ziv1,
for Zel and 1060 3GB, the oc2 in the newest version uses a similar kernel to the one in version 1.5t.
If you experienced stability or latency issues with v1.5t then it is good to try the recent version. But if not, if the v1.5t is working well for you, and you are just mining ZEL, then there is no reason to do it.
We will try to reduce the kernel in future versions so that the 1060 3GB may also benefit in performance.
Thank you for your feedback!
Cheers

[Dark Oopa]

Hello,

I was using 1.5t2 cuda 8 on windows 7 (with 1063s).

I wanted to tried the new version but 1.5u2 nor 1.6V works. I have a message telling in is not a valid Win32 application.
I installed last NVIDIA drivers to have cuda 10 but still same message.

is it still win7 compatible?

[miniZ]

Hello,

I was using 1.5t2 cuda 8 on windows 7 (with 1063s).

I wanted to tried the new version but 1.5u2 nor 1.6V works. I have a message telling in is not a valid Win32 application.
I installed last NVIDIA drivers to have cuda 10 but still same message.

is it still win7 compatible?

Hi Dark Oopa,
We had someone with an issue that might be similar to yours.
Maybe try to update this: Redistributable Packages for Visual Studio 2015 – 2019 from Microsoft.
Let us know if this helps, or we'll try to think of another possibility.
Cheers

[Dark Oopa]

Hello,

I was using 1.5t2 cuda 8 on windows 7 (with 1063s).

I wanted to tried the new version but 1.5u2 nor 1.6V works. I have a message telling in is not a valid Win32 application.
I installed last NVIDIA drivers to have cuda 10 but still same message.

is it still win7 compatible?

Hi Dark Oopa,
We had someone with an issue that might be similar to yours.
Maybe try to update this: Redistributable Packages for Visual Studio 2015 – 2019 from Microsoft.
Let us know if this helps, or we'll try to think of another possibility.
Cheers

Hello,

thanks for the answer.
I installed vc_redist.x64.exe of Visual Studio 2015, 2017 and 2019 from https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads but it didn't change anything :/

[deskcube]

Hi Ziv1,
for Zel and 1060 3GB, the oc2 in the newest version uses a similar kernel to the one in version 1.5t.
If you experienced stability or latency issues with v1.5t then it is good to try the recent version. But if not, if the v1.5t is working well for you, and you are just mining ZEL, then there is no reason to do it.
We will try to reduce the kernel in future versions so that the 1060 3GB may also benefit in performance.
Thank you for your feedback!
Cheers

miniZ.exe --url=ssl://user@127.0.0.1:11005 --par=beam3 --pers=Beam-PoW --extra --latency --oc0 --show-mode

************ miniZ v1.6v2 ************
Number of CUDA[10.0] devices found: 1
Algo:           EQ[beam3]
Pool#0:         user[user]
                server[127.0.0.1] port[11005] ssl[yes] pers[Beam-PoW]
Telemetry:      [http://localhost:20000]
Optimisation:   oc0[0]
Temp. limit:    [90°C]
miniZ<144,5s>[00:0:00:3318]: Selecting GPU#0[0] GeForce GTX 1650
[FATAL  ] GPU[0] has invalid mode 0.
[INFO   ] Disconnecting from 127.0.0.1
[INFO   ]127.0.0.1 Stopping miner


****************
GPU 0 HAS INVALID MODE 0!!!
--oc0  --oc1 --ocx  all don't work.
I can't get this to work on GTX 1650 4GB , Win10 64, latest Nvidia drivers.
any ideas?