Miner software for various hashing algorithms (currenlty Nvidia-only) by palgin & alexkap
palgin - CUDA-related stuff
alexkap - C++/C-related stuff
Cards with CC 5.0+ only.
Nvidia driver 388.3x+ only.
Current testing speeds(HSR):
1060 3Gb - 8.3+ Mh/s
1080 - 16.2+ Mh/s
Current testing speeds(Neoscrypt):
1060 3Gb - 740+ kh/s (non-OC)
1080 - 1280-1300 kh/s (non-OC)
1080Ti - 1850+ kh/s (users reported speed)
Product contains devfee 1% (0.5% for me, 0.5% for alexkap) and is close-sourced, but voluntary work won't be abandoned.
Will be distributed (at least on the first stage) as one binary per algo, not so convenient, I understand, but currently it's code-bounded.
I ask everyone who's interested to participate in open beta, because closed beta didn't give us enough information for bugtracking (there are some).
DOWNLOADS:
]hsrminer for HSR algo, Win version , ]hsrminer for Neoscrypt, Win version , Zipped , ]Test version
Neoscrypt note:
All new features, tweaks and fixes are added to "Test version" first.
GTX 1080 (including Ti),1070, 1060 3/6Gb, 100 Ti users should run without any problems without intensity tweaks. Others may need to tweak intensity first.
9xx family and lower not supported in this release.
For everybody using Windows 10: if you don't have Creators Update installed and have problems with hsrminer, just update your rig. Found this out during investigation with user soggyminer
***ATTENTION***
For rigs with multiple Hi-End graphic cards (5x1080, for example), summary of physical RAM installed plus pagefile size should be more than summary of amounts of allocated memory on each GPU.
Example:
I have 6x1080 rig, on each kernel allocates 6260 Mb memory, so sum of RAM + pagefile should be more than 6260*6 = 37560.
Keep that in mind when launching on multi-GPU systems.
*********************************************************************************************************************************************
SAMPLE USAGE: hsrminer -o URL -u USERNAME -p PASSWORD
Plans for future releases:
1) Until palgin (me) covers at least 75-80% of existing algos hsrminer version will stay 1.0.x
2) After algo coverage we'll start migration to smarter (sgminer-like or something like that) interface, will add working API, maybe in-software overclocking options, any suggestions are greatly appreciated. Currently our miner is highly inspired by ccminer and EWBF's work, but we want to find our own way.
3) After frontend update we'll start updating all algos where it'll be possible to new kernel execution scheme in order to optimise hardware bottlenecks.
4) Add new algos (if there will be any at that time)
F.A.Q (will be updated basing on frequent questions in this topic):
Q: Why did you move from free software to devfee?
A: The situation I'm currently in made me to do so, donation scheme didn't work at all, also my employer informed me that he closes his business and doesn't need my services anymore, with all this I have high load on my family budget (need to cover over 80k$/year bills) which I won't be able to cover without extra income. Freelance don't give me much money without stable employer. So yes, it's money question, also I have another dev working on the project who wants to be paid for his work.
Q: Who's alexkap?
A: It's my ex-colleague who worked on the same employer, this summer we just decided to work together in crypto-field.
Q: hsrminer looks quite like ccminer...
A: True, in early builds it really was ~30% ccminer code (especially monitoring), but now only data output is quite the same. Also we'll migrate to new frontend after algo coverage.
Q: What other algos are you planning to add?
A: At the release time we'll try to cover at least 3-4 popular ones, HSR choice was just for a good base for faster implementation of other algos.
Q: Will you provide any support for your miner?
A: Yes, all support will be provided in this topic.
Q: Linux support?
A: Planned, I'll provide Linux binaries once I set up developement machine for *nix.
Thank for everyone viewing this topic and for your participation!
palgin - CUDA-related stuff
alexkap - C++/C-related stuff
Cards with CC 5.0+ only.
Nvidia driver 388.3x+ only.
Current testing speeds(HSR):
1060 3Gb - 8.3+ Mh/s
1080 - 16.2+ Mh/s
Current testing speeds(Neoscrypt):
1060 3Gb - 740+ kh/s (non-OC)
1080 - 1280-1300 kh/s (non-OC)
1080Ti - 1850+ kh/s (users reported speed)
Product contains devfee 1% (0.5% for me, 0.5% for alexkap) and is close-sourced, but voluntary work won't be abandoned.
Will be distributed (at least on the first stage) as one binary per algo, not so convenient, I understand, but currently it's code-bounded.
I ask everyone who's interested to participate in open beta, because closed beta didn't give us enough information for bugtracking (there are some).
DOWNLOADS:
]hsrminer for HSR algo, Win version , ]hsrminer for Neoscrypt, Win version , Zipped , ]Test version
Neoscrypt note:
All new features, tweaks and fixes are added to "Test version" first.
GTX 1080 (including Ti),1070, 1060 3/6Gb, 100 Ti users should run without any problems without intensity tweaks. Others may need to tweak intensity first.
9xx family and lower not supported in this release.
For everybody using Windows 10: if you don't have Creators Update installed and have problems with hsrminer, just update your rig. Found this out during investigation with user soggyminer
***ATTENTION***
For rigs with multiple Hi-End graphic cards (5x1080, for example), summary of physical RAM installed plus pagefile size should be more than summary of amounts of allocated memory on each GPU.
Example:
I have 6x1080 rig, on each kernel allocates 6260 Mb memory, so sum of RAM + pagefile should be more than 6260*6 = 37560.
Keep that in mind when launching on multi-GPU systems.
*********************************************************************************************************************************************
SAMPLE USAGE: hsrminer -o URL -u USERNAME -p PASSWORD
Plans for future releases:
1) Until palgin (me) covers at least 75-80% of existing algos hsrminer version will stay 1.0.x
2) After algo coverage we'll start migration to smarter (sgminer-like or something like that) interface, will add working API, maybe in-software overclocking options, any suggestions are greatly appreciated. Currently our miner is highly inspired by ccminer and EWBF's work, but we want to find our own way.
3) After frontend update we'll start updating all algos where it'll be possible to new kernel execution scheme in order to optimise hardware bottlenecks.
4) Add new algos (if there will be any at that time)
F.A.Q (will be updated basing on frequent questions in this topic):
Q: Why did you move from free software to devfee?
A: The situation I'm currently in made me to do so, donation scheme didn't work at all, also my employer informed me that he closes his business and doesn't need my services anymore, with all this I have high load on my family budget (need to cover over 80k$/year bills) which I won't be able to cover without extra income. Freelance don't give me much money without stable employer. So yes, it's money question, also I have another dev working on the project who wants to be paid for his work.
Q: Who's alexkap?
A: It's my ex-colleague who worked on the same employer, this summer we just decided to work together in crypto-field.
Q: hsrminer looks quite like ccminer...
A: True, in early builds it really was ~30% ccminer code (especially monitoring), but now only data output is quite the same. Also we'll migrate to new frontend after algo coverage.
Q: What other algos are you planning to add?
A: At the release time we'll try to cover at least 3-4 popular ones, HSR choice was just for a good base for faster implementation of other algos.
Q: Will you provide any support for your miner?
A: Yes, all support will be provided in this topic.
Q: Linux support?
A: Planned, I'll provide Linux binaries once I set up developement machine for *nix.
Thank for everyone viewing this topic and for your participation!
Nice miner, but it doen't work on Windows server 2016 datacenter version. Could you test it with some other windows version and make the support of it better with them? The limitation of win10 creator update is somewhat too limited.
