> For the complete documentation index, see [llms.txt](https://yuriai.gitbook.io/yuriai-guidebook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yuriai.gitbook.io/yuriai-guidebook/background/arbitrum.md).

# Arbitrum

{% hint style="info" %}

## Arbitrum is a technology suite designed to scale Ethereum. 

{% endhint %}

Arbitrum is cheap and works fast to pass all transaction information back to the Ethereum network (the main chain).  The Ethereum blockchain only allows about 14 transactions per second, and gas fees varies depending on the congestion level of the network, and the gas fee even spikes up to hundreds of dollars during congestion. Arbitrum, on the other hand, has 40,000 TPS and a gas fee of about $0.60 per transaction. And Arbitrum fully supports Ethernet Virtual Machines (EVMs), which means developers can integrate their decentralized application Dapps directly with Arbitrum, reducing redevelopment time.

One of the biggest attractions of Arbitrum is that it is fully compatible with EVM. For developers, it is possible to quickly adapt applications from Ethereum to Arbitrum, keeping the code intact and with low migration costs. For users, it allows them to use the native protocol on Ethereum at a lower cost. As a sidechain of Ethereum, Arbitrum is as secure as Ethereum, so its security of Arbitrum is guaranteed. While security problems have occurred in the cross-chaining of Ethereum assets by major high-performance Layer 1 networks, the risk of successful hacking is greatly reduced when cross-chaining Ethereum assets to Arbitrum because of Arbitrum’s rollup and challenge period mechanisms.

Arbitrum's strong computing power is the reason why it is highly favored by the market. This allows it to maintain high-speed and stable operation. YURI AI is also dependent on the Arbitrum ecosystem.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://yuriai.gitbook.io/yuriai-guidebook/background/arbitrum.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.