# Arbitrum

Arbitrum is an Ethereum Layer 2 scaling solution based on Optimistic Rollup technology, designed to address congestion and high gas fees on Ethereum. It achieves high throughput and low transaction fees by processing a large number of transactions off-chain in batches and then submitting the results to the Ethereum main chain.

Arbitrum mainly consists of the following three chains:

## - **Arbitrum One**

It is the first launched, most widely used, and mature general-purpose Layer 2 main chain. By processing transactions in batches and publishing data on Ethereum, it realizes a low-cost and high-throughput on-chain interaction experience. Meanwhile, it maintains high compatibility with Ethereum in terms of security and composability, mainly used for DeFi, NFT, and infrastructure projects.

## - **Arbitrum Nova**

The second main chain launched by the Arbitrum team, adopting the AnyTrust architecture, focuses on providing an extremely low-cost and high-throughput transaction environment. It does not fully publish data to Ethereum but uses a trusted data committee to ensure data availability, suitable for cost-sensitive application scenarios that tolerate certain trust assumptions, such as high-frequency trading applications.

## - **Arbitrum Orbit**

It is not a specific chain but a chain-building framework, allowing developers to freely build exclusive Layer 2 or Layer 3 blockchains based on the Arbitrum technology stack. Developers can set their own fee structures, governance rights, virtual machines, etc., forming "modular" and "application sovereign chains".


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gtokentool.com/en/arbitrum.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
