Close Menu

    Subscribe to Updates

    Get the latest creative news from FooBar about art, design and business.

    What's Hot

    Michael Saylor hints at another Strategy Bitcoin buy after BTC crash

    November 22, 2026

    Solana upgrades to mainnet 1.0 as Foundation takes majority CoinGecko stake

    November 22, 2026

    Why Bitcoin’s quantum security upgrade may take years

    November 22, 2026
    Facebook X (Twitter) Instagram
    Cryptify Now
    • Home
    • Features
      • Typography
      • Contact
      • View All On Demos
    • Typography
    • Buy Now
    X (Twitter) Instagram YouTube LinkedIn
    Cryptify Now
    You are at:Home » Solidity optimizer bug | Ethereum Foundation Blog
    Ethereum

    Solidity optimizer bug | Ethereum Foundation Blog

    Olivia MartinezBy Olivia MartinezNovember 4, 2026No Comments3 Mins Read
    Facebook Twitter Pinterest LinkedIn Tumblr Email
    Share
    Facebook Twitter LinkedIn Pinterest Email


    A bug in the Solidity optimizer was reported through the Ethereum Foundation Bounty program, by Christoph Jentzsch. This bug is patched as of 2017-05-03, with the release of Solidity 0.4.11.

    Background

    The bug in question concerned how the optimizer optimizes on constants in the byte code. By “byte code constants”, we mean anything which is PUSHed on the stack (not to be confused with Solidity constants). For example, if the value 0xfffffffffffffffffffffffffffffffffffffffffffffffe is PUSHed, then the optimizer can either do PUSH32 0xfffffffffffffffffffffffffffffffffffffffffffffffe, or choose to encode this as PUSH1 1; NOT;.

    An error in the optimizer made optimizations of byte code constants fail for certain cases by producing a routine that did not properly recreate the original constant.

    The behavior described in the reported bug was found in a contract in which one method ceased functioning when another – totally unrelated – method was added to the contract. After analysis, it was determined that a number of conditions must exist at once for the bug to trigger. Any combination of conditions that would trigger the bug would consistently have the following two conditions:

    1. The constant needs to start with 0xFF… and end with a long series of zeroes (or vice versa).
    2. The same constant needs to be used in multiple locations, for the optimizer to choose to optimize this particular constant. Alternatively, it needs to be used in the constructor, which optimises for size rather than gas.

    In addition to the two conditions above, there are further, more complicated conditions that are required.

    Analysis

    This bug is present in all released versions of Solidity from at least as far back as summer 2015 to the present. Although the bug has been present since 2015, it seems very hard to trigger by “random” code:

    We performed a static analysis of all contract code deployed on the blockchain, and found no occurrence of such an invalidly generated routine. Note, the fact that we have not found a bug in all the contract code does not guarantee the absence of such occurrences.

    Improvements

    In order to provide better transparency and increased awareness of bugs in Solidity, we have started exporting information about Solidity-related vulnerabilities as JSON-files in the Solidity code repository(1,2). We hope that block explorers will integrate this information along with other contract-related information.

    Etherscan has already implemented this, which can be seen here and here.

    Concerning the bug itself, we added a mini-EVM to the optimizer which verifies the correctness of each generated routine at compile time.

    Furthermore, work has already started on a fully-specified and more high-level intermediate language. Future optimizer routines on this language will be much easier to understand and audit and it will replace the current optimizer.



    Source link

    Share. Facebook Twitter Pinterest LinkedIn Tumblr Email
    Previous ArticleSuccess Story: Aman Singh’s Learning Journey with 101 Blockchains
    Next Article Riot Platforms completes Bitcoin custody transfer from NYDIG to BitGo
    Olivia Martinez

    Related Posts

    Bootstrapping A Decentralized Autonomous Corporation: Part I

    November 19, 2026

    Bootstrapping An Autonomous Decentralized Corporation, Part 2: Interacting With the World

    November 19, 2026

    Bootstrapping a Decentralized Autonomous Corporation, Part 3: Identity Corp

    November 19, 2026
    Leave A Reply Cancel Reply

    Top Posts

    Can Solana price hit $130 after Forward Industries buys…

    October 2, 2026

    Technical Architecture of Real-World Asset Tokenization

    October 2, 2026

    Cardano Faces Bearish Signals as Futures Demand Cools and Whales Sell

    October 7, 2026

    How native transaction assertions could enforce a transaction’s final outcome

    October 7, 2026
    Don't Miss

    Michael Saylor hints at another Strategy Bitcoin buy after BTC crash

    By James WilsonNovember 22, 2026

    Michael Saylor has raised expectations of another Bitcoin purchase by Strategy after sharing his familiar…

    Solana upgrades to mainnet 1.0 as Foundation takes majority CoinGecko stake

    November 22, 2026

    Why Bitcoin’s quantum security upgrade may take years

    November 22, 2026

    Trump memecoin dinner struggles to fill seats as $518 buyer qualifies

    November 22, 2026
    Stay In Touch
    • Facebook
    • Twitter
    • Pinterest
    • Instagram
    • YouTube
    • Vimeo

    Subscribe to Updates

    Get the latest creative news from SmartMag about art & design.

    Demo
    About Us
    About Us

    CryptifyNow: Your daily source for the latest insights, news, and analysis in the ever-evolving world of cryptocurrency.

    X (Twitter) Instagram YouTube LinkedIn
    Our Picks

    Michael Saylor hints at another Strategy Bitcoin buy after BTC crash

    November 22, 2026

    Solana upgrades to mainnet 1.0 as Foundation takes majority CoinGecko stake

    November 22, 2026

    Why Bitcoin’s quantum security upgrade may take years

    November 22, 2026
    Lithosphere News Releases
    Copyright © 2026

    Type above and press Enter to search. Press Esc to cancel.