Changing the hashing algorithm
-
Brilliant News.
-
ghostlander is my hero of the day. huzzah!
-
Wow, ghostlander! Thank you!
Cant wait to see what you ended up with!!
-
Beta 1 is ready.
-
Beta 1 is ready.
!
-
Beta 1 is ready.
Awesome!
-
Very cool, good work Ghostlander.
-
eagerly awaiting to test
-
Nice job!
Cant wait to see what you created!
-
Can we help Beta-testing with p2pool server and/or client ?
-
We have to build a new miner I suppose…
-
I think all we have to do is modify a pre-existing one. It’s half the point of upgrading Scrypt as opposed to making an algo from scratch, I think.
-
We only have the reference code which is pure C and not final yet, though compatible backward with Scrypt for a smooth transition. No assembly optimisations at this moment, therefore no miner other than built in the wallet. In order to run a P2Pool, we need to make a Python module. Step by step.
-
Step by step. :) hand by hand
-
In order to run a P2Pool, we need to make a Python module. Step by step.
So would that be the next step in the process of shifting algo’s?
-
My opinion: build the pool module for neoscrypt and then build modules for cgminer and bfgminer, if it’s not posible to do all this in parallel.
Then test the new versions on the testnet, as we did for the last hard fork.
If we are really really sure, that everything works as expected make the fork on the prod net.
-
+1
-
So would that be the next step in the process of shifting algo’s?
The next step is Beta 2 with the near final C code and SSE2 assembly optimisations where necessary. AVX may improve the performance a bit more, but it isn’t of a key importance.
-
Very glad to hear any news from you
-
Slow down, I haven’t had time to unleash my new ASIC on FTC yet! ;)
