arbos

According to The Defiant, Arbitrum activated the ArbOS 61 Elara upgrade on August 20, adding optional protocol-level transaction filtering, priority fee support, and alternative data availability interfaces for dedicated chains, while adjusting the base fee management and expanding the Stylus contract capacity of Arbitrum One. The compliance filtering feature is turned off by default and requires the chain owner to actively configure external compliance service providers (such as TRM Labs or Chainalysis) and set rules, executing through a dual mechanism of simulated transactions and on-chain guardians.The priority fee feature is also turned off by default and requires the chain owner to enable it through pre-compilation. The collection of priority fees on Arbitrum One still requires a separate DAO vote. Elara also introduced the BaseFeeManager contract, allowing Offchain Labs to adjust the base fee within the DAO-approved range of 0.01 to 0.1 gwei, with a validity period of two years. The code size limit for Stylus contracts has been increased from 24KB to 96KB, which does not apply to Solidity contracts.

According to official news, Arbitrum has announced the activation of the ArbOS Dia upgrade. The officials stated that this is a significant update to its tech stack, introducing support for the Fusaka EIP and enhancing the overall user experience.

ChainCatcher message, Degen posted on X that the DEGEN mainnet will upgrade to ArbOS 32 on January 16, 2025, at 1:00 without any downtime.Highlights of this upgrade include faster withdrawal speeds: the Orbit chain can achieve final confirmation in about 15 minutes (a fast withdrawal feature will be enabled later); integration of Stylus: support for building contracts using Rust and WASM; and a 99% reduction in signature costs: significantly lower costs for secp256r1 verification.

ChainCatcher message, Arbitrum Developers stated that Arbitrum One, Nova, and Sepolia have completed the ArbOS 32 upgrade. Node operators need to upgrade their nodes to at least Arbitrum Nitro v3.2.0, and validator nodes need to upgrade to v3.2.1.This upgrade was coordinated with its Security Council, which approved an emergency action to address: the mispricing issue in Arbitrum Stylus that could lead to denial-of-service attacks; the issue that allows malicious contracts to cause node crashes; and the mispricing issue where Stylus contracts are overcharged due to SLOAD operations. No funds are at risk. Additionally, the team is about to release a comprehensive analysis report.

ChainCatcher message, Arbitrum Developers posted on the X platform stating that the Arbitrum Security Council is planning to take emergency action to activate ArbOS 32 in the coming days. Version v3.2.0 includes security fixes activated by the newly upgraded ArbOS 32, and the source code will be available at 10 AM Eastern Standard Time on Tuesday, after which the upgrade process will begin.Previously, Arbitrum Developers announced that Arbitrum Nitro v3.2.0 has been released, and relevant parties need to upgrade to this version as soon as possible.

ChainCatcher news, Arbitrum has proposed to activate ArbOS 31, which is planned to be implemented on the Arbitrum One and Nova networks. The current version of ArbOS used on Arbitrum One and Arbitrum Nova is ArbOS 20, and the proposal voting will start on August 1.The main upgrades of ArbOS 31 include: activating Arbitrum Stylus, supporting the development of EVM applications using programming languages such as Rust or C++; adding secp256r1 curve verification precompiles to reduce verification costs; optimizing the fee collection mechanism on Arbitrum Nova.

ChainCatcher message, Arbitrum announced that ArbOS Atlas Phase 2 is now live, and Arbitrum OnGas has been further reduced.

ChainCatcher news, Offchain Labs has submitted the ArbOS 20 Atlas AIP proposal to the Arbitrum community, with voting starting at 07:27 Beijing time on February 17 and ending at 07:28 on March 2.It is reported that this AIP proposes several improvements to Arbitrum, including the ability to publish batch L2 transactions on Ethereum in Blob form at a lower cost using EIP-4844, support for most changes included in the Ethereum Dencun upgrade, and two improvements for the batch release of Arbitrum One and Nova. The proposed ArbOS 20 Atlas upgrade will be available for adoption by any Arbitrum.

ChainCatcher news, the Arbitrum community has initiated an AIP proposal called "ArbOS 20 version," which proposes many improvements to the Arbitrum chain, including the ability to publish L2 transaction batches on L1 Ethereum in the form of blobs at a lower cost using EIP 4844. This proposal also includes support for most of the changes included in the Ethereum Dencun upgrade.It is reported that the proposed ArbOS 20 upgrade will be ready for adoption by any Arbitrum chain, involving both Arbitrum One and Nova chains, as they are managed by the Arbitrum DAO. At a higher level, the ArbOS upgrade can be seen as a hard fork of Arbitrum. The ArbOS 20 version is an upgrade based on the ArbOS 11 version that has been adopted by the Arbitrum DAO. Due to technical details allowing for better customizability of the Orbit chain, the proposal increases the version number to 20 instead of 12.

ChainCatcher message, the Arbitrum community has voted to approve the "ArbOS version 11" proposal, which is currently awaiting execution. The proposal suggests several improvements to Arbitrum, including support for the EVM Shanghai upgrade and the PUSH0 opcode, as well as various bug fixes. These improvements have been audited and are ready for adoption, involving Arbitrum Orbit, Arbitrum One, and Arbitrum Nova (the proposal pertains to the latter two), while the ArbOS upgrade can be seen as a hard fork of Arbitrum.

ChainCatcher news, the Arbitrum community has opened the "ArbOS 11 version" AIP proposal voting, which will end at 06:11 Beijing time on December 5. The current support rate is 99.8%. This proposal introduces several improvements to Arbitrum, including support for the EVM Shanghai upgrade and the PUSH0 opcode, as well as various bug fixes. These improvements have already been audited and are available for adoption by Arbitrum Orbit chains, Arbitrum One, and Arbitrum Nova, with the proposal concerning the latter two.The proposal states that the ArbOS upgrade can be considered a hard fork of Arbitrum. Specifically, since the latest version of Geth includes support for the changes made to the EVM in the Shanghai L1 upgrade, Arbitrum also needs to synchronize support to ensure there is no divergence with previous versions of the node software. Currently, the smart contract code for executing the on-chain upgrade has been audited by Trail of Bits. The version of ArbOS currently used by Arbitrum One and Arbitrum Nova is ArbOS 10.