I have a smart contract that outputs a different bytecode when compiled with truffle, and with remix, even though both seem to use the same compiler version: 0.5.7+commit.6da8b019 Is that a known issue ? Is that normal ?
This causes issues to verify my smart contract on etherscan, and thus to be trusted by my users, which is kind of a big deal.
Thanks for your help.
Alright, I've found the answer after digging a little bit more into remix's compilation option. It seems that right now, the default setting on remix is:
evmVersion: "petersburg"
Whereas on Truffle it is set to
evmVersion: "byzantium"
Setting explicitely byzantium in truffle-config fixed the bytecode, and it's now exactly the same as remix's bytecode.
By default Truffle compiles with enabled optimizations, and Remix with disabled.
The 64 bytes (128 hex-characters) which appear right before the last 2 bytes (4 hex-characters), are metadata.
Truffle generates this metadata based on things like the absolute path of the contract in your file system, the current time and so on.
I'm not sure how Remix generates it, but if the two bytecodes differ only by this part, then you have nothing to worry about.
That said, under a given configuration on Etherscan-verification page, both should be verified or both should be not verified.
If you are getting different results, then the two bytecodes are most likely different from each other not only in the metadata part.
