ArbOS 61 Elara live: Stylus x4, compliance screening opt-in
Arbitrum has activated ArbOS 61 “Elara” on Aug. 20, 17:00 UTC, updating both Arbitrum One and Arbitrum Nova. The upgrade introduces a new framework for developers and operational changes for network infrastructure, including optional protocol-level transaction screening.
Key changes in ArbOS 61 Elara:
- Stylus contract capacity rises sharply: on Arbitrum One, the compressed contract code size limit increases from 24 KB to 96 KB (4x). This should reduce the need to split complex contracts into multiple deployments.
- Compliance screening is built into the protocol but remains off by default on Arbitrum One and Nova. It is intended as an opt-in tool for Orbit chain operators (Arbitrum’s customizable Layer 3 networks) that need to meet local regulatory requirements.
- For Orbit chain operators, Elara also adds customizable priority fees, plus an alternative data-availability interface and changes to base-fee administration.
- Gas-refund logic errors from earlier testing are fixed, rolling forward improvements from the prior ArbOS 51 “Dia” cycle.
Network and governance notes:
- Node operators had to upgrade to Nitro v3.11.3 or higher; running older software after activation can put nodes out of consensus.
- The ArbitrumDAO approved the ArbOS 61 Elara upgrade via constitutional governance, with ARB token holders voting. The proposal was tested on Arbitrum Sepolia starting June 29.
Overall, ArbOS 61 Elara improves developer throughput while keeping compliance tooling targeted to Orbit deployments, not mainstream Arbitrum One/Nova usage.
Neutral
The upgrade is technically meaningful (4x Stylus contract size limits, protocol improvements, and required Nitro node updates), which can be viewed as incremental positive for Arbitrum’s developer ecosystem. However, the headline “transaction screening” feature is explicitly opt-in for Orbit chain operators and remains off by default on Arbitrum One and Nova, reducing the likelihood of an immediate, broad user-impacting disruption.
Historically, Arbitrum/rollup infrastructure upgrades tend to cause short-term attention spikes around timelines and node upgrade requirements, but market impact is usually modest unless there are changes to core user flows, fees, or interoperability. Here, governance approval by ARB holders and prior testnet exposure (Sepolia starting June 29) also suggest the rollout is controlled, supporting a steadier sentiment rather than a sharp repricing.
Net: neutral—positive for long-term dev capacity, but limited direct effect on mainstream usage and near-term trading dynamics.