Arbitrum has officially launched its ArbOS 61 “Elara” upgrade, a significant step forward in enhancing its ecosystem for both enterprise users and developers. Activated on August 20, this upgrade introduces innovative tooling for Orbit chains, including an optional protocol-level compliance filtering feature aimed specifically at enterprise deployments.
Node operators are required to update to Nitro v3.11.3 to access these new features. Among the most notable changes is the expansion of the Stylus contract size limit, which has increased from 24 KB to an impressive 96 KB. This enhancement provides developers with greater flexibility, allowing for the creation of larger and more sophisticated smart contracts.
While the compliance filter is expected to draw significant attention, it’s crucial to emphasize that this feature is “optional.” Designed primarily for private or enterprise Orbit chain operators, it is not intended to act as a form of censorship on the public Arbitrum One or Nova networks.
TL;DR
- Arbitrum activated the ArbOS 61 “Elara” upgrade.
- The upgrade adds optional compliance filters for Orbit chains.
- Stylus contract size limits expand from 24 KB to 96 KB.
Why Elara Matters
Arbitrum is evolving beyond a single L2 solution. The ecosystem now encompasses Arbitrum One, Nova, and a growing Orbit chain framework, facilitating the launch of customized chains that utilize Arbitrum technology. This evolution means that upgrades will increasingly impact not only public users but also teams developing specialized networks.
The introduction of Elara aligns perfectly with this broader vision. It offers capabilities tailored for developers and enterprise operators while further refining Arbitrum’s infrastructure stack.
For Orbit chains, the customization aspect is particularly appealing. Teams can design chains to suit specific use cases, compliance requirements, performance goals, or application environments.
Compliance Filters Will Be Debated
The optional compliance filtering feature is poised to spark debate within the community. For enterprises and regulated users, it may represent a necessary infrastructure tool. Operators managing private Orbit chains that serve institutions, tokenized assets, or regulated workflows may need these tools to fulfill legal and compliance obligations.
Conversely, crypto purists might view protocol-level filtering with skepticism. Both perspectives are valid, and the essential aspect is the feature’s scope. This functionality does not impose a blanket change to public Arbitrum One activities; it is configuration-dependent and tailored for Orbit chain operators, a distinction that is vital for users concerned about censorship.
Stylus Contract Expansion Helps Developers
The expansion of the Stylus contract size limit is another critical development. Increasing the limit from 24 KB to 96 KB provides developers with the necessary flexibility to create larger or more complex contracts, supporting richer applications and easing the migration process for teams with substantial codebases.
Stylus represents one of Arbitrum’s major developer-facing innovations. It enables smart contracts to be authored in programming languages beyond Solidity, inviting developers from Rust, C, and C++ backgrounds. By expanding the contract size, Arbitrum makes this environment more practical for a wider range of developers.
Orbit Is Becoming More Enterprise-Friendly
Elara signifies Arbitrum’s commitment to customizable infrastructure. Many enterprises require controls that public networks may not prioritize, including permissioning, compliance mechanisms, custom gas models, privacy considerations, and operational control.
Orbit chains are designed to cater to these specific needs. However, the challenge lies in striking a balance between enterprise flexibility and the open-network ethos that crypto champions.
Arbitrum’s approach empowers custom chain operators to select features without imposing uniform rules across the public ecosystem.
What Comes Next
The next critical phase will be adoption. If more teams leverage the capabilities introduced in Elara to launch Orbit chains, this upgrade could solidify Arbitrum’s position in the rollup-as-a-service and enterprise L3 markets. Conversely, if the compliance tools remain a niche offering, the enhancements for developers might take precedence over regulatory features.
Regardless, ArbOS 61 represents a noteworthy infrastructure upgrade for Arbitrum. It underscores the project’s ongoing evolution from a singular public rollup into a more comprehensive framework for custom Ethereum-aligned chains.
