BitShares Forum

Main => General Discussion => Topic started by: sparkles on November 26, 2014, 09:14:11 pm

Title: [ANN][SPK] Sparkle - BitcoinTalk Announcement Thread
Post by: sparkles on November 26, 2014, 09:14:11 pm
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.
Title: Re: [ANN][SPK] Sparkle - BitcoinTalk Announcement Thread
Post by: matt608 on November 26, 2014, 09:56:58 pm
Glad to hear your dropping on BTS! :)  +5%
Title: Re: [ANN][SPK] Sparkle - BitcoinTalk Announcement Thread
Post by: CLains on November 26, 2014, 11:39:13 pm
Great work Sparkles. +5%
Title: Re: [ANN][SPK] Sparkle - BitcoinTalk Announcement Thread
Post by: cass on November 27, 2014, 01:56:59 am
 +5%
Title: Re: [ANN][SPK] Sparkle - BitcoinTalk Announcement Thread
Post by: 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? 
Title: Re: [ANN][SPK] Sparkle - BitcoinTalk Announcement Thread
Post by: sparkles on November 27, 2014, 10:17:39 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.
Title: Re: [ANN][SPK] Sparkle - BitcoinTalk Announcement Thread
Post by: 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?
Title: Re: [ANN][SPK] Sparkle - BitcoinTalk Announcement Thread
Post by: iHashFury on November 28, 2014, 11:34:52 am
Looking forward to this experiment  ;)

Where is the official sparkle announcement thread on bitsharestalk? (getting fed-up reading all the FUD)
Title: Re: [ANN][SPK] Sparkle - BitcoinTalk Announcement Thread
Post by: yvg1900 on November 29, 2014, 12:28:46 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