Arbitrum chain information
Public RPC endpoints, chain parameters, faucets, and contract addresses for Arbitrum One, Arbitrum Nova, and Arbitrum Sepolia.
Arbitrum public RPC endpoints
Use these public RPC endpoints to connect to Arbitrum One, Arbitrum Nova, and Arbitrum Sepolia.
- Unlike the RPC URLs, the endpoints support only
eth_sendRawTransactionandeth_sendRawTransactionConditionalcalls. - The Arbitrum public RPC endpoints do not support WebSocket.
- The Arbitrum public RPC endpoints do not support IPv6.
| Name | RPC URL | Chain ID | Block explorer | Underlying chain | Tech stack | Sequencer feed URL | Sequencer endpoint |
|---|---|---|---|---|---|---|---|
| Arbitrum One | https://arb1.arbitrum.io/rpc | 42161 | Arbiscan, Blockscout | Ethereum | Nitro (Rollup) | wss://arb1-feed.arbitrum.io/feed | https://arb1-sequencer.arbitrum.io/rpc |
| Arbitrum Nova | https://nova.arbitrum.io/rpc | 42170 | Blockscout | Ethereum | Nitro (AnyTrust) | wss://nova-feed.arbitrum.io/feed | https://nova-sequencer.arbitrum.io/rpc |
| Arbitrum Sepolia (Testnet) | https://sepolia-rollup.arbitrum.io/rpc | 421614 | Arbiscan, Blockscout | Sepolia | Nitro (Rollup) | wss://sepolia-rollup.arbitrum.io/feed | https://sepolia-rollup-sequencer.arbitrum.io/rpc |
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.
To add your project to this list and to the Arbitrum portal, complete the portal application form.
To request support for a Nova third-party tool, complete the Nova support form.
| Provider | Arbitrum One | Arbitrum Nova | Arbitrum Sepolia | WebSocket | Stylus 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
| Endpoint | Purpose | Operational 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
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_sendRawTransactionreturns after the sequencer includes the transaction in a block.- On queue timeout,
eth_sendRawTransactionreturnscontext 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.
- Queue timeout: the sequencer drops the transaction.
eth_sendRawTransactionhas 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.
Recommended fallback patterns
- 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
statusset to0x0. - 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
| Parameter | Description | Arbitrum One | Arbitrum Nova | Arbitrum Sepolia |
|---|---|---|---|---|
| Dispute window | Period in which a can challenge an before the assertion is confirmed | 45818 blocks (about 6.4 days) | 45818 blocks (about 6.4 days) | 20 blocks (about 4.0 minutes) |
| Minimum bond amount | Funds that a proposer must bond to propose an assertion on the | 3600 ETH | 1 ETH | 1 Sepolia ETH |
| Force-include period | Time after which a delayed message can enter the inbox without the | 7200 blocks / 24 hours | 7200 blocks / 24 hours | 5760 blocks / 24 hours |
| Gas target | Gas per second above which the congestion mechanism starts | See child chain gas fees | See child chain gas fees | See child chain gas fees |
| Gas price floor | Minimum gas price | 0.02 gwei | 0.02 gwei | 0.2 gwei |
| Block gas limit | Maximum total gas that the transactions in one block can use | 32,000,000 | 32,000,000 | 32,000,000 |
Current gas targets
Arbitrum One
| Gas target (Mgas/s) | Adjustment window (seconds) |
|---|---|
| 60 | 9 |
| 41 | 52 |
| 29 | 329 |
| 20 | 2,105 |
| 14 | 13,485 |
| 10 | 86,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) |
|---|---|
| 60 | 9 |
| 41 | 52 |
| 29 | 329 |
| 20 | 2,105 |
| 14 | 13,485 |
| 10 | 86,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
| Name | Network | Tokens |
|---|---|---|
| PK910 PoW Faucet | Sepolia | Ethereum Sepolia |
| Faucet aggregator | Sepolia | Ethereum Sepolia, Arb Sepolia |
| Alchemy’s Sepolia Faucet | Sepolia | Ethereum Sepolia, Arb Sepolia |
| Infura's Sepolia Faucet | Sepolia | Ethereum Sepolia |
| ethfaucet.com | Sepolia | Arb 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)
| Arbitrum One | Arbitrum Nova | Arbitrum Sepolia | |
|---|---|---|---|
| Rollup | 0x4DCe...Cfc0 | 0xE7E8...B7Bd | 0xd808...81C8 |
| Sequencer Inbox | 0x1c47...82B6 | 0x211E...c21b | 0x6c97...be0D |
| CoreProxyAdmin | 0x5547...2dbD | 0x71D7...7148 | 0x1ed7...0686 |
Cross-chain messaging contracts
The following contracts are deployed on Ethereum (L1)
| Arbitrum One | Arbitrum Nova | Arbitrum Sepolia | |
|---|---|---|---|
| Delayed Inbox | 0x4Dbd...AB3f | 0xc444...3949 | 0xaAe2...ae21 |
| Bridge | 0x8315...ed3a | 0xC1Eb...76Bd | 0x38f9...33a9 |
| Outbox | 0x0B98...4840 | 0xD4B8...cc58 | 0x65f0...B78F |
| Classic Outbox*** | 0x7607...1A40 0x667e...337a |
***Migrated Network Only
Fraud proof contracts
The following contracts are deployed on Ethereum (L1)
| Arbitrum One | Arbitrum Nova | Arbitrum Sepolia | |
|---|---|---|---|
| ChallengeManager | 0xA556...9fB0 | 0xFE66...A688 | 0xC60b...8B4C |
| OneStepProver0 | 0x35FB...F731 | 0x35FB...F731 | 0x3Fe7...1377 |
| OneStepProverMemory | 0xe0ba...C48b | 0xe0ba...C48b | 0x6268...ec2d |
| OneStepProverMath | 0xaB95...F921 | 0xaB95...F921 | 0x42f5...e8Fa |
| OneStepProverHostIo | 0xa07c...71Cf | 0xa07c...71Cf | 0xdB2c...C165 |
| OneStepProofEntry | 0x4397...42d6 | 0x4397...42d6 | 0xB9cf...AE80 |
Token bridge smart contracts
Core contracts
The following contracts are deployed on Ethereum (L1)
| Arbitrum One | Arbitrum Nova | Arbitrum Sepolia | |
|---|---|---|---|
| L1 Gateway Router | 0x72Ce...31ef | 0xC840...cD48 | 0xcE18...8264 |
| L1 ERC20 Gateway | 0xa3A7...0EeC | 0xB253...21bf | 0x902b...3aFF |
| L1 Arb-Custom Gateway | 0xcEe2...180d | 0x2312...232f | 0xba2F...40F3 |
| L1 Weth Gateway | 0xd920...e2db | 0xE4E2...0BaE | 0xA8aD...0e1E |
| L1 Weth | 0xC02a...6Cc2 | 0xC02a...6Cc2 | 0x7b79...E7f9 |
| L1 Proxy Admin | 0x9aD4...0aDa | 0xa8f7...e560 | 0xDBFC...44b0 |
The following contracts are deployed on the corresponding L2 chain
| Arbitrum One | Arbitrum Nova | Arbitrum Sepolia | |
|---|---|---|---|
| L2 Gateway Router | 0x5288...F933 | 0x2190...DFa8 | 0x9fDD...43C7 |
| L2 ERC20 Gateway | 0x09e9...1EEe | 0xcF9b...9257 | 0x6e24...b502 |
| L2 Arb-Custom Gateway | 0x0967...5562 | 0xbf54...51F4 | 0x8Ca1...42C5 |
| L2 Weth Gateway | 0x6c41...623B | 0x7626...D9eD | 0xCFB1...556D |
| L2 Weth | 0x82aF...Bab1 | 0x722E...5365 | 0x980B...7c73 |
| L2 Proxy Admin | 0xd570...2a86 | 0xada7...d92C | 0x715D...5FdF |
Precompiles
The following precompiles are deployed on every L2 chain and always have the same address
| Arbitrum One | Arbitrum Nova | Arbitrum Sepolia | |
|---|---|---|---|
| ArbAddressTable | 0x0000...0066 | 0x0000...0066 | 0x0000...0066 |
| ArbAggregator | 0x0000...006D | 0x0000...006D | 0x0000...006D |
| ArbFunctionTable | 0x0000...0068 | 0x0000...0068 | 0x0000...0068 |
| ArbGasInfo | 0x0000...006C | 0x0000...006C | 0x0000...006C |
| ArbInfo | 0x0000...0065 | 0x0000...0065 | 0x0000...0065 |
| ArbOwner | 0x0000...0070 | 0x0000...0070 | 0x0000...0070 |
| ArbOwnerPublic | 0x0000...006b | 0x0000...006b | 0x0000...006b |
| ArbRetryableTx | 0x0000...006E | 0x0000...006E | 0x0000...006E |
| ArbStatistics | 0x0000...006F | 0x0000...006F | 0x0000...006F |
| ArbSys | 0x0000...0064 | 0x0000...0064 | 0x0000...0064 |
| ArbWasm | 0x0000...0071 | 0x0000...0071 | 0x0000...0071 |
| ArbWasmCache | 0x0000...0072 | 0x0000...0072 | 0x0000...0072 |
| NodeInterface | 0x0000...00C8 | 0x0000...00C8 | 0x0000...00C8 |
Misc
The following contracts are deployed on the corresponding L2 chain
| Function | Arbitrum One | Arbitrum Nova | Arbitrum Sepolia |
|---|---|---|---|
| L2 Multicall | 0x842e...4EB2 | 0x5e1e...cB86 | 0xA115...d092 |
ResourceConstraintManager | 0x8F59...823a | 0x653e...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 One | Arbitrum Nova | Arbitrum Sepolia | |
|---|---|---|---|
RollupCreator | 0xB90e...eB8b | 0xF916...60F4 | 0x5F45...16cF |
TokenBridgeCreator | 0x2f56...000e | 0x8B9D...8c14 | 0x56C4...bD8E |
Nova-specific tooling
Since January 31, 2026 (23:59 UTC), these third-party tools no longer support :
- 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.
| Service | Alternative 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:
- 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?
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?