OK Now on topic.

We are seeing the shear power of asic to destroy a coin and are trying to defend with our own asic's and failing. I think we can all agree to that statement. So the reason that we have not changed Algo's is to stop a hard fork, well guess what we got one anyway. And it will keep happening until the main issue is addressed. The only way to protect this coin is to change algo's and to continue to do so every time a asic is made for the one we are running. Unless this merge mining is going to actually happen. And for the Asic's already defending the coin they can be used to shore the price.

Now since any coin that is profitable will eventually have an asic created for it we need to look at the economics and decide logically how to progress to protect from this inevitability. If we goto a algo like X13 (looks like X11 is already fpga) then we can see how quickly that road will fail (just bye looking at x-11) So the only other real choice is an "N" factor I think (correct me if I am wrong). But we do not have to choose any specific "N" factor that is already implemented. We should look at getting our own mix of algo's. Scrypt-Jane is a great example to look at when deciding what way to proceed.

I have not or do I intend to do any in depth analysis of algo's as I have stated previously as The time investment just is not worth the effort for me. But there are those here who are capable and have the investment that this would make this a valid endeavor for their time.