Arbitrum has activated ArbOS 61, known as “Elara,” introducing a new set of tools for its Orbit chain framework. The upgrade went live on August 20, and node operators are required to update to Nitro v3.11.3.

The release combines a developer-focused change with a more politically sensitive one. Elara raises the Stylus contract size limit from 24 KB to 96 KB, while also adding an optional protocol-level compliance filtering feature aimed at certain Orbit deployments.

A broader upgrade for the Arbitrum stack

Elara reflects how Arbitrum has expanded beyond a single public layer-2 network. Alongside Arbitrum One and Nova, the ecosystem now includes Orbit, a framework that allows teams to launch custom chains using Arbitrum technology.

As that ecosystem grows, platform upgrades increasingly affect different kinds of operators: public network participants, application developers, and teams building specialized chains. Elara is positioned as part of that broader shift toward a more modular infrastructure stack.

Compliance filters are optional and limited in scope

The most closely watched part of the release is the new compliance filtering capability. According to the source material, the feature is optional, configuration-dependent, and intended for private or enterprise Orbit chain operators rather than the public Arbitrum networks.

That scope is central to how the change is being framed. The feature should not be described as censorship on Arbitrum One or Nova, because it is not presented as a blanket rule for activity on those public chains. Instead, it is a tool available to operators that may need additional controls for specific deployments.

Why the feature may split opinion

The compliance addition is likely to draw different reactions from different parts of the market. Enterprise or regulated users may regard protocol-level filtering as necessary infrastructure, particularly where chains are built for institutional use, tokenized assets, or regulated workflows.

At the same time, critics who favor open network design may object to the idea of compliance checks being embedded at the protocol level. The source notes that both views are understandable, and that the main distinction is whether such controls are imposed across public networks or selectively enabled on custom chains.

Stylus gets more room for larger contracts

Beyond the governance debate, Elara also includes a practical developer upgrade. The contract size limit for Stylus has been increased from 24 KB to 96 KB, giving builders more capacity for larger or more complex smart contracts.

That change could make it easier to support richer applications and accommodate teams working with heavier codebases. Stylus is one of Arbitrum’s main developer initiatives, designed to allow smart contract development in languages beyond Solidity, including Rust, C, and C++.

What to watch after activation

The next confirmed step after activation is operational: node operators must move to Nitro v3.11.3. Beyond that, the main question is how widely the new Orbit features are adopted.

If teams use Elara’s capabilities to launch more custom chains, the upgrade could reinforce Arbitrum’s position as a provider of Ethereum-aligned infrastructure for specialized deployments. If the compliance tooling remains a niche option, the expansion of Stylus may prove to be the more consequential part of the release.

Source: bitcoinist.com