Quote from: rdyoung on September 02, 2015, 01:08:38 AM

Quote from: Cogitorium on September 02, 2015, 12:56:58 AM

Crytsey Responce to me,
[]ny2cafuse 1 point an hour ago
Crypsty is pretty cautious when it comes to wallet updates. They are offline under the premise that the entire network isn't updated, and there is a chance for a fork if enough hashing power was put into a POW wallet version. Fact of the matter is that the devs should have included code that blocked older wallet versions. This would have blocked the POW wallets from connecting to other nodes, and Cryptsy POT wallets would have been online a long time ago.

The devs have hopefully told cryptsy that POW is over, its now POSv, aside from unknown attack vectors, to attack the coin costs BTC to do so.

It doesn't matter if they told them the POW mining is over or not. The wallet code still says that wallets with the protocol version held when we were POW mining are still valid nodes. Thus the network update error... if that is what is causing all this fuss.

However, if anyone really wanted to, they could spin up a bunch of POW wallets via docker and CoreOS, throw some MH at it and create running forks that would disrupt the chain. In fact, they wouldn't even need to mine on this separate network. They would just need enough nodes running so that when a POSv wallet tries to confirm a block, the POW wallet nodes invalidate the blocks.

This isn't rocket science. The devs should have addressed this as a possible security concern. It's already a concern with the exchanges. Devs - Patch the minimum protocol version pull request that I posted to the potcoin github and move on.

-Fuse