Hi everyone,
A new miniZ version v2.2c is out with support for EthashB3 and EvrProgPoW algorithms to mine Rethereum and Evrmore, respectively.
Please find miniZ version v2.2c @ Download page.
Changelog:
- Added support for EthashB3 algorithm (Rethereum, RTH). Fee: 1%.
- Added support for EvrProgPoW algorithm (Evrmore, EVR). Fee: 1%.
- Removed DAG generation when mining ProgPow/Ethash fee, for most cases.
- Fixed issue when mining ProgPow/KawPoW that caused miner error.
- Fixed Zil issues when mining with Nicehash.
- Small improvements for RTX40XX GPUs for 125,4 (FLUX) and 144,5 (BTG, BTCZ,…).
*** Thank you all for the feedback! ***
Remember to try --oc1/--oc2/--ocX options for optimum performance. (NVIDIA only)
For additional information check our Usage or FAQ pages.
*** Download miniZ latest version 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!
Hi,iotapi here from vipor.net. I see you added Rethereum to your miner. Hit me up here or on twitter @ViporNET or on our discord about adding your dev fee to our pool.
Greetings, it seems that there is a problem with the Hawaii kernel in Kawpow on Linux while it works on Windows
Hi merci,
Sorry but we cannot understand the issue.
Could you try to explain what is the error message? Could you paste it here?
Thank you.
Cheers
dag greater than 4GB will cause the card to fall into an unrecoverable error until the next reboot
I can’t seem to post a link ” imgur.com/ a / 6xj2tJN ” Here are some screenshots of what happens, the operating system is hiveos
Feature Request: Adding “gpuclock2” and “memclock2” for the second algo. Currently, I mine Flux and Zil and would benefit from adding these command line arguments, being because I lock the memory clock to 5000 on flux and would like the ability to unlock and add memory offset when switching to Zil and when returning back to Flux, setting the memory offset back to 0 and locking the memclock back to 5000.
Hi Curtis,
Thank you for your message. Have you tried the following options?
--gpuoffset2=[offset(MHz)]Apply list of GPU clocks offset for secondary algoEx.
--gpuoffset2=+100; For two GPUs:--gpuoffset2=+100,-120;--memoffset2=[offset(MHz)]Apply list of memory clocks offset for secondary algoEx.
--memoffset2=-500;--power2=[power(W)]Apply list of power limits for secondary algo.--power2=1will reset to stock value. (0 to ignore)(Admin/sudo is required)
Does this help?
Cheers
Unfortunately it does not help. memoffsets do not change the locked memory state, for example if i use –memclock=5000 on my rtx 3060ti to lock the memclock to 5000mhz to yield a more efficient hash/watt, I cannot change that memclock from 5000mhz with memoffset duringthe zil round. It must currently stay locked at 5000mhz throughout the zil round as well. Not a big deal for it is only a minute per round but, just suggesting it for zil runs better with a higher memory clock.
Hi, there is an issue with Zill mining with Zano i tried all pools its not connected. please advice
Hi Yousef AlZaabi,
Are you having any miner error? If so, could you paste here the error you’re getting with miniZ?
We tried the following and it is working well. The miner is connecting and sending good shares to both pools.
miniZ.exe --url=ZanoWallet.WorkerName@zano.luckypool.io:8866 --url=ZILWallet.WorkerName@eu.crazypool.org:5005 --extraIf this doesn’t help, could you paste here your command line?
Thank you.
Cheers
Not sure if you would consider this a bug or rather just a request but when dual mining with Zil, using both –mode and –zil-init parameters does not work, due to zil not supporting the set mode. It does set the mode for the main algo, but then the error being thrown on initialization cancels the prebuilding/storing the zil dag. It just reloads the zil dag every round still.
hello. i missed a option to exclude zil shares on statistics. thanks all
hello. request –show-diff2=0 to disable best share statistic was great. thx
Hello! A very angry miner who works wonders on the pool. Could you add algorithms for AMD, the same ones that exist for Nvidia? For example equihash192 and others. It’s sorely missed)
Hi Anton,
Thank you for your suggestion.
This was not a priority at the moment.
We’ll have a look and see if we’ll go in that direction .
What GPU’s are you using?
Cheers