Home / Smart Contract Auditing / Solidity Compiler v0.8.31 Released with Fusaka EVM Support and Preparations for Breaking 0.9.0 Update

Solidity Compiler v0.8.31 Released with Fusaka EVM Support and Preparations for Breaking 0.9.0 Update

The Solidity development team has officially announced the release of the Solidity Compiler version 0.8.31. This latest iteration of the industry-standard smart contract programming language compiler introduces critical support for upcoming Ethereum Virtual Machine (EVM) capabilities tied to the Fusaka network upgrade, expands the flexibility of custom storage layout specifiers, and rolls out official support for ARM-based Linux environments. Furthermore, version 0.8.31 initiates the deprecation cycle for a primary batch of legacy features destined for permanent removal in the upcoming 0.9.0 breaking release.

Notable Features and Changes

Fusaka Support

Osaka by Default

With the Fusaka network upgrade scheduled for deployment on the Ethereum mainnet, the Solidity team has designated the osaka environment as the default target for the compiler. Developers building smart contracts will automatically compile against these latest EVM standards unless specified otherwise. As with previous updates, developers retain full control over their target environment and can select older EVM versions using the standard --evm-version command-line flag or through the settings.evmVersion configuration option.

CLZ Opcode

Version 0.8.31 officially integrates support for the Counting Leading Zeros (CLZ) opcode, as defined in EIP-7939. This specialized EVM operation efficiently counts the number of leading zero bits in a 256-bit word. While initially previewed in recent pre-releases, its stable inclusion marks a notable advancement for lower-level bit manipulation, compression algorithms, and specialized data structures.

Although the direct applications within the compiler’s native code generation remain targeted for future optimization research, the primary beneficiaries of the CLZ opcode will be decentralized application layers and core developer libraries. Established utility frameworks—such as Vectorized’s Solady and OpenZeppelin’s Math libraries—are expected to leverage the opcode heavily, potentially replacing existing software-based routines like Math.clz() with native EVM instructions to achieve greater gas efficiency.

Changes to the Release Process

Linux ARM Releases

Beginning with version 0.8.31, the Solidity project is expanding its official distribution channels to include native Linux binaries compiled for the ARM architecture. This addition serves developers utilizing ARM-based hardware as their primary workstation operating system, as well as those running compilation pipelines inside Linux containers on ARM servers via platforms like Docker.

While ARM support is not entirely new—binaries for Apple Silicon Macs have been distributed previously, and advanced users could always compile Solidity from source on Linux ARM—this release integrates those binaries directly into the official continuous integration and release infrastructure. These official binaries undergo the project’s rigorous testing suite, including deterministic build verifications to ensure that produced bytecode and metadata match identically across all supported platforms.

Introducing Pre-releases

Historically, the Solidity team maintained a strict binary release schedule split between stable full releases and nightly development builds. To bridge the gap between these milestones, the team launched a lightweight pre-release process in October with version v0.8.31-pre.1. This feedback-driven channel allows the development community to test experimental features—such as early implementations of the CLZ opcode—in a more stable environment prior to mainnet-bound compiler deployments.

Discontinuation of PPA Releases

As part of an ongoing effort to streamline maintenance and optimize distribution channels, the Solidity team is officially discontinuing the Ubuntu Personal Package Archive (PPA) as a binary distribution mechanism starting with this release. While niche distribution paths are being phased out, Docker container images will remain supported for at least one more release cycle, though their future depends on usage metrics. Developers utilizing containerized workflows should note that official container images have already migrated from DockerHub to GitHub’s container registry.

Constants in Storage Layout Specifiers

The 0.8.31 update introduces meaningful enhancements to custom storage layout specifiers, enabling developers to use constant variables directly within base slot expressions. For instance, developers can define a constant offset and apply it cleanly to a contract’s layout declaration.

The Solidity team notes that compile-time evaluation capabilities remain intentionally constrained, supporting only arithmetic expressions involving rational number literals processed in unlimited precision. Introducing finite-precision integer types through explicit type conversions, built-in functions, or ternary operators will trigger a compilation error. The developers plan to introduce specialized built-in functions in upcoming releases to ease these restrictions before developing a more comprehensive compile-time evaluation architecture.

Feature Deprecations

With the upcoming 0.9.0 release slated to remove long-standing technical debt and modernize the language, version 0.8.31 begins issuing official deprecation warnings for several features.

Removal of <address>.send() and <address>.transfer() Functions

The <address>.send() and <address>.transfer() functions were originally designed to facilitate Ether transfers while restricting the recipient’s ability to execute complex, arbitrary code. Because the EVM lacks a native mechanism to transfer funds without invoking target execution, these functions forward a hard-coded stipend of 2,300 gas—historically enough to log events or read storage, but insufficient for reentrant state modifications.

However, changes to EVM opcode gas pricing over time rendered these assumptions fragile. Modern smart contract development widely considers these methods an anti-pattern, recommending <address>.call() with an empty payload as the standard alternative. Because <address>.call() forwards unlimited gas by default, developers relying on strict gas limitations must adopt alternative defensive architectures, such as reentrancy guards utilizing transient storage or adhering strictly to the checks-effects-interactions pattern. The Solidity team highlights that a truly future-proof solution requires native EVM-level support, such as the proposed PAY opcode (EIP-5920), which could eventually manifest as an <address>.pay() method if adopted.

Removal of ABI Coder V1

ABI coder v2, which introduced robust support for structs, arbitrarily nested arrays, and enhanced input validation, has served as the default encoder since version 0.8.0. Because ABI coder v1 is fundamentally incompatible with the modern Intermediate Representation (IR) compilation pipeline, it has become entirely obsolete. Compiling with the --via-ir flag already bypasses the v1 pragma in favor of v2. Version 0.8.31 marks the formal step toward removing the legacy coder entirely.

Removal of Virtual Modifiers

Inheritance mechanics in Solidity can introduce significant complexity. Modifiers declared as virtual and overridden in derived contracts have frequently proved confusing to developers while generating intricate corner cases within the compiler architecture. Because virtual modifiers are not strictly essential for contract architecture, the team has elected to deprecate and remove them, though virtual functions can still be invoked from within standard modifiers.

Removal of Contract Comparison Operators

Historically, contract types shared a thin abstraction layer with addresses, permitting operations like inequality comparisons directly between contract instances (e.g., c < d). Over successive releases, the language has established a rigorous separation between raw addresses and distinct contract types. Version 0.8.31 introduces warnings for direct contract comparisons, moving toward a requirement for explicit type conversions to address in future releases to eliminate syntactic ambiguity.

Finally, the alternative Natspec comment mechanism for annotating memory-safe assembly blocks (/// @solidity memory-safe-assembly) is being deprecated. Because the standard assembly ("memory-safe") block syntax is now universally established across supported compiler versions, the legacy Natspec workaround will be removed alongside other non-backward-compatible elements in version 0.9.0.

How to Install and Upgrade

Developers can upgrade to Solidity v0.8.31 by referencing the official installation documentation provided by the Solidity team. Binaries and source archives are available directly through the official GitHub release page. Developers building from source are advised to use the official source tarball rather than automatically generated GitHub source archives to ensure proper build integrity and dependency tracking.

Tagged: