Arbitrum chain information

Arbitrum public RPC endpoints

caution

• Unlike the RPC Urls, the Sequencer endpoints only support eth_sendRawTransaction and eth_sendRawTransactionConditional calls.
• Arbitrum public RPCs do not provide Websocket support.
• IPv6 is not supported.

This section provides an overview of the available public RPC endpoints for different Arbitrum chains and necessary details to interact with them.

Name	RPC Url(s)	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

More RPC endpoints

More Arbitrum chain RPC endpoints can be found in Chain Connect: Arbitrum One and Arbitrum Nova.

Alternatively, to interact with public Arbitrum chains, you can rely on many of the same popular node providers that you are already using on Ethereum:

Third-party RPC providers

WANT TO BE LISTED HERE?

Complete this form , if you'd like to see your project added to this list (and the Arbitrum portal).

Need support for Nova 3rd party tooling?

Complete this form to submit a support request.

Provider	Arb One?	Arb Nova?	Arb 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	✅	✅	✅	✅
GetBlock	✅			✅
Infura	✅		✅	✅	Enabled on request
Lava	✅	✅
Moralis	✅
Nirvana Labs	✅	✅	✅	✅
NodeReal	✅	✅
NOWNodes	✅
Pocket Network	✅
PublicNode	✅	✅	✅
Quicknode	✅	✅	✅	✅	Testnet supported in free tier
Tenderly	✅		✅	✅	Testnet supported in free tier
Unifra	✅
Validation Cloud	✅		✅	✅	Testnet supported in free tier

Sequencer endpoint behavior

Arbitrum One exposes two public endpoints with different roles, shown below: a general-purpose public RPC URL, and a direct sequencer endpoint that accepts only eth_sendRawTransaction and eth_sendRawTransactionConditional. The table below summarizes how they differ in 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. Any application that depends on availability should use a third-party node provider or run its 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.	Exposes the defined queueing and timeout behavior described below, but it is still a best-effort public endpoint with no formal SLA.

Latency and timeout behavior

Under nominal load, transactions submitted to the sequencer endpoint are accepted in well under a second. Internally, the sequencer places submissions into a bounded in-memory queue (default capacity 1024). The queue timeout (default 12 seconds) bounds how long a submitted transaction may remain pending in the sequencer's background queue before being picked up or rejected; it does not provide a formal end-to-end inclusion latency guarantee. If the transaction is not picked up within that window, eth_sendRawTransaction returns context deadline exceeded, and the transaction was not accepted—it is safe to retry.

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—context deadline exceeded and network/connection errors are safe to retry with backoff. Do not retry terminal errors such as nonce too low or contract reverts.

Monitoring and alerting

A successful eth_sendRawTransaction response means the sequencer has already sequenced your transaction into an L2 block—the call blocks until the block is created and returns only then, not merely when the transaction is enqueued. Treat this as the sequencer's soft confirmation that your transaction has been ordered and executed. It does not by itself mean the transaction has been 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 submission calls that return errors or exceed your expected latency ceiling rather than assuming a pending-but-unconfirmed state.

Chain parameters

Param	Description	Arbitrum One	Arbitrum Nova	Arb Sepolia
Dispute window	Time for assertions to get confirmed during which validators can issue a challenge	45818 blocks (~ 6.4 days )	45818 blocks (~ 6.4 days)	20 blocks (~ 4.0 minutes)
Minimum bond amount	Amount of funds required for a validator to propose assertion on the parent chain	3600 ETH	1 ETH	1 Sepolia ETH
Force-include period	Period after which a delayed message can be included into the inbox without any action from the Sequencer	5760 blocks / 24 hours	5760 blocks / 24 hours	5760 blocks / 24 hours
Gas target	Target gas/sec, over which the congestion mechanism activates	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 amount of gas that all the transactions inside a block are allowed to consume	32,000,000	32,000,000	32,000,000

Current gas targets

Gas target (Mgas/s)	Adjustment window (seconds)
60	9
41	52
29	329
20	2,105
14	13,485
10	86,400

To learn more about the gas target, refer to the Gas and fees deep-dive.

To determine how to configure the gas target for your chain, refer to the Dynamic pricing for Arbitrum chains page, to calculate the values for your chain, refer to the How to calculate the values for your chain section on the same page.

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	0x042B...0Cf4
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

Nova-specific tooling

Effective January 31, 2026 (23:59 UTC), the following third-party tools will no longer be supported for Arbitrum Nova environments:

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

This change does not impact any other Arbitrum technology, such as Arbitrum One or other Arbitrum chains.

A non-exhaustive list of alternatives to the outgoing tools has been compiled. While the capabilities may not be 1-to-1, suitable replacements are provided that cover the core competencies required.

Service	Alternate provider
RPC	- Allnodes - Quicknode - More alternatives can be found at chainlist.org
Block Explorer	- Blockscout
Webhooks	- Quicknode

Below, an FAQ can be found to address any further questions or concerns Nova builders and users may have. Additional questions can be submitted here.

FAQ

What exactly is changing on January 31, 2026?

The following third-party tools will no longer be supprted for Arbitrum Nova:

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

These changes apply only to Nova-specific environments and do not affect Arbitrum One or other Arbitrum chains.

Does this impact my funds or assets on Arbitrum Nova?

User funds and onchain assets on Arbitrum Nova are not affected. All assets on Arbitrum Nova remain accessible and withdrawable regardless of the tooling change.

Will existing Nova applications continue to function?

Yes, continued building is supported, provided that a migration away from deprecated tooling is completed and infrastructure dependencies are updated as required. Reliance on the aforementioned services should be reviewed, and a transition to alternative providers should be completed before January 31, 2026.

Who can I contact if there are issues or questions I need addressed?

Please reach out with additional questions here.