The development team behind Solidity, the leading smart contract programming language for the Ethereum ecosystem and EVM-compatible networks, has officially announced the launch of Solidity v0.8.36. This latest software release brings a variety of crucial updates, including a pair of medium-severity security fixes, targeted enhancements to the compiler’s intermediate representation (IR) pipeline, and necessary codebase housekeeping following recent shifts in Ethereum network upgrade roadmaps.
The rollout of version 0.8.36 marks another step forward in the continuous evolution of the compiler infrastructure. As smart contract complexity grows within decentralized finance, gaming, and enterprise applications, the Solidity team has maintained a sharp focus on improving backend efficiency, resolving long-standing compilation roadblocks like the notorious "stack-too-deep" error, and hardening the overall security posture of the language. Developers relying on the compiler can now access the release across standard distribution channels, with several key changes highlighting the update.
Important Bugfixes and Security Enhancements
Security remains a foundational priority for the Solidity core maintenance team, given the high-stakes financial environment in which smart contracts operate. Solidity v0.8.36 ships with two specific security fixes designed to address vulnerabilities classified at a medium severity level. While routine updates often focus purely on developer experience and syntax features, maintaining rigorous defense-in-depth measures within the compiler itself is critical to preventing unintended compilation artifacts or security lapses in deployed bytecode.
Although the detailed mechanics of these medium-severity patches are integrated into the broader changelog for the release, their inclusion underscores the ongoing commitment of the maintainers to proactively identify and mitigate risks. Developers are strongly encouraged to review the full changelog documentation and integrate the new version into their continuous integration and deployment pipelines to ensure their smart contracts benefit from the latest security hardening.
SSA CFG Stack-to-Memory Spilling (Experimental)
One of the most notable engineering advancements in Solidity v0.8.36 centers on the experimental static single assignment (SSA) form control-flow-graph (CFG) code generator. First introduced in the preceding v0.8.35 release as part of the compiler’s modern IR pipeline, the SSA backend represented a major shift in how Solidity structures and optimizes intermediate code generation. However, upon its initial debut, developers noted a significant limitation: stack-to-memory spilling had not yet been ported over to the SSA architecture.
With the arrival of v0.8.36, this capability has officially been added to the experimental backend. Stack-to-memory spilling allows the code generator to intelligently move local variables and intermediate values out of the EVM’s restricted execution stack and into memory whenever stack depth limitations are approached. In practical terms, this effectively solves the frustrating "stack-too-deep" compilation error for contracts utilizing the SSA backend—an issue that has historically plagued complex smart contract development by forcing developers to artificially refactor their code, wrap variables in structs, or split functions into smaller components.
Despite this major functional milestone, the SSA CFG code generator remains experimental. It is not yet enabled by default within the standard --via-ir compilation pipeline. Developers wishing to test the feature and leverage stack spilling must explicitly invoke it using the compiler flags --experimental --via-ssa-cfg. The Solidity core team has indicated that stabilizing and maturing the SSA CFG code generator stands as one of their primary engineering priorities for the upcoming six-month development cycle, signaling that a wider rollout and eventual default adoption may lie on the horizon as testing and validation continue.
Removal of the Experimental EOF Backend
Alongside the introduction of new experimental features, Solidity v0.8.36 also brings code cleanup by officially removing the experimental EVM Object Format (EOF) backend. In previous development cycles, substantial engineering effort was dedicated to implementing comprehensive EOF support within the compiler. This work was undertaken in enthusiastic anticipation of EOF’s inclusion in the upcoming Fusaka network upgrade, which was widely discussed across the broader Ethereum core development community.
However, as the upgrade specifications evolved and discussions progressed among Ethereum core developers, the EOF feature proposal was ultimately rejected from inclusion in the Fusaka network upgrade late in the planning process. Because the format lacks mainnet support and currently faces no concrete prospect of adoption by any operational blockchain network in the foreseeable future, maintaining the backend within the Solidity codebase became obsolete.
To prevent technical debt and keep the compiler codebase lean, maintainers elected to remove the experimental EOF backend entirely in version 0.8.36. This routine housekeeping ensures that the development team can focus its resources on active pipelines, such as the aforementioned SSA backend and core EVM optimizations, rather than maintaining dormant features tied to rejected protocol upgrades.
How to Install and Upgrade
Developers looking to incorporate Solidity v0.8.36 into their development workflows can access comprehensive upgrade guidance through the official Solidity documentation portal. Pre-compiled binaries and release packages are hosted directly on the project’s GitHub repository under the v0.8.36 release tag.
Teams that prefer building the compiler directly from source code are advised to exercise caution regarding source archive selection. Maintainers have emphasized that developers should avoid utilizing the generic source archives that are generated automatically by GitHub’s infrastructure. Instead, the correct procedure requires downloading the dedicated solidity_0.8.36.tar.gz source tarball provided in the release assets, or alternatively checking out the precise v0.8.36 tag via Git to ensure cryptographic and structural integrity.
The release of Solidity v0.8.36 highlights the steady, methodical progress of the language’s compilation infrastructure, balancing immediate security needs with forward-looking architectural experiments. As the developer community adopts the new version, feedback on the experimental SSA backend will likely play a vital role in shaping the future of smart contract compilation on Ethereum and compatible networks.

