As litecoinpool gets near 51% of the network, it begs to question whether or not something could be added to the protocol to protect from the possibility of a 51% attack. For example what if when one party start to get near 51% the protocol automatically "freezes" former blocks to prevent any 'rewriting' of past transactions. By doing this automatically it might give us some piece of mind.
I think the problem is that there's no way to tell if two blocks come from the same entity. We know the hashing power of pools just because pools make their numbers public.
Maybe someone will come and prove me wrong, but I don't think there's any sensible way to completely avoid the possibility of a 51% attack without giving up decentralization.
The good news, let me state this once again, is that even if one single entity has 51% of the hashing power it doesn't mean that this entity is going to use it to attack the chain.
On the other hand, it would be preferable if miners who want to mine in a pool took advantage of the many Litecoin pools
that are available, instead of concentrating in one single pool.