The development team behind Solidity, the leading programming language for writing smart contracts on Ethereum and other compatible blockchains, has officially announced the release of Solidity v0.8.36. This latest update brings crucial security patches, significant architectural cleanup, and continued experimental enhancements to the compiler’s intermediate representation (IR) pipeline.
As smart contract security remains paramount in the decentralized finance and Web3 ecosystem, regular compiler updates are vital for maintaining robust, bug-free decentralized applications. Version 0.8.36 arrives with a focused set of improvements designed to enhance overall developer experience, resolve persistent compilation hurdles, and streamline the compiler codebase by removing obsolete components.
Developers and smart contract engineers can now access the new release directly via the official GitHub repository, alongside updated installation guides provided in the official Solidity documentation.
Important Bugfixes and Security Updates
At the heart of the Solidity v0.8.36 release are two important security fixes. Both addressed vulnerabilities have been classified as medium severity. While high-severity bugs often capture the most headlines in the blockchain industry, medium-severity fixes are equally critical for preventing subtle compilation anomalies, unexpected execution behavior, or edge-case logic flaws that could potentially affect smart contract deployments.
Although the detailed breakdown of the internal bug mechanics is distributed across the full changelog entries within the release notes, the development team consistently urges development teams to upgrade their toolchains promptly. Integrating these medium-severity security patches ensures that projects compiling via standard pipelines remain protected against newly identified edge cases within the parser, typechecker, and code generation phases.
Notable Features and Changes
SSA CFG Stack-to-Memory Spilling (Experimental)
One of the most notable engineering advancements in Solidity v0.8.36 revolves around the experimental Static Single Assignment (SSA) form control-flow-graph (CFG) code generator. Solidity version 0.8.35 initially introduced this experimental SSA-form CFG code generator for the IR pipeline, marking a major step toward modernizing the compiler’s optimization and code generation infrastructure.
However, when that feature initially landed, a notable gap remained: stack-to-memory spilling had not yet been ported over to the SSA backend. This limitation meant that complex smart contracts with deeply nested scopes or a high number of local variables could still hit optimization roadblocks.
Solidity v0.8.36 addresses this missing piece by introducing stack-to-memory spilling to the experimental SSA backend. With spilling now fully integrated, the code generator possesses the capability to automatically move variables and values from the limited EVM stack into memory when necessary during compilation. Consequently, complex code structures that previous alternative pipelines would otherwise reject with the infamous "stack too deep" error can now successfully compile through the SSA backend.
The development team has clarified that this capability remains strictly experimental for now. Developers wishing to test it out must explicitly enable it using the --experimental --via-ssa-cfg command-line flags. It is not yet set as the default behavior when using the standard --via-ir compilation pipeline. Nevertheless, stabilizing and maturing the SSA CFG code generator stands as one of the core development priorities for the Solidity team over the next six months, signaling a major trajectory shift for future compiler architectures.
Removal of the Experimental EOF Backend
In a move to clean up and reduce technical debt within the compiler repository, Solidity v0.8.36 officially removes the experimental EVM Object Format (EOF) backend.
A substantial amount of engineering work had previously gone into implementing comprehensive EOF support within the compiler. This implementation was undertaken in anticipation of EOF’s inclusion in the upcoming Fusaka network upgrade. However, as the upgrade specifications evolved, the EOF feature was ultimately rejected from inclusion in Fusaka late in the process.
With no active mainnet support scheduled and no realistic prospect of adoption by any major Ethereum-compatible network in the near future, the experimental EOF backend became entirely obsolete. Rather than maintaining dead code that could complicate future compiler updates, the development team chose to excise the backend as a matter of routine codebase housekeeping. This removal simplifies the internal architecture of the Solidity compiler, ensuring that maintenance efforts remain focused on active, production-ready features.
Full Changelog and Compiler Updates
The comprehensive release notes for v0.8.36 include structured breakdowns across multiple categories, encompassing internal compiler features, minor bugfixes, and infrastructure enhancements. While the experimental SSA backend and the removal of EOF dominate the major talking points of this release cycle, dozens of smaller adjustments contribute to the overall stability and reliability of the language toolchain.
For developers looking to integrate Solidity v0.8.36 into their existing development workflows—whether using Hardhat, Foundry, Remix, or direct command-line compilation—upgrading requires following the standard installation procedures outlined in the official documentation.
When building the compiler directly from source code, developers are strongly advised to avoid using the automatically generated source archives provided by GitHub by default. Instead, the team recommends utilizing the official solidity_0.8.36.tar.gz source tarball or checking out the v0.8.36 Git tag directly to ensure proper dependency resolution and build integrity.
The Solidity core team extended its gratitude to the wide community of open-source contributors, testers, and security researchers whose ongoing feedback, bug reports, and code contributions made the v0.8.36 release possible.

