18 Nov 2026, Wed

Solidity Compiler v0.8.35 Released with ERC-7201 Comptime Builtin and Experimental SSA CFG Code Generator

The development team behind the Solidity programming language has officially announced the release of the Solidity Compiler version v0.8.35. This latest update introduces several significant features, architectural enhancements, and critical bug fixes that target long-standing developer pain points within the Ethereum ecosystem. Among the highlights of the v0.8.35 release are a new compile-time builtin function designed to streamline namespaced storage layouts, a formalization of the compiler’s experimental feature workflow, an early-stage static single-assignment control-flow graph code generator for the IR pipeline, and continued preparation for the upcoming major version 0.9.0.

Some of the foundational elements included in this stable release were previously previewed by the core team earlier in the year through the v0.8.35-pre.1 pre-release distribution. With the official rollout, developers can now incorporate these capabilities into their production and staging environments, backed by comprehensive documentation and refined tooling support.

Notable Features and Changes

The erc7201 Comptime Builtin

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

ERC-7201 has become an increasingly vital standard across the smart contract landscape, formalizing the practice of isolating a contract’s state behind a securely hashed namespace. This structural pattern effectively prevents storage collisions in complex proxy-based architectures and diamond-style upgradeable smart contract patterns.

This new builtin pairs seamlessly with the layout at storage layout specifier that was initially rolled out in version 0.8.29 and subsequently expanded in version 0.8.31. Developers can now cleanly define storage slots using expressions such as contract MyContract layout at erc7201("openzeppelin.storage.MyContract") uint256 x; uint256 y; .

Crucially, erc7201 represents a historic milestone for the language: it is the very first compile-time (comptime) builtin introduced into Solidity. Historically, the compiler’s comptime evaluator was strictly limited to arithmetic operations performed on rational number literals. While traditional builtins like keccak256 have long benefited from constant folding during the compiler’s optimization phase—granting runtime gas savings—they lacked the type-system capability required to function within strict comptime contexts like storage layout specifiers or array lengths. By making erc7201 fully available wherever a comptime expression is required, the development team has directly resolved limitations previously highlighted during the 0.8.31 release cycle, paving the way for a more robust and capable comptime evaluator in future versions of the language.

Formalizing the Experimental Feature Process

In past releases, the Solidity compiler introduced various in-development features that relied on an ad-hoc mixture of command-line interface flags and pragma experimental directives. This decentralized approach meant that developers frequently lacked a consistent mechanism to identify whether they were opting into unstable functionality, and metadata signaling remained patchy across builds.

Solidity v0.8.35 addresses this transparency gap by formalizing a strict process for handling experimental features, detailed extensively in the updated documentation. Under this new framework, utilizing any experimental capability now requires the inclusion of a master top-level --experimental flag on the command line, or the corresponding boolean settings.experimental field within Standard JSON inputs.

The --experimental flag acts strictly as a master toggle. By itself, it does not enable any specific feature; rather, it serves as a prerequisite gateway for any individual per-feature flags or pragmas to be accepted by the compiler. Attempting to use an experimental feature without explicitly passing the master toggle now triggers a hard compilation error. Developers who were previously passing affected feature flags directly will need to update their build pipelines to include --experimental or adjust their JSON configuration files to keep their builds operational.

The core team emphasizes that this change does not constitute a backwards-compatibility break, as experimental features have always been explicitly excluded from standard compatibility guarantees. Instead, the update makes this unstable status explicit at the user-facing surface, ensuring developers are fully aware when they are opting into functionality that carries no stability guarantees and may undergo breaking changes even during non-breaking compiler releases.

Furthermore, whether a contract has been compiled with experimental mode enabled is now permanently recorded within both JSON and CBOR metadata. The CBOR experimental field, which previously indicated only experimental source-level pragmas, has been broadened to encompass the entire experimental compilation context. This improvement also closes a known architectural gap wherein targeting an unreleased Ethereum Virtual Machine version previously generated experimental bytecode without flipping the corresponding flag.

Experimental SSA CFG Code Generator

Solidity v0.8.35 delivers an experimental new EVM backend for the intermediate representation pipeline. This alternative code generator produces bytecode directly from a program’s static single-assignment form control-flow graphs—referred to as SSA CFGs, generated on a per-function basis—complete with a precomputed stack layout that the backend subsequently shuffles the EVM stack to match.

The rationale behind this major engineering effort centers on two persistent challenges within the IR pipeline: long compilation times and the frustrating "stack-too-deep" errors that plague complex contract development. According to recent developer surveys conducted within the community, stack-too-deep errors remain the most frequently reported recurring hurdle for smart contract engineers. Furthermore, compilation via the IR pipeline has historically been measurably slower than the legacy evmasm pipeline.

The traditional Yul-to-EVM code transformation relies heavily on heuristics that often struggle when processing deeply nested expressions and intricate control flow, contributing directly to extended compilation durations. Transitioning toward an SSA-based backend provides a significantly stronger structural foundation for intelligent stack scheduling and overall compilation performance, representing the primary long-term solution for these issues.

Developers wishing to experiment with this new backend can activate it by passing --experimental --via-ssa-cfg on the command line, or by configuring settings.experimental: true alongside settings.viaSSACFG: true in Standard JSON configurations. Both configurations automatically imply --via-ir.

The development team notes that this is an early experimental rollout. Although the code generator is continuously exercised against the full external-contract semantic test suite on every pull request, it is not yet the default option for --via-ir. Promoting it to standard status will require extensive review, rigorous fuzzing, and likely an independent external security audit. In accordance with the newly established experimental policy, only major structural modifications affecting the SSA CFG code generator will be explicitly documented in future changelogs.

Deprecation Warnings for Upcoming 0.9.0 Keywords

Continuing the systematic deprecation trajectory initiated in version 0.8.31, Solidity v0.8.35 introduces warning messages for a specific set of identifiers that are scheduled to be promoted to reserved keywords in the upcoming major version 0.9.0. While the previous deprecation phase focused primarily on the removal of obsolete language features, this batch centers entirely on claiming specific names to prevent future namespace conflicts.

Solidity declarations utilizing identifiers such as at, error, layout, leave, super, this, or transient will now emit formal compiler warnings. Within Yul contexts—including both standalone Yul and inline assembly blocks—leave is transitioning into a reserved Yul keyword, while terms like basefee, blobbasefee, blobhash, clz, mcopy, memoryguard, prevrandao, tload, and tstore are becoming reserved Yul identifiers. The latter group consists of established Yul builtins that the language maintains as reserved; the accumulation of exceptions reflects the extended duration of the 0.8.x release cycle, as the project’s strict backwards-compatibility commitments hold these keyword promotions until version 0.9.0.

These notifications are issued strictly as warnings rather than hard compilation errors. Existing codebases will continue to compile successfully, granting development teams a comfortable transition window to refactor and rename affected declarations before version 0.9.0 officially converts these warnings into breaking errors.

Revert Strings Strip and Custom Errors

An important bug fix in version 0.8.35 resolves a discrepancy involving the gas-saving compiler option --revert-strings strip—represented as revertStrings: "strip" in Standard JSON configurations. This optimization flag reduces overall bytecode size by stripping out revert reason strings while ensuring that transactions still revert when conditions fail. The underlying design assumption was that revert reason strings primarily served as human-readable diagnostic messages for end users rather than structured data relied upon by interacting smart contracts.

The introduction of custom errors within require statements—such as require(condition, CustomError(...)), introduced in Solidity 0.8.26—introduced a structural complication because custom errors explicitly encode structured data. Prior to version 0.8.35, the IR pipeline (--via-ir) incorrectly stripped away the custom error arguments of require statements alongside standard text strings. Consequently, a failing require statement reverted with completely empty error data instead of properly transmitting the encoded custom error payload, creating an inconsistency with the legacy evmasm pipeline.

The development team chose to resolve this behavioral discrepancy by ensuring that custom errors are preserved, correcting the bug across the IR pipeline. This fix specifically affects require() statements rather than plain revert statements utilizing custom errors, and applies exclusively to the IR pipeline.

Ethdebug Output Reorganization

Solidity v0.8.35 reorganizes the output selection for the ethdebug format to establish a more granular structure that aligns consistently with how other compiler outputs are exposed. The former flags --ethdebug and --ethdebug-runtime have been deprecated and replaced by four distinct options: --ethdebug-resources, --ethdebug-compilation, --ethdebug-program, and --ethdebug-program-runtime, accompanied by equivalent keys within Standard JSON configurations.

Crucially, generating ethdebug outputs no longer forces a full binary compilation process. Ethdebug remains classified as an experimental feature and is now formally gated behind the new --experimental flag alongside other experimental components.

How to Install and Upgrade

Developers looking to upgrade their toolchains to the latest Solidity compiler release can consult the official installation instructions available in the language documentation. Pre-compiled binaries and release packages can be obtained directly from the official project repository on GitHub under release tag v0.8.35.

Teams opting to build the compiler directly from source code are strongly advised to avoid utilizing the raw source archives automatically generated by GitHub. Instead, developers should download the dedicated solidity_0.8.35.tar.gz source tarball or explicitly check out the v0.8.35 tag using git to ensure proper version integrity.

The core development team extends its appreciation to all community contributors, testers, and protocol developers whose ongoing feedback and code contributions helped make the v0.8.35 release possible.

Leave a Reply

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