In this sense, the models are not significantly different: they both try to solve a situation as best possible. You are arguing for one rather than the other, which is fine. The OP not picking your favorite is not necessarily a crime: the model he did pick has significant advantages (it is legally sound, for one; it allows the users themselves to choose whether they want to be slaughtered or not, as opposed to just "Oops, you hadn't stamped a card on Aug 17th? Ah well, poopy for you" for another).
I would agree entirely if there were no chain of ownership information whatsoever. Since there is a list that apparently has at least
some valid information, it could be argued as irresponsible and to the detriment of shareholders if it weren't used fully.
The problem, however, is that whether you accept it or not is irrelevant. You're not the standard to measure this by. I'm not either, nor is anyone else (or even, "everyone else", as in, all the F in corpus).
A good representation of the kernel of the problem is right here: we used to have a measuring stick. It burned. Now we have no measuring stick.
Correct, but we do have different classes as you've pointed out. There is no one-size-fits-all answer, and treating all of them the same is a disservice. Due to the circumstances, both solutions would be necessary to afford the best chance for as many shareholders to be accommodated as possible. If giga wants to enforce the current solution afterward, at least there will be an option of parting ways.
As far as giga's situation, I can understand the difficulty. At the same time, there is the ability to handle claims on a case-by-case basis without resorting to disclosure of private information for all owners. Some additional work now can speed the transition to a single solution. For example: if a shareholder has assets with multiple issuers, the information can be cross-referenced by issuers with the shareholder's permission. This still relies upon nefario's list being valid, but it reduces the chance of independent fraud from the client side.
