Thanks for the reply! The quality of the discussion is getting better!
Agreed, Inflation is a non-sequitor to this discussion.
Right, it doesn't matter as long as we compare all systems as if they were not using inflation to pay for security. Bitcoin POW does have huge inflation atm to pay miners / pay for security.
What I am proposing is allowing full nodes to automatically become "delegates" if they are on a unique IP and have a minimum stake of lets say 0.1BTC
Interesting! But then you would have the problem of actually nothing at stake (an attacker would just have to create millions of full nodes) plus own stake. In the end you have NXT like POS with the additional requirement to create a ton of full nodes to attack the network. It could be said that an attacker might be better at creating full nodes at scale than the average stakeholder which would make the system more easy to attack.
An attack with DPoS would simply involve flooding the market with many potential delegates
An attacker would have to trick stakeholder into thinking that his delegates are good delegates. The DPOS implementation of BTSX is in its early days. Today almost all delegates are some reputable forum members. Later the idea is that big companies or trustworthy public individuals from the crypto (currency) world would provide delegates: Exchanges, payment processors, DAC developement companies, trustworthy stakeholders; basically everyone that has an interest in a working BTSX system provides a delegate. Those entities then would have a lot more to loose (credibility of an exchange for example) than they could gain from a 51% attack which might be reversed anyway by a fork.
Regarding your attack: Stakeholders would have to be convinced that the random flood of delegates the attack set up are more trustworthy then the current delegates. That might work with 1 or even a few but not with 52.
Now if that happens there could be a fork that reverses the double spent / reversed transactions. Like you said correctly this might harm others who made transactions between the point in time when the double spend happened and when transactions are halted to fork. Those ppl could be compensated through a fund. The advantage would be that the incentive for a double spend attack would decrease to zero when the attacker knows that there is such a fund and a fork would reverse his double spend anyway. How could such a fund be funded (work only work if BTSX grows and tx volume picks up; but gives you an idea what delegates could be good for apart from tx processing): Buy a delegate or several delegates who commit to paying parts of their delegate pay into such a fund. Those delegates then campaign among Stakeholders with this fund.
Forking is possible with any open source coin
As for forking to protect a network in general: Let's assume someone has acquired 51% of all hashing power for Bitcoin's sha256 mining then Bitcoin would have to find and implement a new proof of work algorithm in order to fork and get rid of the 51% control of a single party.
When someone has acquired 51% of stake in a POS coin you can simply fork and not honor this 51% and let the market decide which network is considered more trustworthy (probably the one without the 51% control....).
Please explain to me how this attack could be mitigated without decloaking the identity of all the potential delegates and thus bringing into the conversation a whole new can of worms.
See above. And I would also say that a mix of anonymous and publicly known delegates would be most resilient.
Overall I do not propose that DPOS / POS has no disadvantages. I am pretty certain though that the security per cost you achieve with POS/DPOS is a lot higher than with POW. In the end security and decentralization costs and someone (coin holders or users) has to pay those costs.