When you write code, you have to compile it. Here is an easily readable if statement in C:
If ( trump_count > biden_count)
{
trump_count --;
biden_count++;
}
That says if trump has more than biden, then subtract 1 from Trump and add 1 to Biden.
That is an oversimplified example but there would have to be something along those lines in the Smartmatic/Dominion code. So we should be able to get that off of the machines right? Wrong. Machines don't read code like that. That kind of code is compiled so that when it gets on the machine it is all just 1's and 0's and the program called the compiler creates that code and it is generally unreadable.
https://files.catbox.moe/ahpcx1.png
If we knew what the compiler they used was then we could decompile the code and have our smoking gun right there in the code. However, I think they thought that through and created their own compiler so that if the code and compiler are subpoenad, they can hand over a compiler that was designed in a way to obfuscate the offending code.
If you think writing your own compiler is hard, guess again. You just need to know how the CPU works and how storage and memory are addressed. Even that crazy bastard that wrote TempleOS wrote his own compiler.
I cannot believe we aren't dissecting the code forensically, and if someone is, that would be the absolute best way to prove this, beyond statistical analysis, eyewitness testimony, etc.
Happy Thanksgiving.
view the rest of the comments →
[–] 26556987? ago
there are excellent open source compiler frameworks like the excellent llvm/clang stack which, for instance, Apple bases its language compilers off of
so one could get a great deal of leverage by just starting with such an existing compiler and the going to the code generation module (a distinct module in llvm) and work on that to obfuscate - even the higher degrees of optimization alone can tend to make the actual machine instruction sequence rather non-obvious relative to the original source code, but with actual intent, a higher degree of obfuscation could be acheived.
Or one could transform ordinary binary instruction code into an encrypted form that has to be decrypted before it can execute on the target CPU. The decryption could be built into a custom page loader - the decryption key could be provided at program execution time and the key might be kept on something like a removable usb stick or smart card