22 Nov 2026, Sun

Solidity Compiler v0.8.35 Released with First Comptime Builtin, Experimental SSA CFG Code Generator, and Upcoming 0.9.0 Deprecations

The development team behind the Solidity programming language has officially announced the release of the Solidity Compiler version v0.8.35. Building upon a busy cycle of updates and pre-releases, this latest version introduces significant improvements to developer tooling, lays down a formal framework for handling experimental features, and introduces the language’s very first compile-time (comptime) builtin function. The update also continues the ongoing preparation work for the eventual release of Solidity 0.9.0 by issuing crucial deprecation warnings for upcoming keyword promotions.

Some of the groundbreaking features included in this stable release were initially previewed earlier in the year within the v0.8.35-pre.1 pre-release. By bringing these tools into the main release channel, the Solidity core team is offering smart contract developers a cleaner, more robust, and more future-proof development experience across both standard and intermediate representation (IR) compilation pipelines.

Notable Features and Changes

The release of Solidity v0.8.35 brings a robust mix of language-level additions, structural modifications to how experimental features are handled, and critical bug fixes. The most impactful changes revolve around storage layout optimization, a newly formalized experimental process, and a brand-new code generator designed to tackle some of the ecosystem’s most persistent pain points.

The erc7201 Comptime Builtin

One of the standout additions in Solidity 0.8.35 is the introduction of a new builtin function: erc7201(string memory id) returns (uint). This function computes the base storage slot for a namespace string using the precise formula defined in the Ethereum Improvement Proposal ERC-7201, which is mathematically equivalent to keccak256(keccak256(id) - 1) & ~0xff.

ERC-7201 formalizes the widespread industry practice of placing a smart contract’s state behind a hashed namespace. This approach is vital for preventing storage collisions in proxy-based and diamond-style upgradeable contract patterns. The new builtin pairs naturally with the layout at storage layout specifier that was originally introduced in version 0.8.29 and subsequently extended in version 0.8.31.

What makes erc7201 truly unique is that it marks the very first comptime builtin in the language. Until now, Solidity’s comptime evaluator was strictly limited to performing arithmetic operations on rational number literals. While existing builtins like keccak256 have historically undergone constant folding during the optimization stage of code generation—allowing developers to reap gas savings—they lacked the type-system benefit of being usable in a compile-time context, such as a layout specifier or an array length definition.

By allowing erc7201 to be used wherever a comptime expression is required, this release directly addresses limitations previously flagged by the development team, paving the way for a much more capable comptime evaluator in future versions of the compiler.

Formalizing the Experimental Feature Process

In past releases, the Solidity compiler has shipped various in-development features that could be unlocked through an ad-hoc mix of command-line interface flags and pragma experimental directives. This decentralized approach meant there was no consistent, unified way for developers to recognize when they were opting into unstable functionality, and metadata signaling remained patchy at best.

Solidity 0.8.35 introduces a comprehensive formalization of this process, documented thoroughly in the newly updated Experimental Mode documentation. The most visible manifestation of this change is the introduction of a new top-level --experimental flag, along with its boolean counterpart settings.experimental in Standard JSON input configurations.

The --experimental flag serves strictly as a master toggle. On its own, it does not activate any specific feature, but it is now mandatory if a developer wishes to use any per-feature flags or pragmas. Attempting to use experimental features without the master toggle now results in a hard compilation error.

Developers who were already passing affected flags directly will need to update their workflows to include --experimental or set settings.experimental: true in their JSON inputs to keep their builds functioning. This adjustment does not represent a backwards-compatibility break, as experimental features have traditionally been excluded from stability guarantees. Instead, it makes those risks explicit, ensuring that no developer accidentally opts into unstable functionality that carries no stability guarantees and may change in breaking ways even during minor releases.

Furthermore, whether a contract was compiled with experimental mode enabled is now permanently recorded in both JSON and CBOR metadata. The CBOR experimental field, which previously only indicated experimental pragmas present in the source code, has been broadened to cover this entire mode, successfully closing a known oversight where targeting unreleased EVM versions could produce experimental bytecode without signaling the flag.

Experimental SSA CFG Code Generator

Solidity 0.8.35 also ships an experimental new EVM backend for the IR pipeline. This backend generates bytecode directly from the program’s static single-assignment (SSA) form control-flow graphs (SSA CFGs), utilizing a precomputed stack layout that the backend subsequently shuffles the EVM stack to match.

The rationale behind building this new code generator lies in two long-standing pain points for the IR pipeline: excessively slow compilation times and the dreaded stack-too-deep errors. Stack-too-deep errors consistently rank as the most commonly reported recurring issue among smart contract developers, as highlighted in recent developer surveys, and compilation via IR has historically been measurably slower than the traditional evmasm pipeline.

The legacy Yul-to-EVM code transformation relies heavily on heuristics that often struggle when confronted with deeply nested expressions and complex control flow. An SSA-based backend provides a much stronger foundation for both stack scheduling and compilation performance, representing the most realistic long-term solution to these bottlenecks.

Developers can test this code generator by passing --experimental --via-ssa-cfg on the command line, or by configuring settings.experimental: true alongside settings.viaSSACFG: true in Standard JSON inputs. Both options automatically imply --via-ir. While the codegen is continuously tested against the full external-contract semantic test suite on every pull request, it remains an early experimental release. It is not yet the default option for --via-ir, and gas benchmarking alone will not be sufficient to promote it; the team plans to subject it to thorough review, extensive fuzzing, and external auditing before making it the standard.

Deprecation Warnings for Upcoming 0.9.0 Keywords

Continuing the deprecation work that began in version 0.8.31, this release introduces warnings for identifiers that the core team plans to formally promote to keywords in the upcoming major release, Solidity 0.9.0. While the previous deprecations focused primarily on removing obsolete features, this batch centers entirely on claiming names to prevent future conflicts.

Solidity declarations utilizing identifiers such as at, error, layout, leave, super, this, or transient will now emit a warning. Within Yul, whether used standalone or within inline assembly blocks, leave is slated to become a Yul keyword, while basefee, blobbasefee, blobhash, clz, mcopy, memoryguard, prevrandao, tload, and tstore will become reserved Yul identifiers. Because these latter terms are standard Yul builtins that are typically kept reserved, the growing list of exceptions is a byproduct of the unusually long 0.8.x release cycle, as the compiler’s strict backwards-compatibility policy holds them until the 0.9.0 boundary.

These notifications are issued purely as warnings rather than hard errors. Existing codebases will continue to compile successfully, giving developers an adequate window to rename affected declarations well before version 0.9.0 turns these warnings into breaking compilation errors.

Revert Strings Strip and Custom Errors

Another notable fix addresses an interaction between optimization flags and custom errors. The option --revert-strings strip (or revertStrings: "strip" in Standard JSON) is a popular gas-saving feature that strips revert reason strings from the generated bytecode while ensuring that reverts still occur. The implicit assumption behind this setting has traditionally been that returndata serves merely as a human-readable message rather than structured data that dependent contracts should rely upon.

The introduction of require(condition, CustomError(...)) in version 0.8.26 complicated this assumption because custom errors explicitly encode structured data. Until version 0.8.35, the IR pipeline would aggressively strip the custom-error argument of a require statement alongside standard strings, resulting in failed require calls reverting with empty error data instead of the properly encoded custom error. Meanwhile, the legacy evmasm pipeline handled this differently, creating an inconsistency between pipelines. The development team resolved this discrepancy by ensuring that custom errors are preserved, avoiding a scenario where stripping revert strings would inadvertently destroy structured error data. This fix applies specifically to require() statements utilizing custom errors within the IR pipeline.

Ethdebug Output Reorganization

Finally, this release reorganizes the output selection for ethdebug to make it more granular and consistent with how other compiler outputs are exposed. The old --ethdebug and --ethdebug-runtime flags have been replaced by --ethdebug-resources, --ethdebug-compilation, --ethdebug-program, and --ethdebug-program-runtime, with corresponding keys introduced in Standard JSON. Ethdebug outputs no longer force a full binary compilation by default, and the tool remains experimental, appropriately gated behind the new --experimental flag alongside other unstable features.

How to Install and Upgrade

Developers wishing to upgrade to the latest iteration of the compiler can consult the official installation instructions available in the Solidity documentation. The release packages and binaries can be downloaded directly from the official GitHub repository under release tag v0.8.35.

For those compiling the software directly from source, the development team strongly advises against using the automatically generated source archives provided by GitHub. Instead, developers should utilize the official solidity_0.8.35.tar.gz source tarball or check out the exact v0.8.35 tag via git to ensure a reliable and verifiable build. The core team has expressed gratitude to all community contributors who tested pre-releases, reported bugs, and helped bring this major release to completion.

Leave a Reply

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