Topic: hsrminer - Nvidia mining software for various algos by palgin&alexkap (Read 30789 times)

REMOVED UNTIL RECONSTRUCTION

last ccminer klaust is very good

What is best miner for Neoscrypt at this moment ?

Where can I download this miner from? Could you please provide me a download link?

API works on a fixed port 4001

Well, it's surely been said a million times already, but:

PLEASE add an API!

Hello,

My miner works for 1-2 even 10 or more hours, but constantly crashes with the below error:

Cuda error in func 'neoscrypt_cpu_hash_1060' at line 1408 : the launch timed out and was terminated.
Cuda error in func 'neoscrypt_cpu_hash_1060' at line 1408 : the launch timed out and was terminated.
 INFO : [10:45:30] : Connection interrupted
 INFO : [10:45:30] : Share difficulty reset -- 64 (0.00098)
 INFO : [10:46:20] : New block #65039 received, new difficulty is 1230.424
 INFO : [10:46:47] : New block #65040 received, new difficulty is 1229.887
 INFO : [10:46:53] : New block #65041 received, new difficulty is 1234.741
 INFO : [10:47:26] : New block #65042 received, new difficulty is 1317.929
 INFO : [11:04:09] : Connection interrupted
 INFO : [11:04:10] : Share difficulty reset -- 32 (0.00049)
 INFO : [11:08:22] : New block #65043 received, new difficulty is 981.775
 INFO : [11:08:34] : New block #65044 received, new difficulty is 977.713
 INFO : [11:08:41] : New block #65045 received, new difficulty is 1058.435
 INFO : [11:10:32] : New block #65046 received, new difficulty is 1051.208
 INFO : [11:12:31] : New block #65047 received, new difficulty is 1038.114
 INFO : [11:13:36] : New block #65048 received, new difficulty is 1148.740
 INFO : [11:13:40] : New block #65049 received, new difficulty is 1154.018
 INFO : [11:14:33] : New block #65050 received, new difficulty is 1209.880
 INFO : [11:14:47] : New block #65051 received, new difficulty is 1269.202
 INFO : [11:15:06] : New block #65052 received, new difficulty is 1270.820
 INFO : [11:15:10] : New block #65053 received, new difficulty is 1291.227
 INFO : [11:15:43] : New block #65054 received, new difficulty is 1298.237
 INFO : [11:15:48] : New block #65055 received, new difficulty is 1312.554
 INFO : [11:18:04] : New block #65056 received, new difficulty is 1290.903
 INFO : [11:18:06] : New block #65057 received, new difficulty is 1312.083
 INFO : [11:21:59] : New block #65058 received, new difficulty is 1272.708
 INFO : [11:22:28] : New block #65059 received, new difficulty is 1641.071
 INFO : [11:22:49] : Connection interrupted

Any clues on why this is happening?

PS: I have 2 rigs with the same settings, mining the same thing, on the same pool, and only one is crashing. The other one works perfectly.

Dear sir, my first and last message directed to you personally.

Don't waste your time reading or answering this, you'll be in my ignore list for quite a long time when your opus'll finally be born.

First of all, as I always mention, You came to my thread, not Me to yours, as you can see I've posted nothing at that garbage hole and never tried to stop your little reverse-engineering project.
It's only you splashing your saliva here, GTFO and make your life not so miserable.

Now containment:


1) I'm not accusing anyone, I've just posted two ways of thinking on the same problem, nothing more. And container is a shit when it comes to mining, doesn't matter how good it is, it will cost nothing without proper kernel. Which you can't say about kernel, give it input, you'll receive output, volia, solution, check it against target, volia, proper solution, not so much code, isn't it?

2) The lie is that you do it for community, you do it only because I've hurted your oversized Ego, and don't think you've hidden your personality under this new account

Are you right about devfee? Partially, man, partially, because dev pool connection is not momental, that value highly differs for every user and that doesn't mean that I gain anything from client connecting to server, only fools think so, for some users full dev time was 38-45 secs, for some it could take more as in your case. Even calculating this, kernel speed gave much more profit for end users, much more, none've pushed Neooscrypt so high before me on Pascal architecture and you're just a parasite in that case, you can write hundreds of reveals and investigations, that will change nothing.
Maybe in your perfect world users follow devs, idea, community, etc., in real world the only thing users follow is money.
In your case users switched for functionality, nothing more, so your crown is made of chocolate, man, be careful, chocolate's melting sometimes.

And let's make it bold!!!! 14528731478% DEVFEE, beware, liar, thief, criminal, freedom, ZOG, HOLD THE DOOR, hold the door, holdthdor, Hotdor, Hodor!!!

3) Destructive code is the one and only thing that can stop your kind from your business, so look carefully when you'll start new freedom-fight campaign against me, or you'll make a lot of trouble to your fanbase and for yourself personally (let's make it a little surprise and see).
Because You'll be a creator of "destructive" binary, not Me, my binary will be as clean as a perfect diamond prism.

And there will be no conclusion to all this shit, it's just some kind of open PM which everyone can read and understand from his/her point of view.

Sayonara, my "friend".

...
First of all, as I always mention, You came to my thread, not Me to yours, as you can see I've posted nothing at that garbage hole and never tried to stop your little reverse-engineering project.
...

Sounds like you guys should collaborate on the miner and split the devfee. Justaminer has spent quite some time figuring out what the end-users want, including API and reliability. I doubt that he had any ill intent by patching it in the beginning based on posts in respective thread. Slapping a devfee on a patched release was questionable, but that was done before Palgin's return.

Palgin's kernel optimization work is amazing. No questions about it.

We all would benefit if you two combine your knowledge and experience and make a great miner to try and beat that excavator which currently has ~10% advantage on 1080/1080Ti.

I don't approve patching someone else's proprietary binary, but when the only dev went AWOL, there was some excuse for it. If I were the original dev in such situation, I would expect an apology from someone who hacked my binary without my knowledge and would be open to suggestions and collaboration. But that's just me.

In any case, try to be respectful and open-minded. The last thing we need right now is a dev war in this space.

With respect,
SCSI