Home
Optimistic Rollup
Arbitrum One
Arbitrum Nova
OP Mainnet
Base
opBNB
Fuel v1
Mantle
ZK Rollup
Starknet
zkSync Era
zkSync Lite
Linea
Polygon zkEVM
Scroll
Taiko
Kakarot
RaaS Framework
OP Stack
Arbitrum Orbit
ZK Stack
Celestia
Avail
Sovereign
Stackr
No Code Deployment
Eclipse
Opside
AltLayer
Cartesi
Caldera
Conduit
Shared Sequencer
Flashbots Suave
EigenLayer
Espresso
Dymension
Saga
OmniChain
LayerZero
Axelar
Arbitrum Orbit Ecosystem
An overview of the Projects in the Arbitrum Orbit ecosystem.
Description
Arbitrum Orbit refers to the ability for anyone to permissionlessly deploy Layer3 chains on top of Arbitrum Layer2 chains, Arbitrum Nitro is the current tech stack.
- Launch Layer3 Rollup chains (like Arbitrum One)
- Launch Layer3 AnyTrust chains (like Arbitrum Nova)
- Build and customize an Layer3 with the Arbitrum Nitro core for application-specific needs.
While Layer3 chains can deploy permissionlessly, launching a Layer2 chain on Ethereum will require submitting a proposal to the Arbitrum DAO.
State Validation
- Fault Proof
Multi-round Interactive Proving
Data Availability
- Arbitrum Rollup Chain (like Arbitrum One)
- On chain Ethereum DA
- Arbitrum AnyTrust Chain (like Arbitrum Nova)
- External Data Availability Committee (DAC)
- DACert
Funds can be lost if the external data becomes unavailable (CRITICAL).
Users can be censored if the committee restricts their access to the external data.
AnyTrust gives the sequencer two ways to post a data block on L1: it can post the full data, or it can post a DACert proving availability of the data. The L1 inbox contract will reject any DACert that uses an invalid Keyset; the other aspects of DACert validity are checked by L2 code.
Upgradeability
- Security Council - Multisig Manage
There is a 13 days delay for upgrades initiated by the DAO that can be canceled by the 9/12 Security Council multisig. This multisig can also upgrade with no delay.
Operator
- Single Sequencer (existing)
- Censorship Resistance Users can force any transaction: Allows the users to circumvent censorship by interacting with the smart contract directly.
- Sequencer Failure: Transact using Layer1 If the primary sequencer goes down, the user is able to submit a transaction through Layer1 and force its inclusion on Layer2.
MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.
Environment
- Ethereum VM
- Stylus - WASM