> There are many reasons to use subsidiaries for things like this, like to invite outside investment, ringfence risk, cede operational risk, and many more.
Agreed, there are many valid reasons to have subsidiaries of course.
The issue is rather with the fact that we are having the assumption that the threat is outside rather than inside and so systems with mechanisms to be less transparent are far more prone to this risk.
It has been academically shown that most corporate/ white paper scams aren't done from outside but rather from inside the company itself through genuine structures and incentives which go wild. (Something shockingly visible in AI space), Enron's example also comes to my mind.
The best way I can explain it to the programming crowd is this: Imagine how ridiculous it would sound if you are ranked with how many lines of code you ship and how much token you would spend and so we end up with tokenmaxxing and hearing stories about people literally burning tokens in innovative ways because they want to get on top of a leaderboard. Oh wait, it is already happening or has happened.
Generally speaking, It is preferable to be transparent with debt and other things rather than not especially so for long term because sooner rather than later you might get caught. Obviously if there is some stuff which prefers from ringfencing risk then sure.
Also as I spoke of Enron, but the exact structure was used by Enron as well as @fzeroracer discusses in their comment[0] so it might be a genuine question.