The development team behind Solidity, the leading smart contract programming language for the Ethereum ecosystem and EVM-compatible networks, has officially announced the release of Solidity v0.8.36. This latest stable version brings a series of vital updates, including two medium-severity security fixes, crucial improvements to the experimental Single Static Assignment (SSA) control-flow graph (CFG) code generator, and the complete removal of the obsolete Ethereum Object Format (EOF) backend.
As smart contract security and compiler optimization remain paramount in the fast-paced world of decentralized finance and blockchain engineering, the release of version 0.8.36 marks another step forward in the ongoing refinement of the Solidity toolchain. Developers working across decentralized applications, protocols, and foundational infrastructure are encouraged to review the changes and plan their upgrade paths accordingly.
Important Bugfixes and Security Enhancements
At the heart of the Solidity v0.8.36 release are two essential security patches. Although specific details regarding the exploit vectors or exact mechanics of the vulnerabilities are typically disclosed through official security advisories to give developers time to patch their code, the development team has classified both fixes as having a medium severity level. These fixes address underlying flaws in the compiler that, if left unaddressed, could potentially lead to unexpected compilation behaviors or edge-case vulnerabilities in deployed smart contracts.
In addition to these security updates, the release incorporates various general bugfixes aimed at improving overall compiler stability, type-checking precision, and code generation accuracy across different deployment targets. Maintaining robust security practices and swift vulnerability mitigation continues to be a core focus for the Solidity core maintainers, ensuring that developers can rely on the compiler to translate high-level business logic into secure and predictable EVM bytecode.
SSA CFG Stack-to-Memory Spilling Marks Major Experimental Progress
One of the most notable engineering advancements in Solidity v0.8.36 revolves around the experimental SSA-form control-flow graph code generator, which was initially introduced to the Intermediate Representation (IR) pipeline in version 0.8.35. When that feature first rolled out, developers noted a significant gap: stack-to-memory spilling had not yet been ported to the SSA backend.
Solidity v0.8.36 successfully bridges that gap by introducing stack-to-memory spilling to the experimental SSA backend. In the Ethereum Virtual Machine, developers frequently encounter the notorious "Stack Too Deep" error when dealing with functions that have too many local variables, complex control flow, or deeply nested logic. This limitation arises because the EVM lacks registers and instead relies on a strictly bounded evaluation stack.
With stack-to-memory spilling now active in the SSA pipeline, the code generator can intelligently move values from the constrained execution stack into memory when necessary. Consequently, complex codebases that previously failed compilation under existing pipelines due to stack overflow limitations can now compile successfully through the SSA backend.
Despite this significant milestone, the SSA CFG code generator remains experimental. It is not yet enabled by default for the standard --via-ir pipeline, and developers wishing to test it must explicitly enable it using the command-line flags --experimental --via-ssa-cfg. The Solidity core team has indicated that stabilizing and fully maturing the SSA CFG code generator is one of their primary engineering priorities for the upcoming six-month development cycle, signaling a major future shift in how Solidity optimizes and generates low-level bytecode.
Removal of the Experimental EOF Backend
Solidity v0.8.36 also features significant codebase cleanup with the official removal of the experimental EVM Object Format (EOF) backend. A substantial amount of engineering work and code had previously been implemented to support EOF in anticipation of its inclusion in the forthcoming Fusaka network upgrade.
However, plans changed late in the development process when EOF was ultimately rejected from inclusion in the network upgrade. Because the feature lacks mainnet support and currently has no realistic prospect of adoption by any major Ethereum network in the foreseeable future, the experimental backend became entirely obsolete. As part of routine maintenance and long-term repository hygiene, the development team has elected to strip out the unused EOF support, thereby simplifying the codebase, reducing technical debt, and streamlining future maintenance efforts.
How to Install and Upgrade to Solidity v0.8.36
Developers looking to integrate Solidity v0.8.36 into their local development environments and continuous integration pipelines can find comprehensive installation guidelines within the official Solidity documentation. The release packages and binaries are hosted directly on the project’s GitHub repository under the v0.8.36 release tag.
For teams and individual developers who prefer building the compiler directly from the source code, the maintainers issue a specific reminder regarding source archives. Developers are explicitly advised to avoid using the generic source archives that are automatically generated by GitHub. Instead, builds should be performed using the dedicated solidity_0.8.36.tar.gz source tarball provided in the release assets, or by checking out the exact v0.8.36 tag directly via Git to ensure integrity and correct submodule dependencies.
The Solidity core team extended formal acknowledgments to the wide community of independent contributors, testers, and protocol developers whose ongoing feedback, bug reports, and code contributions made the v0.8.36 release possible. As the ecosystem continues to evolve, regular updates like this ensure that Solidity remains a secure, powerful, and adaptable language for the next generation of blockchain architecture.

