miniZ v1.8y is out!
Hi everyone, a new miniZ version v1.8y is out with added support for Ethash mining. Fixed invalid shares on Flux mining. Improvements for 125,4 algorithm on RTX 30XX. And more…
Please find miniZ version v1.8y @ Download page.
Changelog:
- UPDATE: Fixed GTX 1660 regression while mining flux. – v1.8y2
- Added support for Ethash and Etchash mining. Ethereum mining, most Ethash coins, and Ethereum Classic.
- Improvements for Flux, on RTX 30XX.
- Fixed invalid shares on Flux, and ETH.
- Added Maxwell kernel for Beam.
- Fixed kernel for 1650 Ti, RTX 3060, and Quadro T1000 on Beam.
- Added algo and pers details to Telemetry.
- Options
--server
and--port
can be used separately. (Fixing issue with NiceHash “there is no pool selected”.) - Added
--forcenvml
, to force GPU monitoring. - Intensity option was modified.
- When no worker name is specified, miniZ doesn’t make worker=rig’s name anymore.
- No need to add stratum1 to url, for ETH, on Proshashing.
- Improved stale shares.
- No need to add stratum/stratum1/stratum2 to url, for ETH, on most pools. (Let us know if this is not the case for your pool.)
*** Thank you all for the feedback! ***
You can check Ethash performance here.
Remember to try --oc1/--oc2/--ocX
options for optimum performance.
For additional information check our Usage or FAQ pages.
*** Download miniZ version v1.8y here. ***
Engage, feedback and support
Because your feedback is very important, miniZ kindly encourages you to use the comment box below for general questions and feedback.
Certainly we will strive to help you with any doubt and provide a solution to any problem you may encounter. In case you need to reach us, please check the Support page.
Follow us
On Twitter
Our thread on bitcointalk.org
We wish you a fast and friendly mining experience!
Nice Update for Miniz! I use it for equihash since a long time. Would like try it for ETH but it missing something.
I have a Nvidia 1060 with Hynix GDDR5 memory. These card hash 19 MH instead of 24 like all other 1060. Trex miner and phonix miner have a Bootstrap or memory tweak option. When activate this option, I get 24 MH.
If you could add this, I,ll be able to use mini Z.
Thx!
Hi Frederic Gagnon,
Thank you for your suggestion and for your preference!
Which OS are you using? For Linux this should be fairly easy to implement.
Cheers
Hi, i was try use miniZ for rtx 3060 and use 150,5 algo but only get about 25 sol/s. Could i get more improvement? it’s should be around got about 40-50 sol/s with equihash 150,5 algo.
Regards,
Hi Mrencep,
Thank you for the feedback!
We’ll have a look and improve it 🙂
Cheers
Hello guys!
I have this code
but i always get an error:
QNetworkReply::RemoteHostClosedError
How i can fix this error?
PS. Also, I saw that the Chrome browser can’t get a response through a request like localhost_url/?method=getstat like my code, but the IE browser does it without problems.
Hi Till,
Thank you for contacting us.
Could you try this:
QTcpSocket socket;
socket.connectToHost("127.0.0.1", 20000);
socket.write(" getstat");
socket.waitForReadyRead(3000);
QString data= socket.readAll();
qDebug() << data.mid(data.indexOf('{'));
Let us know how it goes.
Cheers
Bugged reply visual editor version -cant type in Visual mode. Only for answer reply.
QString data= socket.readAll();
returns an empty string.
Maybe i need send to socket some JSON or something else (not simple string ” getstat”)?
ADD: PS. I know that my code probably works because I use it to work with other miners (both versions via Socket and HTTP requests).
Hi Till,
Thank you for the feedback.
Strange, it worked for us, but maybe it is because we tested on linux…
At the moment miniZ will reply only with the json string. It does not send the http headers, so QT doesn’t work when using QNetworkRequest.
We’ll include http headers in the next version!
Cheers
Hi, so I did everything for my 3060 and I also did –tune=5 and the result was 34.80 MH/s, can’t go more than that, it must go up to 40MH/s.
I’m running it on linux 5.4.0-hiveos btw.
Hi Sheraim,
With driver 460.39 it may reach 40 MH/s.
With recent drivers ~35MH/s is OK.
Maybe we’ll be able to make a small improvement for the next version.
Cheers