Arbitrum chain information

Public RPC endpoints, chain parameters, faucets, and contract addresses for Arbitrum One, Arbitrum Nova, and Arbitrum Sepolia.

Request an update

Arbitrum public RPC endpoints

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

Warning
  • Unlike the RPC URLs, the endpoints support only eth_sendRawTransaction and eth_sendRawTransactionConditional calls.
  • The Arbitrum public RPC endpoints do not support WebSocket.
  • The Arbitrum public RPC endpoints do not support IPv6.
NameRPC URLChain IDBlock explorerUnderlying chainTech stackSequencer feed URLSequencer endpoint
Arbitrum Onehttps://arb1.arbitrum.io/rpc42161Arbiscan, BlockscoutEthereumNitro (Rollup)wss://arb1-feed.arbitrum.io/feedhttps://arb1-sequencer.arbitrum.io/rpc
Arbitrum Novahttps://nova.arbitrum.io/rpc42170BlockscoutEthereumNitro (AnyTrust)wss://nova-feed.arbitrum.io/feedhttps://nova-sequencer.arbitrum.io/rpc
Arbitrum Sepolia (Testnet)https://sepolia-rollup.arbitrum.io/rpc421614Arbiscan, BlockscoutSepoliaNitro (Rollup)wss://sepolia-rollup.arbitrum.io/feedhttps://sepolia-rollup-sequencer.arbitrum.io/rpc
More RPC endpoints

Chain Connect lists more RPC endpoints for Arbitrum One and Arbitrum Nova.

Third-party RPC providers

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

Add your project to this list

To add your project to this list and to the Arbitrum portal, complete the portal application form.

Get support for Nova third-party tools

To request support for a Nova third-party tool, complete the Nova support form.

ProviderArbitrum OneArbitrum NovaArbitrum SepoliaWebSocketStylus tracing
1RPC✅
Alchemy✅✅✅Available on paid plans
Allnodes✅✅✅
All That Node✅✅✅
Ankr✅✅Available on paid plans
BlockPi✅✅
Chainbase✅✅
Chainnodes✅
Chainstack✅✅Available on paid plans
dRPC✅✅✅✅
Dwellir✅✅✅
GetBlock✅✅
Infura✅✅✅Enabled on request
Lava✅✅
Moralis✅
Nirvana Labs✅✅✅✅
NodeReal✅✅
NOWNodes✅
Pocket Network✅
PublicNode✅✅✅
Quicknode✅✅✅✅Testnet supported in free tier
SwiftNodes✅✅
Tenderly✅✅✅Testnet supported in free tier
Unifra✅
Validation Cloud✅✅✅Testnet supported in free tier

Compare provider latency

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 behavior

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

The two endpoints at a glance

EndpointPurposeOperational guarantees
https://arb1.arbitrum.io/rpc (public RPC URL)General-purpose read/write endpoint, useful for development and low-volume reads.No uptime, latency, or rate-limit guarantees. If your decentralized app depends on availability, use a third-party node provider or run your own node.
https://arb1-sequencer.arbitrum.io/rpc (sequencer endpoint)Direct submission path to the chain's sequencer for write traffic. Accepts only eth_sendRawTransaction and eth_sendRawTransactionConditional.Has the queueing and timeout behavior described below. It is still a best-effort public endpoint with no formal service-level agreement (SLA).

Latency and timeout behavior

Rollout status

This section and the two that follow describe the new transaction submission behavior. It reaches Arbitrum Sepolia first and Arbitrum One later. Until it reaches a chain, the sequencer endpoint on that chain works the old way:

  • eth_sendRawTransaction returns after the sequencer includes the transaction in a block.
  • On queue timeout, eth_sendRawTransaction returns context deadline exceeded. The sequencer didn't accept the transaction, so you can retry it.

For details, see Transaction submission behavior.

Under nominal load, the sequencer endpoint accepts a submission in well under a second. The sequencer places each submission in a bounded in-memory queue, with a default capacity of 1024. The queue timeout, 12 seconds by default, limits how long a transaction can wait in that queue. It isn't a guarantee of end-to-end inclusion time.

When a submission hits a queue limit, eth_sendRawTransaction behaves as follows:

  • Queue full: it returns an error right away. The sequencer doesn't admit the transaction, so nothing is dropped. You can retry it.
  • Queue timeout: the sequencer drops the transaction. eth_sendRawTransaction has already returned the transaction hash, so you get no error and no receipt. The transaction is not included. Check the sender's nonce, then resubmit the same signed transaction or re-sign it with the same nonce. See Handle transactions with no receipt.
  • Use a third-party node provider as your primary endpoint, or as a fallback when a direct sequencer submission fails.
  • Retry on transient errors only. You can retry network and connection errors with backoff. Don't retry terminal errors such as nonce too low.
  • Read reverts from the receipt. A revert isn't a submission error. The receipt shows it, with status set to 0x0.
  • If a transaction has no receipt by your deadline, check the sender's nonce before you resubmit. See Handle transactions with no receipt.

Monitoring and alerting

A successful eth_sendRawTransaction response means the sequencer admitted your transaction into its queue. It does not mean the transaction is in a block. To confirm inclusion, poll eth_getTransactionReceipt. You can also send the transaction to an RPC node with eth_sendRawTransactionSync, which returns the receipt once the sequencer executes the transaction. For details, see Transaction submission behavior.

Neither response means the transaction is posted to the parent chain in a batch or finalized there. If your application needs parent-chain finality guarantees, track that separately. For monitoring, alert on these cases:

  • Submission calls that return errors or exceed your expected latency ceiling.
  • Transaction hashes that never get a receipt.

Chain parameters

ParameterDescriptionArbitrum OneArbitrum NovaArbitrum Sepolia
Dispute windowPeriod in which a can challenge an before the assertion is confirmed45818 blocks (about 6.4 days)45818 blocks (about 6.4 days)20 blocks (about 4.0 minutes)
Minimum bond amountFunds that a proposer must bond to propose an assertion on the 3600 ETH1 ETH1 Sepolia ETH
Force-include periodTime after which a delayed message can enter the inbox without the 7200 blocks / 24 hours7200 blocks / 24 hours5760 blocks / 24 hours
Gas targetGas per second above which the congestion mechanism startsSee child chain gas feesSee child chain gas feesSee child chain gas fees
Gas price floorMinimum gas price0.02 gwei0.02 gwei0.2 gwei
Block gas limitMaximum total gas that the transactions in one block can use32,000,00032,000,00032,000,000

Current gas targets

Arbitrum One

Gas target (Mgas/s)Adjustment window (seconds)
609
4152
29329
202,105
1413,485
1086,400

Arbitrum Nova

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

Arbitrum Sepolia

Gas target (Mgas/s)Adjustment window (seconds)
609
4152
29329
202,105
1413,485
1086,400

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 list

NameNetworkTokens
PK910 PoW FaucetSepoliaEthereum Sepolia
Faucet aggregatorSepoliaEthereum Sepolia, Arb Sepolia
Alchemy’s Sepolia FaucetSepoliaEthereum Sepolia, Arb Sepolia
Infura's Sepolia FaucetSepoliaEthereum Sepolia
ethfaucet.comSepoliaArb Sepolia

Arbitrum smart contract addresses

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 contracts

Core contracts

The following contracts are deployed on Ethereum (L1)

Cross-chain messaging contracts

The following contracts are deployed on Ethereum (L1)

***Migrated Network Only

Fraud proof contracts

The following contracts are deployed on Ethereum (L1)

Token bridge smart contracts

Core contracts

The following contracts are deployed on Ethereum (L1)

The following contracts are deployed on the corresponding L2 chain

Precompiles

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

Misc

The following contracts are deployed on the corresponding L2 chain

FunctionArbitrum OneArbitrum NovaArbitrum Sepolia
L2 Multicall0x842e...4EB20x5e1e...cB860xA115...d092
ResourceConstraintManager0x8F59...823a0x653e...86B7

Canonical factory contracts

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.

Arbitrum OneArbitrum NovaArbitrum Sepolia
RollupCreator0xB90e...eB8b0xF916...60F40x5F45...16cF
TokenBridgeCreator0x2f56...000e0x8B9D...8c140x56C4...bD8E

Nova-specific tooling

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

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.

ServiceAlternative provider
RPC- Allnodes
- Quicknode
- For more alternatives, see chainlist.org
Block explorer- Blockscout
Webhooks- Quicknode

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

FAQ

What changed on January 31, 2026?

These third-party tools no longer support Arbitrum Nova:

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?

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?

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?

Complete the Nova support form.

How is this guide?

On this page