Arbitrum chain information

Arbitrum public RPC endpointsCopy Anchor Link

Use these public RPC endpoints to connect to Arbitrum One, Arbitrum Nova, and Arbitrum Sepolia.

Third-party RPC providersCopy Anchor Link

You can also connect to public Arbitrum chains through many of the node providers that you use on Ethereum.

Compare provider latencyCopy Anchor Link

To compare the live latency of the public Arbitrum endpoints that need no API key, use the OpenChainBench Arbitrum RPC benchmark. OpenChainBench probes each endpoint every minute from three regions. It publishes the p50, p95, and p99 latency under an open methodology and the CC BY 4.0 license.

Sequencer endpoint behaviorCopy Anchor Link

Arbitrum One has two public endpoints with different roles. The public RPC URL is for general use. The direct sequencer endpoint accepts only eth_sendRawTransaction and eth_sendRawTransactionConditional. The table compares their purpose and operational guarantees.

The two endpoints at a glanceCopy Anchor Link

Latency and timeout behaviorCopy Anchor Link

Under normal load, the sequencer endpoint accepts a transaction in less than a second. The sequencer puts each submission in a bounded in-memory queue. By default, the queue holds 1,024 transactions.

The queue timeout is 12 seconds by default. It limits how long a transaction can wait in the queue before the sequencer picks it up or rejects it. The timeout is not an end-to-end inclusion latency guarantee. If the sequencer does not pick up the transaction before the timeout, eth_sendRawTransaction returns context deadline exceeded. In that case, the sequencer did not accept the transaction, and you can safely retry it.

Recommended fallback patternsCopy Anchor Link

• Use a third-party node provider as your primary endpoint, or as a fallback when a direct sequencer submission fails.
• Retry only on transient errors. You can safely retry context deadline exceeded and network or connection errors with backoff. Do not retry terminal errors, such as nonce too low or contract reverts.

Monitoring and alertingCopy Anchor Link

A successful eth_sendRawTransaction response means that the sequencer has already put your transaction in an L2 block. The call returns only after the sequencer creates the block, not when it adds the transaction to the queue. Treat this response as the sequencer's soft confirmation: the sequencer has ordered and executed your transaction.

The response does not mean that the transaction is posted in a batch to the parent chain, or final there. If your app needs parent-chain finality, track it separately. For monitoring, alert on submission calls that return errors or take longer than your latency limit. Do not assume a pending-but-unconfirmed state.

Chain parametersCopy Anchor Link

Current gas targetsCopy Anchor Link

Arbitrum OneCopy Anchor Link

Arbitrum NovaCopy Anchor Link

Arbitrum Nova uses a single gas target of 7,000,000 gas/s (7 Mgas/s) and no adjustment windows.

Arbitrum SepoliaCopy Anchor Link

For more about the gas target, see Gas and fees deep dive.

To configure the gas target for your Arbitrum chain, see Dynamic pricing for Arbitrum chains. To calculate the values, see How to calculate the values for your chain.

Faucet listCopy Anchor Link

Arbitrum smart contract addressesCopy Anchor Link

The following information may be useful to those building on Arbitrum. We list the addresses of the smart contracts related to the protocol, the token bridge and precompiles of the different Arbitrum chains.

Protocol smart contractsCopy Anchor Link

Core contractsCopy Anchor Link

The following contracts are deployed on Ethereum (L1)

Cross-chain messaging contractsCopy Anchor Link

The following contracts are deployed on Ethereum (L1)

***Migrated Network Only

Fraud proof contractsCopy Anchor Link

The following contracts are deployed on Ethereum (L1)

Token bridge smart contractsCopy Anchor Link

Core contractsCopy Anchor Link

The following contracts are deployed on Ethereum (L1)

The following contracts are deployed on the corresponding L2 chain

PrecompilesCopy Anchor Link

The following precompiles are deployed on every L2 chain and always have the same address

MiscCopy Anchor Link

The following contracts are deployed on the corresponding L2 chain

Canonical factory contractsCopy Anchor Link

The following factory contracts are deployed on the corresponding chain and are used to deploy new Arbitrum chains (RollupCreator) and their token bridges (TokenBridgeCreator). For factory contracts on additional chains (Ethereum, Base, and testnets) and deployment instructions, see Canonical factory contracts.

Nova-specific toolingCopy Anchor Link

Since January 31, 2026 (23:59 UTC), these third-party tools no longer support Arbitrum Nova:

• Alchemy
• Nova Arbiscan (nova.arbiscan.io)
• Tenderly

This change applies only to Arbitrum Nova. It does not affect Arbitrum One or other Arbitrum chains.

The table lists some alternatives to these tools. Each alternative covers the core features, but its features can differ from the tool it replaces.

The FAQ below answers common questions from Nova builders and users. To ask another question, complete the Nova support form.

FAQCopy Anchor Link

What changed on January 31, 2026?Copy Anchor Link

These third-party tools no longer support Arbitrum Nova:

• Alchemy
• Nova Arbiscan (nova.arbiscan.io)
• Tenderly

The change applies only to Arbitrum Nova. It does not affect Arbitrum One or other Arbitrum chains.

Does this change affect my funds or assets on Arbitrum Nova?Copy Anchor Link

No. The change does not affect your funds or onchain assets on Arbitrum Nova. You can still access and withdraw all of your assets.

Do existing Nova apps still work?Copy Anchor Link

Yes, if you move off the deprecated tools and update your infrastructure dependencies. Review where your decentralized app uses these services, and move to alternative providers. The deadline for this move was January 31, 2026.

How do I get help?Copy Anchor Link

Complete the Nova support form.