I just made a pretty simple point in response to you, and then tried to explain it to b9ron, when he took issue with it.
And I never even came close to saying I only trust code I wrote myself, not sure where you pulled that from.
I inferred you don't trust code you didn't write from this comment:
...
And the only way to change that, is to verify all the code (which as I have also pointed out, does not even suffice entirely, as you are still trusting that the code you see is what was actually running).
You say you don't trust entirely the code that has been leaked/revealed is the same as what is currently running and since the only way to be truly sure of that - without having to trust anyone else - is to have written the code yourself.
I never said that -- nowhere have I suggested that the leaked code is not what is currently running on the network. It does not even make sense to suggest so, given that my point was first made before the leak had even occurred.
You wrote that you had been pushing for source release "for the version of Atlantis which has been out for ~1 month", and I responded by saying it would be a problem if the commit history going back to the last public derosuite commit were not included, and that even if it was, it would still be problematic, given that git is not immutable. Please read again the hypothetical I gave using monero, to better understand my point; we are not concerned here with any code prior to dero's going closed-source, nor with the code in the leak, but rather the fact that there is no way to know what has been running on the network in the interim.