Quote from: bjmillican4 on April 03, 2014, 10:14:16 PM

Quote from: jommy99 on April 03, 2014, 09:09:17 PM

We may need to be looking at this problem, coins with KGW are being attacked!...
Regarding Auroracoin TW exploit (Fix included) https://bitcointalk.org/index.php?topic=552895.0
"The exploit BCX has found in KGW implememtation is real and, I believe, he is most likely attacking with the exploit just now..."

Pandacoin was hit with an attempted attack last night..

Yes, it definitely affects all kgw currencies.

Yep. Actually, the timing for this is good. A fix the KGW needs to be done BEFORE the android wallet is deployed. And Rush is doing maintenance on FUNK. Before we hit other exchanges, I think the timing is good to put a fix in for this.

Other stuff I want to implement. And want your thoughts:

1) Add in the notification/alert system [#1 priority. This is so we can more easily inform users to switch when it is needed]
2) Raise the fees. The fees were never meant to be 0.001 [same as Litecoin]. It's supposed to be higher, closer to the soft dust limit [same as Dogecoin's fees]. Like what happened with doge, if FUNK becomes popular, a spam attack can happen on the network if we don't raise the fees.

If you want to help! https://github.com/The-Cypherfunks/The-Cypherfunks

Anything else? I'm still adverse to changing the hashing algorithm. And I've explained why several times. It comes down to: asic-resistance will always be an uphill battle. Doing mobile development, I'm especially concerned how the hashing verification affects SPV syncing. SPV is supposed to be quick, not the days of syncing a full chain. I have no idea how X11 for example performs for SPV verification. You are doing a lot of expensive verification hashing. Scrypt-N with expensive external memory requirements sounds like a deathknell for mobile SPV wallets. Scrypt is already slower than SHA256 [substantially]. The other factor is simply: development time. Currently I'm spending most of my time doing development on Cypherfunks. Porting native hashing code over to android is just something I don't have time for. There is scrypt native code already. So that solves that.

Also! Dig comkort. Thanks for voting Jommy! I will vote there as well, as well as on mintpal. Let's get the ball rolling, the beats dropping and rhythm flowing.

EDIT: Just to clarify. I'm going to study the TW exploit fully to see if it's needed. It is definitely an exploit, but if its attack vector is too large (like a 51% attack), then we'll reconsider.