Quote from: xeroc on November 28, 2014, 08:30:56 AM
Is there are reason you chose a non-asic-resistant algorithm like SHA* .. and not went for the PTS algo which seems to be pretty asic resistant?

Yep, same question here: selection of SHA512 will leave huge part of CPU miners (individuals that may benefit most from DPOS) out of the game nearly immediately.

I really suggest to reconsider PoW algo to something more centralization-resistant like MMCv2.

Follow @yvg1900 on Twitter to get updates on performance mining software

Looking forward to this experiment  ;)

Where is the official sparkle announcement thread on bitsharestalk? (getting fed-up reading all the FUD)

Is there are reason you chose a non-asic-resistant algorithm like SHA* .. and not went for the PTS algo which seems to be pretty asic resistant?

Quote from: Bitcoinfan on November 27, 2014, 08:08:08 PM
Hi Sparkles,

Can Sha 512 be merged mined with Bitcoin?  Have you put much thought into preventing a 51% attack early on in the experiment?

No it cannot.

Hi Sparkles,

Can Sha 512 be merged mined with Bitcoin?  Have you put much thought into preventing a 51% attack early on in the experiment? 

 +5%

Great work Sparkles. +5%

Glad to hear your dropping on BTS! :)  +5%

https://bitcointalk.org/index.php?topic=874406.new#new

Give it some love and show your support as BTS holders benefit from any publicity produced by Sparkle and have a stake in the system.