18 Nov 2026, Wed

Solidity v0.8.36 Released With Experimental SSA Stack-to-Memory Spilling and Security Patches

The development team behind Solidity, the leading programming language for writing smart contracts on Ethereum and other compatible blockchain networks, has officially announced the launch of Solidity version 0.8.36. This latest software

release brings a collection of important updates to the compiler ecosystem, addressing critical code generation capabilities while responding to shifts in broader Ethereum network upgrade roadmaps.

Among the primary highlights of the v0.8.36 release are two medium-severity security fixes designed to strengthen the overall security posture of compiled smart contracts. In addition to these patches, the update delivers meaningful progress on the experimental front. Specifically, it expands the capabilities of the SSA-form control-flow-graph code generator that was initially rolled out in the previous major release, introducing much-needed stack-to-memory spilling to combat persistent compilation bottlenecks. At the same time, the release team has officially removed the experimental EVM Object Format backend, cleaning up obsolete code following recent changes to upcoming network upgrade plans across the wider ecosystem.

Important Bugfixes

Software security and reliability remain central priorities for the Solidity core maintenance team. Version 0.8.36 ships with two essential security fixes aimed at mitigating vulnerabilities classified as medium severity. While compilers serve as the invisible bridge between developer-written source code and the machine-executable bytecode deployed on the blockchain, any latent bug or edge case within the compiler logic can introduce subtle flaws into smart contracts.

The inclusion of these medium-severity security patches underscores the continuous auditing and maintenance effort required to keep decentralized application infrastructure secure. Developers and smart contract engineers are routinely advised to keep their compilation toolchains up to date to benefit from these behind-the-scenes protections, minimizing the risk of deploying contracts with known compiler-level vulnerabilities.

Notable Features and Changes

Beyond security patches, Solidity v0.8.36 introduces targeted modifications to the compiler’s internal architecture, reflecting both forward-looking performance goals and necessary maintenance in response to evolving Ethereum layer developments.

SSA CFG Stack-to-Memory Spilling (Experimental)

A cornerstone of this release is the enhancement of the experimental static single assignment (SSA) form control-flow-graph (CFG) code generator, which was first integrated into the intermediate representation (IR) pipeline in version 0.8.35. When the SSA backend was originally introduced, developers noted a notable limitation: stack-to-memory spilling had not yet been implemented for that specific architecture.

Version 0.8.36 addresses this gap by successfully porting stack-to-memory spilling into the SSA backend. In the Ethereum Virtual Machine, the limited availability of stack slots frequently leads to the infamous "stack too deep" compilation error, a common frustration for developers writing complex smart contracts with numerous local variables and deeply nested scopes. With the new spilling mechanism in place, the code generator can intelligently shift values from the restricted evaluation stack into memory when necessary. Consequently, complex codebases that would otherwise be rejected by existing compilation pipelines can now successfully compile through the SSA backend.

Despite this major functional leap forward, the SSA CFG code generator remains experimental. It must be explicitly invoked using the command-line flags --experimental alongside --via-ssa-cfg, and it is not yet set as the default behavior for the standard --via-ir pipeline. However, the Solidity development team has indicated that stabilizing and maturing the SSA CFG code generator stands as one of their primary engineering objectives over the coming six months, paving the way for more efficient and robust code generation in future stable releases.

Removal of the Experimental EOF Backend

In another significant architectural change, version 0.8.36 completely removes the experimental EVM Object Format (EOF) backend. A considerable amount of engineering effort had previously been dedicated to implementing robust EOF support within the compiler, built in eager anticipation of its inclusion in the upcoming Fusaka network upgrade.

However, late in the development and consensus process, the EOF proposal was ultimately rejected from inclusion in the Fusaka upgrade package. With no viable mainnet deployment schedule and no realistic prospect of adoption by any active blockchain network in the foreseeable future, the experimental EOF backend became functionally obsolete. Rather than maintaining dead code that could add unnecessary complexity and technical debt to the codebase, the maintainers chose to remove the feature entirely as part of routine project housekeeping, streamlining and simplifying the Solidity source code repository.

Full Changelog and Bugfixes

The v0.8.36 release encompasses a wide array of meticulous internal improvements spanning compiler features, diagnostic enhancements, and general bugfixes. The core contributors have continuously refined the tooling to ensure predictable behavior, better error messaging, and improved optimization paths across various execution environments. While the headline features focus heavily on the SSA backend evolution and cleanup of obsolete components, the comprehensive changelog reflects ongoing collaboration from a vast community of open-source contributors dedicated to the long-term health and evolution of the Solidity ecosystem.

How to Install and Upgrade

Developers looking to migrate their projects to the latest iteration of the language can access the update immediately. Upgrading to Solidity v0.8.36 involves following the standard installation instructions detailed in the official project documentation.

Pre-compiled binaries and release packages are readily available for download directly through the official GitHub repository under the v0.8.36 release tag. Developers who prefer building the compiler toolchain directly from source code are explicitly advised to avoid using the automatic source archives generated by GitHub. Instead, the team recommends downloading the official solidity_0.8.36.tar.gz source tarball or checking out the exact v0.8.36 tag via Git to ensure a complete and verified build environment.

The Solidity core team has expressed deep appreciation for the community of independent contributors, security researchers, and developers whose ongoing feedback, code contributions, and testing efforts continue to drive the growth and stability of the platform forward.

Leave a Reply

Your email address will not be published. Required fields are marked *