A bug within the Solidity Optimizer was reported by way of Ethereum Basis Bounty Program, by Christoph Gentzsch. This bug has been patched as of 2017-05-03 with the discharge of Solidity 0.4.11.


The bug in query is expounded to how the optimizer optimizes over constants in byte code. By “byte code fixed” we imply something to pushEd on the stack (to not be confused with Solidity constants). For instance, if the worth 0xffffffffffff Is to pushed, so the optimizer can both PUSH32 0xffffffffffffffffffor select to encode it as push1 1; No;,

Optimization of byte code constants failed for some circumstances attributable to an error within the optimizer, which produced a routine that didn’t correctly recreate the unique constants.

The conduct described within the reported bug was present in a contract during which a technique stopped working when one other – fully unrelated – technique was added to the contract. After evaluation, it was decided that a number of situations should exist concurrently for the bug to be triggered. Any mixture of situations that may set off a bug would include two consecutive situations:

  1. steady have to initialize 0xFF… and ends with an extended sequence of zeroes (or vice versa).
  2. The identical fixed must be utilized in a number of locations to ensure that the optimizer to decide on to optimize away this specific fixed. Alternatively, it must be used within the constructor, which optimizes for measurement as a substitute of gasoline.

Along with the above two situations, extra complicated situations are mandatory.


This bug has been current in all launched variations of Solidity from no less than the summer time of 2015 to the current. Though the bug has been current since 2015, it appears not possible to be triggered by “random” code:

We carried out a static evaluation of all contract code deployed on the blockchain, and located no occurrences of such invalidly generated routines. Word, the truth that we discovered no bugs in all contract code doesn’t assure the absence of such incidents.


In an effort to have higher transparency and enhance consciousness of bugs in Solidity, we have now began exporting details about Solidity associated vulnerabilities within the type of JSON-files to the Solidity code repository.1,2, We count on Block Explorers to combine this data with different contract-related data.

Etherscan has already carried out this, which could be seen in Right here And Right here,

Relating to bugs, we have added a mini-EVM to the optimizer that verifies the correctness of every generated routine at compile time.

As well as, work has already begun on a totally specified and extra high-level intermediate language. Will probably be a lot simpler to know and audit future optimizer routines on this language and it’ll substitute the present optimizer.

Recommended Posts