Quote from: tacotime on May 08, 2013, 08:08:26 PM

Quote from: megablue on May 08, 2013, 07:37:52 PM

Quote from: tacotime on May 08, 2013, 07:26:48 PM

Quote from: rbdrbd on May 08, 2013, 07:25:59 PM

Quote from: Hydroponica on May 08, 2013, 07:06:49 PM

So, instead of getting raped by GPU farms, we are now getting raped by multi-CPU server farms Huh

No, just the CPUs on GPU farms.

Probably you're getting raped by GPU farms, too. You don't need to change the kernel from cgminer or reaper all that much to GPU mine this coin right now, and at the current value of N I would wager that most GPUs get 1000+ KH/s.

Wrong... it isn't using standard scrypt algo... you can mine with gpu but non of your shares will be accepted by the network.

I'm aware it's running block header hashes with keccak and chacha20 -- but all you need to do is port them to GPU kernel that comes with cgminer/reaper.
https://github.com/ckolivas/cgminer/blob/master/scrypt130302.cl

The keccak/chacha20 implementation he took from scrypt-jane is here
https://github.com/floodyberry/scrypt-jane/blob/master/code/scrypt-jane-hash_keccak.h
https://github.com/floodyberry/scrypt-jane/blob/master/code/scrypt-jane-mix_chacha.h

Edit: You need to play with the lookup_gap and thread_concurrency to get the best performance, too.

I also believe the OP may be a bit BIP incompliant.

I do not see an RPC command or a Field in getwork - getworkex or getblocktemplate that gives the current Nfactor.

I may be wrong and missed it, but withholding vital mining information from RPC is ,shall we say "dirty pool" Wink