I experienced a worrying issue today which is important for a possible future bytecode verification in aeScan which I wanted to double check before deploying my contract on mainnet.
for whatever reason, the exact same script running against the exact same http compiler with api-version v7.5.0 and compiler version v7.3.0 produces different bytecodes.
the expectation is of course that the produced bytecode does NOT differ.
this affect only applies if the http compiler is restarted! (if I run the script multiple times on the same http compiler instance, the bytecode is the same)
I experienced a worrying issue today which is important for a possible future bytecode verification in aeScan which I wanted to double check before deploying my contract on mainnet.
for whatever reason, the exact same script running against the exact same http compiler with api-version
v7.5.0
and compiler versionv7.3.0
produces different bytecodes.the expectation is of course that the produced bytecode does NOT differ.
I was running the following script:
3 example bytecodes:
one (currently committed)
two
three