Why does an Oraclize contract deployed with Remix JavaScript VM gives an "invalid opcode error" and not on main/testnet?
I have thought why the Remix JavaScript VM reports the error:
Exception during execution. (invalid opcode). Please debug the transaction for more information.
for any Oraclize contract Create
through the Remix interface, when the same contract is perfectly deployable on the main/testnet?
In the end, solc
compiles the contract, so if the bytecode contains an invalid opcode, it must be the case also on the main/testnet? So, why doesn't Ethereum complaint when the contract is deployed on, e.g., Rinkeby?
Does anyone have technical insight to describe why only the Remix JavaScript VM sees an invalid opcode?