Changing the hashing algorithm
-
I’ll start on the p2pool modifications today.
-
I’d relly like to knwo how you “make” a miner… or a p2pool.
Respect guys! You’re doing all this in two? three people?
You rock!
-
The glory goes to Bushstar and Ghostlander.
I don’t do veery much here, as my programming experience in the crypto area is not that much.
I can modify exsiting code a bit, that’s all. ;)
-
Hi , I like cgminer ,who can build it ?
-
I like my sgminer, but I think Iam not smart enough to modify it :/
-
Also, the thought crossed my mind, what we could do for those mining with Nvidia GPUs?
Anybody able to modify cudaminer?
-
Having support for all the camps from the off will make for a stronger launch.
-
I’m hoping we can deal with cudaminer (or sponsor/commission the guys who wrote it to implement neoscrypt?) Again I would be happy to chip in as I am one of the many who would benefit from nvidia support!
-
I’m curios as to how Neo would work out on nVidia… x11 seems to have an advantage with em, could this be the case here?
-
NeoScrypt P2Pool module is ready. P2Pool works on a fake testnet using CPUminer.
-
So, ghostlander… now we need to modify the scrypt module in cg/sg-miner.
I’ve been watching/messing out with the sph-sgminer for Darkcoin as I wanted to modify the algo (I’ll do wathever if it can distract me from my thesis! ;) ). For what I see, it’s enough to exactly “replicate” the algo from the hashing.cpp (in the wallet) to the algo.c file in the root directory. But I may be off-track… Do you think that’s the right path?
I mean, some optimization should be done (I don’t know where to start) but having a working GPU miner (albeit a non-opt one) from day one looks like a very good start, don’t you think?
So, the big question is: who is doing this? Is the algo accessible or is it still in a top secret state?
-
Suffered a setback . :(
I’m compiling cgminer on win32(x86) . My IDE is Visual Studio 2013 . After I add neoscrypt.cpp and neoscrypt.h to the cgminer.vcxproj, then compily it .
But I get a lot of errors:
ROTL32, Identifier not found
SCRYPT_BLOCK_SIZE ,Undeclared identifier
stack, Unknown size
-
This is because NeoScrypt is supposed to be compiled by a C compiler, not a C++ one. The work-around is in a PM.
-
Great work on the algo change. Looks like it might be worth haveing a p2pool test site, with all miner updates needed.
-
I believe it’s of very great importance that we don’t forget the nvidia cards out there, we want to be open and welcoming to all miners as fast as possible after release :)
-
most of my GPUs have blown up in the last 2 months.
-
One thing I have noticed running feathercoind and other coin daemons on a p2pool with tight memory. The 0.6 series daemon takes 190 MB compared to the 0.8 which are more like 230 MB. (can vary higher)
Both of which seems higher than they need…
That won’t be directly related to the algorythm, but the pool daemon pass round the work, so its something that might be “optimisation” In the builds.
Whilst we’re considering testing / improving performance.
-
I had a mail chat with one of the authors of cudaminer.
He is interested to add neoscrypt to cudaminer, but he can’t make it happen soon. -
One thing I have noticed running feathercoind and other coin daemons on a p2pool with tight memory. The 0.6 series daemon takes 190 MB compared to the 0.8 which are more like 230 MB. (can vary higher)
Block index is held in memory. More blocks in main chain = more memory consumed.
-
I had a mail chat with one of the authors of cudaminer.
He is interested to add neoscrypt to cudaminer, but he can’t make it happen soon.Is there someone official behind the ccminer? That’s also a viable option for nvidia and perhaps he/she/they have more time to add NS? :)
