Skip to main content

ArbOS software releases: Overview

info

This document provides an overview of Nitro node software releases that upgrade ArbOS. Visit the Nitro Github repository for a detailed index of Nitro releases.

Arbitrum chains are powered by Arbitrum nodes running the Nitro software stack. The Nitro software stack includes ArbOS, the Layer 2 EVM hypervisor that facilitates the execution environment of an Arbitrum chain.

Although new Nitro releases are shipped regularly, only a subset of Nitro releases carry ArbOS upgrades. These special Nitro releases are significant because ArbOS upgrades are Arbitrum's equivalent to a "hard fork" - an upgrade that alters a node's ability to produce valid Arbitrum blocks. This is why validator nodes supporting a public Arbitrum chain (One, Nova) must update Nitro whenever a new ArbOS version is released and voted for adoption by the ArbitrumDAO.

Note that every Nitro release is backwards compatible. In other words, the latest version of Nitro will support all previous ArbOS releases. This means that your validator's Nitro version must be greater than or equal to the version that includes the latest ArbOS upgrade.

How often should I be upgrading my ArbOS version?

It is strongly recommended to keep your Nitro's node software up-to-date as best you can to ensure you are benefting from the latest improvements to the Arbitrum technology stack. ArbOS version bumps are especially important because these upgrades change how Arbitrum nodes produce and validate assertions on a rollup's state.

ArbOS upgrades are carried out by the chain's owner; in the case of Arbitrum One and Nova, the owner is the Arbitrum DAO and so an upgrade will require a governance proposal and vote to pass to complete the upgrade. This is an example of a Nitro release that contains an ArbOS version bump, specifically to ArbOS 11.

Visit Inside Arbitrum Nitro to learn more about Nitro's architecture; more information about ArbOS software releases is available on the Arbitrum DAO forum.

List of available ArbOS releases​

Naming and numbering scheme​

Beginning with ArbOS 20, ArbOS releases use the name of planetary moons in our solar system, ascending in alphabetical order (i.e. the next ArbOS upgrade after ArbOS 20 "Atlas" will be a planetary moon that begins with the letter "B").

The number used to denote each upgrade will increment by 10, starting from ArbOS 20 (i.e., the next ArbOS upgrade after ArbOS 20 will be ArbOS 31). This was done because there are teams who have customized their Orbit chain's behavior or precompiles and who may wish to use ArbOS's naming schema between official ArbOS version bumps (e.g. ArbOS 12 could be the name of a customized version of ArbOS for a project's L3 Orbit chain).

Note that there may be cases where special optimizations or critical fixes are needed for a specific family of ArbOS releases that will diverge from the standard numbering scheme described above. For example, ArbOS 32 will be the canonical ArbOS version for the “Bianca” family of releases. Node operators and chain owners are expected to upgrade from ArbOS 20 directly to ArbOS 32 (instead of ArbOS 30 or ArbOS 31).

Network status​

To view the status and timeline of network upgrades on Arbitrum One and Nova, please visit this page.

Expectations for Orbit chain owners​

For Orbit chain owners or maintainers: it is important to note that before upgrading your Orbit chain(s) to the newest ArbOS release, we strongly encourage waiting at least 2 weeks after the new ArbOS release has been activated on Arbitrum One and Nova before attempting the upgrade yourself. The rationale behind this short time buffer is to allow the Offchain Labs team to address any upgrade issues or stability concerns that may arise with the initial rollout so that we can minimize the chances of your chain(s) hitting the same or similar issues and to maximize the likelihood of an eventual smooth, seamless upgrade. Arbitrum Orbit chains, as always, can pick up new features & enable new customizations as they see fit. ArbOs 31 "Bianca" which unlocks Stylus for use, is no exception to this rule. However, we believe this delay ensures consistent UX across all Orbit chain owners and managers for these critical upgrades.

Note that enabling an ArbOS upgrade is not as simple as bumping your chain’s Nitro node version. Instead, there are other steps required that are outlined in our docs on How to upgrade ArbOS on your Orbit chain. Please be sure to follow them and let us know if you encounter any issues.

Stay up to date​

To stay up to date with proposals, timelines, and statuses of network upgrades to Arbitrum One and Nova: