The "blake" algo is only for SFR and NEOS (its the real blake256 algo), blakecoin changed it to speed up the hashrate
The original submission of Blake-256 was 10 rounds but in the final they increased the rounds to 14 to try and gain more support from the judges but in the end NIST wanted the sponge function to get total immunity from length extension attacks rather than just resistance like all the other algo's in the final of the SHA-3 competition
Blake is based on ChaCha which is often used in an 8 round configuration hence why I chose to use that over the other extra security margin versions as that is all the extra rounds do!
Here is the proof that 8 round Blake-256 has a minimum security margin of 2200 for best attack by a world leading expert academic team in cryptography
http://eprint.iacr.org/2013/852.pdf
for brute force attack there is still no better than 2256 and as the process of mining is like a partial preimage attack seems pointless to waste time, resources and efficient using the final submission 14 round version as it did not help win over the NIST judges
all variants are real due to a feature of the Blake algo "simple speed/confidence trade-off with the tunable number of rounds"
reducing the rounds also makes the algo smaller in hardware for FPGA so you can build higher Fmax bitstreams and would also make an Asic smaller thus cheaper, faster, and use less watt/hash for same nanometer process
*also note that the rounds in Blake2 are also reduced "from 14 to 10 for BLAKE2s (successor of BLAKE-256)"
Thanks for porting the Blakecoin version
hmm ? on which pool ?
I also own a R9 285 but i dont plan to use opencl in this project.
