maynardminer / mm.hash Goto Github PK

AMD is currently expiremental in MM.Hash. There are some miners that do not use api/and or require unique tactics to get hashrate/mining information.

I am looking for AMD testers and other individuals to help beta test AMD side in order to fully integrate AMD into MM.Hash and by extension integrate profit switching for AMD into HiveOS

In 1.3.9 I changed bench-marking so that stats will be set to zero if it fails benchmarking 3 times in a row. This is different from it setting to zero if it fails benchmarking just once.

I was informed on bitcointalk by a user that this may not be working. However, on my version it seems to be working fine- I have not been stuck on an algo/coin that was dead.

Please let me know if anyone can reproduce. I will be testing thoroughly tonight to make sure it works as intended.

I noticed that linux powershell is being wishy-washy with converting current time to universal time. This may cause some weird stat-fluctuations after 24 hours, which effect long-term hashrate cacluations. I'm working on how to make a linux shell script to call UTC time. At least this is happening with my version.

For now, I recommend running miner in Static benchmark mode after bench-marking (Close Miner, Open Configuration file you are using, set StatInterval to 1000 like instruction in file).

This bug only happens near/after 24 hours of mining, and will not happen if you are not using Dynamic Hashrate mode (Which is advised not to use anyways if you are mining algos like x16r).

I will patch very soon.

Just wanted people to know that my latest commit involves some experimental testing I am doing for advanced miner settings...Which will include being able to customize individual devices.

I am not sure how stable the miner will be with the last commits, so use with caution until all bugs are worked out. As of now- the Advanced settings were not working, It doesn't send argument script for miner devices to CCMiner arguments correctly. I uploaded it so people can see what I am doing, and how I'm trying to make them work.

I have been noticing that HMQ1725 algo using Tpruvot CCminer has not been stable for on my miner- It continues to shutdown. Please let me know if anyone else can reproduce.

I am looking for another compilable ccminer that supports HMQ1725.

When I performed my last commit, I noticed the USD/Day calculation was off, as least when calculating it for RVN (What I auto-exchange to). However, even with the absurd figures- It was still prioritizing miners correctly, just the amount displayed was off.

I am working on a fix for it.

I am still receiving occasional reports as of beta 1.4.6b of miner not disabling an algorithm (setting hashrate to zero) after it has failed to benchmark three times.

I am having trouble determining the specific cause of this bug, as I cannot replicate it no matter how many attempts I try.

I'm going to try to a different approach, and re-write how the timeout system works, including removing -Timeout parameter as it is depreciated (was for old coin database).

I noticed with my miner, along with other mining software that I used in the past, the donation parameter is inaccurate. It starts donating an hour after you restart the program...Then waits 24 hours. This both can screw dev and/or user...Depending on whether or not they are constantly restarting or not.

Next release fixes that, and turns donation into a percentage, in which any figure can be used. It also remembers when you last started or closed mine, preventing the app from donating when it shouldn't be, as I saw in some of the other mining programs.

Explanation will be in new release of operation in a file called Dev notes.

There is a bug with new version regarding blakecoin algo. I'm too concerned about it as blakecoin doesn't have a lot of profitability as of now.

To workaround it, us argument -No_Algo blakecoin

HiveOS has upgraded to 18.04.

I have a new test version here:

https://github.com/MaynardMiner/MM.Test/releases/tag/v.1.4.6b

If you are having issues with installing powershell, or miner basically won't start, try the following:

sudo apt-get install libunwind8 libicu55 -y

into a terminal. Then start miner.

If it doesn't work, contact me in discord channel on readme.

I am working on testing and getting everything work now.

Next release ensure new terminal window for miners open to the side of main program, and doesn't stack or overlap. This means they will open, but not obscure main window. I'm trying to do it in a manner which uses as little of resources as possible, knowing that a potential for MM.Hash is using it in ARM based micro-controllers.

I also will be fixing small visual issues I noticed. Any other requests before I release, let me know.

Note- I tried to fix it so that "Idle" miners will display total time they ran, and reset 24 hours...It's a lot more difficult than I thought, so I'm leaving go for now.

Full explanation will be a file called Dev Notes when I commit.

KlausT will compile under cuda 9.1 and work. However, I noticed I would get memory() free pointer error when using with 1070. No issues with 1050ti. I am talking to KlausT now about issue, and for the time being left his miner inside MM.Hash, but not used.

Since his miner is up to date, My miner will not autocompile it yet. His build is different than Tpruvot. I have to fix build process specifically to compile his.

I will do so, once I confirm it works well under linux.

Next release will require a few more dependencies to run windows binaries. Instead of trying to explain how to do it all- I am attempting to build an install script for MM.Hash, which will check and install needed binaries.

This means it will be simple as making a Ubuntu minimal installation, and then running two commands- And then its good to go.

I will also leave my overclocking script in next release, so you can change the settings in the script (like MM.Hash.), then run and it will set everything as easily as afterburner.

Please add algo equihash 192.7 (zero)
Mine use optiminer zero, lolminer zero,ewbf new 0.3

I pushed and uploaded 1.3.9 to fix the bugs in 1.3.8 quickly:

-help.txt is inaccurate. I updated correct version on github to match new changes for 1.3.9

-version information on screen: It was updated. It says 1.3.8. It is however 1.3.9- I forgot to change it.

I am working on getting Windows version working to match the same options/features of hiveos version. However, I am trying to also keep up wit user requests on the HiveOS side.

The last known good working versions for Windows were 1.3.6 & 1.3. 7 I recommend using those until you see me mention Windows version is now working.

Just started my first test with MM.Hash (v1.3.9). I get the following error:
"A parameter cannot be found that matches parameter name 'GPU_Count1"
When I remove this parameter from the custom miner configuration, a few parameters seems to be processed ok, but then:
"A parameter cannot be found that matches parameter name Algorithm"

I am still a complete noob regarding mining, HiveOS, everything. ;)

MM.Hash has now migrated into SWARM project:

https://github.com/MaynardMiner/SWARM

Blockmaster_Coin file will fail, due to the fact that their api/currencies are down.

If you would like to mine via coin through blockmasters_coin- please let them know you would like to see their api/currencies working again.

One person telling them is not enough.

If anyone uses miner, and sees a better CCMiner to be used for certain algos- Please let me know. I will add to application immediately.

Miner must be able to be built and compiled, ideally under the ./build.sh command. Not many developers are still supporting linux compiling.

I am getting lots of instability reports, and have noticed increased loads for Cuda 9.2 miners. I have noticed higher loads and stat reporting issues as a result of it on HiveOS version: The system resource use is being kicked up dramatically.

I am going to make an option that will allow users to specify which cuda they want to use.

-Cuda 9.1
-Cuda 9.2

The default will be Cuda 9.2, but if users want to roll back and use Cuda 9.1 they will be able to.

Next miner release over weekend will allow MM.Hash to use any windows-based miner, such as enemy miner, which is windows binary only.

Still reccommend compiling miners using linux build where possible, so it is compiled under latest build, but this means MM.Hash should be able to use any mining program, especially if you know how to change arguments.

I will be including some miners I have already tested.

Full explanation will be in a file labeled Dev Notes when I next commit.