What Is Arbitrum Orbit? Building Custom L3 Chains

Arbitrum Orbit is a framework that lets developers launch their own blockchain — either an L2 settling directly to Ethereum or an L3 settling to Arbitrum One or Arbitrum Nova — using the same technology stack Arbitrum itself runs on. It essentially turns "launch your own rollup" from a research project into a configurable product.

The basic idea: settlement layers stacked on each other

Ethereum is the base layer, or L1. Layer-2 rollups like Arbitrum One post transaction data and proofs back to Ethereum, inheriting its security while executing transactions more cheaply off-chain. An L3, sometimes called an "orbit chain" or "appchain," takes this one step further: it settles to an L2 instead of directly to L1.

This might sound like it just adds a layer of indirection, but the motivation is specialization. A project can run its own chain with custom gas tokens, custom fee markets, tailored throughput, or privacy features, while still ultimately relying on Ethereum's security through the L2 it settles to.

What you get by building on Orbit

• Dedicated blockspace: Your application isn't competing with unrelated dApps for gas on a shared chain.
• Custom gas token: Some Orbit chains let you pay fees in the project's own token rather than ETH.
• Choice of technology: Orbit chains can be configured as optimistic rollups (Arbitrum's core tech) or validity-proof-based validium/AnyTrust chains, trading off data availability cost against security guarantees.
• Permissioned or permissionless: Teams can restrict who can transact or keep the chain fully open, depending on their use case.

The trade-offs of going custom

Running your own chain isn't free of downsides. Liquidity that would otherwise sit on a large, established chain gets fragmented across your app-specific chain instead. Bridging assets in and out adds friction and, historically, has been one of the largest sources of exploited losses in crypto — see our overview of crypto bridges for why bridge design matters so much.

There's also a decentralization question. Many Orbit (and other L2/L3) chains launch with a single sequencer operated by the founding team, meaning that team can, in principle, reorder or delay transactions. This is common across the L2 landscape today, not unique to Orbit, but it's a real centralization vector worth checking before committing significant funds.

AnyTrust vs. full rollup mode

Configuration	Data availability	Cost	Security assumption
Full rollup (Arbitrum-style)	All data posted to the parent chain	Higher	Inherits parent chain's security fully
AnyTrust / validium mode	Data held by a committee, not fully on-chain	Lower	Trusts a data availability committee

Orbit chains can choose either configuration depending on whether the project prioritizes minimal trust assumptions or lower operating costs.

When Orbit makes sense

Orbit is best suited to applications with high, predictable transaction volume that would otherwise be expensive or congested on a shared chain — gaming platforms, specific DeFi protocols processing many small trades, or enterprise use cases needing custom compliance rules. For most end users and smaller projects, using an existing chain like Arbitrum One directly remains simpler and benefits from deeper existing liquidity and tooling.

If you're evaluating whether to build on an existing L2 or launch your own Orbit chain, our guide on choosing the right L2 for your dApp walks through the relevant trade-offs in more depth, including fee models and ecosystem fit.

How Orbit chains actually get built

In practice, launching an Orbit chain involves configuring a set of parameters rather than writing rollup software from scratch: choosing the settlement layer (Ethereum directly for an L2, or Arbitrum One/Nova for an L3), selecting the data availability mode, setting the native gas token, and deploying the standard bridge and core contracts that Arbitrum provides as part of the framework. Teams can further customize things like precompiles, custom gas metering, or permissioning rules for who can submit transactions, depending on their specific application's needs.

This configurability is the whole point of Orbit as a product: a gaming studio might want extremely cheap, high-throughput transactions with a permissioned validator set for a specific title, while a DeFi protocol might want an open, permissionless L3 with its governance token as the native gas asset. Both are achievable within the same underlying framework, just configured differently.

Comparing Orbit to other "launch your own chain" frameworks

Arbitrum Orbit isn't the only option in this space — Optimism's OP Stack and Polygon's CDK offer similar "launch a custom chain" capabilities built around their respective technology stacks. The core trade-offs discussed above — dedicated blockspace and customization versus fragmented liquidity and sequencer centralization — apply broadly across all of these frameworks, not just Orbit specifically. The meaningful differences tend to come down to the underlying rollup technology (optimistic versus ZK), the specific ecosystem's tooling and liquidity, and which parent chain the new chain ultimately settles to.

Bottom line

Arbitrum Orbit lowers the technical barrier to launching a custom L2 or L3, letting teams get dedicated blockspace and configurable fee models while still settling back to Arbitrum or Ethereum. The trade-off is fragmented liquidity, added bridging risk, and — in most current deployments — a centralized sequencer. It's a strong fit for high-volume, specialized applications, but not a default choice for general-purpose use, where an established chain's liquidity and battle-tested infrastructure usually win out.