Changing the hashing algorithm
-
Beta 1 is ready.
Two days later on Cryptsy…
As I see it, the announcement was enough to shake the market!
(sorry for the big pic don’t know how to resize the with the bbcode of the forum)
-
Two days later on Cryptsy…
As I see it, the announcement was enough to shake the market!
(sorry for the big pic don’t know how to resize the with the bbcode of the forum)
Yup, lizhi reads the forums so he bought another mil. ;D
-
LOL ;D other people’s doubts benefit me
-
Two days later on Cryptsy…
As I see it, the announcement was enough to shake the market!
(sorry for the big pic don’t know how to resize the with the bbcode of the forum)
So why didn’t it shook the PXC price ??
-
Just reading this: re: Potential flexibility of Scrypt ASICs to modification
,https://bitcointalk.org/index.php?topic=494625.0
it seems the GridSeed GC3355 - (Scrypt) ASIC has GNU/Linux onboard, so is programmable anything but the SHA256 hashing algorithm will soon be ASIC mixable, able by adjusting the software… + you could probably even add other op systems.
1 - Start the controller in failsafe mode:
2 - Telnet into the device:
3 - Switch to the live partition:
4 - Change the root password:
5 - Enable SSH:
6 - Reboot the device:
-
Just reading this: re: Potential flexibility of Scrypt ASICs to modification
,https://bitcointalk.org/index.php?topic=494625.0
it seems the GridSeed GC3355 - (Scrypt) ASIC has GNU/Linux onboard, so is programmable anything but the SHA256 hashing algorithm will soon be ASIC mixable, able by adjusting the software… + you could probably even add other op systems.
1 - Start the controller in failsafe mode:
2 - Telnet into the device:
3 - Switch to the live partition:
4 - Change the root password:
5 - Enable SSH:
6 - Reboot the device:
Sooner or later, someone will code the other algorithms to run on them, hence why most only claim to be “asic resistant”
Nice article though, bookmarked, will have a read proper later :)
-
Beta 2 is ready. All reference code is in place. 64-bit assembly code is also there, though it works well for the Intel CPUs only. The AMD CPUs are better with the reference code, though I have tested the K8 and K10 generations only. Working on the environment now.
-
Beta 2 is ready. All reference code is in place. 64-bit assembly code is also there, though it works well for the Intel CPUs only. The AMD CPUs are better with the reference code, though I have tested the K8 and K10 generations only. Working on the environment now.
Can you create a p2p test pool ? We can test together. In addition, we need a new mining software.
-
Ghost let me know if/when you want to test on GPUs, I don’t have any problems pointing my 30+ GPUs at a test coin so long as you have a linux build.
-
Can you create a p2p test pool ? We can test together. In addition, we need a new mining software.
P2pool test pool should be no problem ;)
for the mining software, it’s probably ‘just’ a modification of an existing miner, e.g. cgminer or bfgminer for linux.
-
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.
-
Probably I’ll be avaliable for MPOS in one week from now. After that I can jump into p2pool if no one else is interested :)
-
Beta 2 is ready. All reference code is in place. 64-bit assembly code is also there, though it works well for the Intel CPUs only. The AMD CPUs are better with the reference code, though I have tested the K8 and K10 generations only. Working on the environment now.
Thanks for updating us about the process!
-
Could try to adapt and setup p2pool, but not sure how to test it without a working miner.
If the block prefixes don’t change, not much to do here, I think.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.
-
Is it very difficult to have merged mining of all Neoscrypt coins (similar to Blake 256 system)?
Just a tought…
-
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 ;)
-
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! ;)
-
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.
-
Great news thanks for all your hard work on this. I think some tips are in order!
-
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.
