The Solidity development team has officially announced the release of Solidity v0.8.36, the latest iteration of the widely used programming language for writing smart contracts on Ethereum and other compatible blockchain networks. This new release brings a pair of medium-severity security fixes, notable improvements to the experimental intermediate representation (IR) pipeline, and a clean-up of deprecated architecture in response to broader Ethereum network upgrade changes.
Available now for download via GitHub and standard package managers, version 0.8.36 continues the core team’s focus on optimizing compiler performance, improving code generation backends, and ensuring robust security across the decentralized application ecosystem.
Important Bugfixes and Security Updates
At the heart of the Solidity v0.8.36 release are two important security fixes, both classified as medium severity. While smart contract developers routinely rely on the compiler to catch basic syntax and logic errors, underlying compiler bugs can occasionally introduce subtle vulnerabilities or unexpected execution paths into compiled bytecode. The development team strongly advises all developers, protocol engineers, and security auditors to update their compilation pipelines to version 0.8.36 to ensure these patches are integrated into their development workflows.
Although specific details regarding the exact nature of the medium-severity fixes are typically elaborated within the formal GitHub advisory and changelog documentation, updates of this tier generally address edge cases in data encoding, memory management, or control-flow translation within the compiler’s code generation phases. Maintaining an up-to-date compiler version remains one of the foundational best practices in smart contract security, mitigating the risk of deploying contracts affected by recently discovered compiler-level flaws.
Notable Features and Changes
Beyond security patches, Solidity v0.8.36 introduces significant updates to its compilation architecture. Most notably, the release advances the development of the experimental SSA-form control-flow-graph (CFG) code generator while simultaneously pruning obsolete backend code that no longer aligns with Ethereum mainnet roadmap trajectories.
SSA CFG Stack-to-Memory Spilling (Experimental)
In Solidity 0.8.35, the core team introduced an experimental SSA-form control-flow-graph code generator designed specifically for the IR pipeline. While that initial rollout marked a major milestone in modernizing the compiler’s architecture, developers quickly encountered functional gaps. Most notably, stack-to-memory spilling had not yet been ported to the SSA backend, leaving certain complex contracts unable to compile successfully.
Solidity v0.8.36 directly addresses this limitation by introducing stack-to-memory spilling to the experimental SSA backend. With this functionality now in place, the code generator gains the ability to seamlessly move variables and values to memory when the EVM execution stack reaches its capacity limits. As a result, large and complex smart contract codebases that previously triggered the dreaded "stack too deep" error under existing compilation pipelines can now successfully compile through the SSA backend.
Despite this major functional improvement, the feature remains strictly experimental. Developers wishing to test the updated SSA CFG backend must explicitly enable it using the command-line flags --experimental --via-ssa-cfg. It is not yet enabled by default for the standard --via-ir compilation pipeline. According to the development roadmap, stabilizing the SSA CFG code generator stands as one of the primary engineering priorities for the core team over the next six months as they work toward making it production-ready.
Removal of the Experimental EOF Backend
In another notable change, Solidity v0.8.36 completely removes the experimental EVM Object Format (EOF) backend. A substantial amount of engineering effort had previously been dedicated to implementing EOF support within the compiler in anticipation of its inclusion in the upcoming Fusaka network upgrade.
However, as the consensus around the Fusaka upgrade evolved, the EOF feature was ultimately rejected from inclusion late in the process. With no active mainnet support for EOF and no realistic prospect of adoption by any operational Ethereum-compatible network in the near future, the dedicated compiler backend became obsolete. As part of routine code maintenance and housekeeping, the development team elected to remove the redundant code entirely, thereby simplifying the compiler’s codebase, reducing maintenance overhead, and preventing potential confusion among developers.
How to Install and Upgrade
Developers looking to integrate Solidity v0.8.36 into their existing development environments can follow the comprehensive installation instructions provided in the official Solidity documentation. The release binaries and source code packages are hosted directly on the project’s official GitHub repository.
Teams that prefer to build the compiler directly from source are strongly cautioned against using the automatically generated source archives provided by GitHub’s default interface. Instead, developers must use the official solidity_0.8.36.tar.gz source tarball or check out the exact v0.8.36 tag via Git to ensure proper dependency management and build integrity.
The Solidity core team has extended its gratitude to the open-source contributor community whose ongoing feedback, testing, and code contributions continue to drive the evolution and security of the language.






