Looks like it was the CTOs commit. That's not to say that he didn't pull changes from elsewhere. I'm leaning more and more toward the "Retirement Attack" the more that comes out. Honestly the lawsuit is gonna be lit. We're probably gonna learn a lot.

![](https://m.stacker.news/150810)

![](https://m.stacker.news/150811)

That seems more plausible to me but I don’t have a strong feeling about how plausible it is. 

Another possibility is that it was initially a genuine mistake that someone later saw the opportunity to exploit.

Still pretty sophisticated to bury it so, being able to pull that off and not know how damned near impossible it will be to cash out seems unlikely... but if it was an off-shore wagie maybe they're content to drip small amounts and aren't bearing the cost of the legal/business destruction.

justin_shocknet

My reading of this question is not that there would have been a decision from the top, but rather someone who worked on the code wrote it this way so they could exploit it if need be.