@kukabi Sorry for the misunderstanding, but that is not quite what I meant.
My centralization concern has nothing to do with whether the nodes are running on distributed cloud providers or bare metal. The critical issue I am pointing to is the centralized geoDNS and load balancing infrastructure, which effectively breaks end-to-end (e2e) encryption and opens an attack vector to DDOS attacks. Also the operational risks having a single entity with so much power of the RPC nodes.
If you re-read my initial post about rsETH incident , the threat model I am highlighting is not about direct on-chain exploits or altering finality. The latest and most sophisticated attack vectors in the industry are specifically targeting off-chain infrastructure.
In our ecosystem, an off-chain exploit of this nature could easily be weaponized against platforms like Hydration or vDOT. Even if the original DOT base layer isn’t directly compromised in such an event, a massive off-chain exploit within the ecosystem would still have catastrophic implications for Polkadot’s overall reputation and user trust. I can strongly advise to study the rsETH / KelpDAO incident. In the chain of mistakes was a harmless governess change to increase LTV of rsETH to 90%.