Quote:

This is all what the-best-available-decompiler was able to do with our obfuscated code

Another Quote:

Performance-wise, we can do A LOT of obfuscation per network tick

Quote:

However, we can (and SHOULD) do MUCH better than that

Another Quote:

With our approach, each and every obfuscation has to be hacked individually..

Quote:

Technically, what we’re looking for here, is any kind of bijection; we’ll use this bijection to convert our data from one representation into another one (and as it is a bijection, we can revert it later).

Another Quote:

As we’re not writing our obf<> classes manually (instead, we have a code generator doing it for us on each build), the sky is the limit to the obfuscations we can generate."<> classes manually (instead, we have a code generator doing it for us on each build), the sky is the limit to the obfuscations we can generate.

Quote:

Bingo! We’ve got an executable, which automagically performs TONS of integrity checks, which checks are spread all over the executable, and are extremely non-obvious too.

Another Quote:

This approach of 'not revealing code until attack costs are high' is certainly not limited to payments.