Re: [ANN][FLAP] FlappyCoin ★ 0 PREMINED ★ COPYRIGHTED ★ MANY GIVEAWAYS ★ V1.0.0.2

Quote from: ghur on February 24, 2014, 07:08:53 AM

Quote from: hash.so on February 23, 2014, 08:48:45 PM

It's a great pool, that's why it's always has a ton of the network

I'm not sure why you say it's well above 51%, talking about forking or double spend attacks is not relevant for scrypt. We have ~4GH/s on hash.so, so "we" have >51% of flap for quite some time.

The only valid concern is DDoS attacks, and flap network loosing tons of hashing power but with KGW even it is not an issue, coin would retarget itself quickly.

More info in here: http://www.reddit.com/r/flappycoin/comments/1yihen/seems_this_pool_httpsflaphashsoindexphp_is/cfkvxhp

I guess I need to write this up somewhere, because it keeps happening quite often, I can't complain tho, it means that my pools are great

I'm not sure why you're posting this, because non of that is true.

51% attacks work just as well on scrypt coins as they do on bitcoin. There's no particular difference between these coins that makes 51% less of a risk.
51% should be actively avoided.

Your assertion about KGW is incorrect as well. KGW actually makes a DDoS attack more powerful and more effective.
An attacker could massively drop the difficulty almost instantly by attacking the largest pool.
Due to KGW adjusting difficulty so fast, the attacker would see a very large increase in coins mined per khash.

On coins that retarget much slower (hours/days), a DDoS attack will only reduce the competition in finding blocks, but not directly reducing difficulty (as it would take a longer time for difficulty to adjust).
This would make such an attack not as effective as it would be against a KGW coin.

I only meant it doesn't matter if I have 51% of the flappy network, I could easily use our other pools to launch a 51% attack against flappy (we have 5GH/s of scrypt), hell I could launch a 51% attack against any coin that has less than 5GH/s of network. I know it works just a well for scrypt coins as SHA256, but because most scrypt coins are smaller than the larger pools it doesn't really matter in practice.

My assertion about KGW was only about the network health, blocks would still be generated at a steady pace.

As for closing signups, that's not going to work, all of my users are shared in the pool and everyone can switch coins with just a click of a button.