Changing the hashing algorithm

mirrax

Is it very difficult to have merged mining of all Neoscrypt coins (similar to Blake 256 system)?

Just a tought…

voingiappone

Eventually can help with cgminer, but I’m not an experienced c/c++ programmer. So if you could share the code I can give it a try at least.

Same here!

I can offer my (very) limited c++ knowledge but you’ll have to explain me what to do ;)

vizay

If any of you wants to help with either Python code for P2Pool or PHP code for MPOS or OpenCL kernel for [cg,sg,bfg]miner, I have no problem of sharing the reference code with you. I’m going to finish CPUminer first.

P.S. My notebook has blown up yesterday due to summer heat. Shouldn’t have purchased Alienware, lesson learnt.

I can at least take a look at the python stuff (not promising that I can help since I don’t know what level of programming is required before I’ve looked at the code) and see if I can help out. Just finished version 1.1 of our chargeback system at work written in python so I need a new project to set my teeth in! ;)

ghostlander

I’ve completed CPUminer nearly. The only issue left is endian conversion: all Bitcoin derivatives are little endian inside, so NeoScrypt is also little endian completely. SHA-256d and Scrypt are big endian ones due to SHA-256 being employed by both. CPUminer is also big endian inside.

The P2Pool module seems to be a simple wrapper over the reference code, so this is an easy part.

kris_davison

Great news thanks for all your hard work on this. I think some tips are in order!

ghostlander

CPUminer works now in both native (NeoScrypt) and legacy (Scrypt) modes. Not parallelised much yet, so the performance is the same to the internal wallet miner. NeoScrypt and Scrypt should deliver very comparable CPU performance, maybe NeoScrypt a little bit better.

kris_davison

That’s great glad to hear the initial results are showing a performance improvement with neoscrypt.

Wellenreiter

I’ll start on the p2pool modifications today.

voingiappone

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!

Wellenreiter

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. ;)

lizhi

Hi , I like cgminer ,who can build it ?

ChekaZ

I like my sgminer, but I think Iam not smart enough to modify it :/

Wellenreiter

Also, the thought crossed my mind, what we could do for those mining with Nvidia GPUs?

Anybody able to modify cudaminer?

MrWyrm

Having support for all the camps from the off will make for a stronger launch.

kris_davison

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?

ghostlander

NeoScrypt P2Pool module is ready. P2Pool works on a fake testnet using CPUminer.

voingiappone

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?

lizhi

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

ghostlander

This is because NeoScrypt is supposed to be compiled by a C compiler, not a C++ one. The work-around is in a PM.