Arbitrum Sepolia Faucet: How to Get Testnet ETH and Configure Your RPC

Quick answer: how to get Arbitrum Sepolia testnet ETH

To get testnet ETH on Arbitrum Sepolia, you need a wallet address on that network and a faucet that supports it. Most faucets ask for your address, may require a social login or minimum mainnet balance, and drip a small amount such as 0.1 ETH per day. The exact amount and cooldown depend on the faucet.

Before you claim, add Arbitrum Sepolia to your wallet so the tokens are visible and usable. The network uses chain ID 421614, the native currency is Sepolia Ether (ETH), and the block explorer is sepolia.arbiscan.io. You can use the public OnFinality RPC endpoint https://arbitrum-sepolia.api.onfinality.io/public for read and write calls during development.

• Chain ID: 421614
• Currency symbol: ETH
• Explorer: https://sepolia.arbiscan.io
• Public RPC example: https://arbitrum-sepolia.api.onfinality.io/public

When a faucet is enough and when you need a managed RPC

A faucet solves the token problem, but it does not solve the connectivity problem. If you are deploying a contract once or testing a wallet connection, a public RPC endpoint and a faucet drip are usually sufficient. If you are running automated tests, a local fork, or a backend service that polls the chain frequently, you may hit rate limits or inconsistent responses from public endpoints.

In that case, consider a managed RPC service or a dedicated node. OnFinality provides RPC API access and dedicated node infrastructure for supported networks. You can start with the public endpoint and move to a dedicated plan when your testnet workload grows or when you need more predictable access.

• Use a faucet when you only need testnet ETH for manual testing.
• Use a managed RPC when you need consistent access for scripts, CI, or backend services.
• Use a dedicated node when you need isolated resources or custom configuration.

Add Arbitrum Sepolia to MetaMask or your wallet

Most wallets let you add a custom network. Use the settings below to add Arbitrum Sepolia. After saving, switch to the network and confirm that your address shows a zero ETH balance before claiming from a faucet.

If you prefer to add the network programmatically, you can call wallet_addEthereumChain with the same parameters. The example below uses the OnFinality public endpoint.

• Network name: Arbitrum Sepolia
• New RPC URL: https://arbitrum-sepolia.api.onfinality.io/public
• Chain ID: 421614
• Currency symbol: ETH
• Block explorer URL: https://sepolia.arbiscan.io

Claim testnet ETH and verify the drip

After adding the network, copy your wallet address and paste it into a faucet that supports Arbitrum Sepolia. Some faucets require you to connect a wallet, hold a minimum balance on a mainnet, or complete a captcha. Follow the faucet's instructions and submit the request.

Once the faucet confirms, open the block explorer and search for your address. You should see an incoming transaction. If the faucet provides a transaction hash, you can track it directly. Wait for confirmation before assuming the drip failed.

• Copy the address from the wallet while it is on Arbitrum Sepolia.
• Submit the address to the faucet and complete any required steps.
• Check the explorer for the incoming transaction.
• If the faucet shows a transaction hash, paste it into the explorer search bar.

Debugging common faucet and RPC issues

If you claimed tokens but do not see them, first confirm that your wallet is on Arbitrum Sepolia and not on Ethereum Sepolia or Arbitrum One. Then check the explorer for the faucet transaction. If the transaction is pending, the network may be congested; wait and refresh. If the transaction succeeded but your balance is still zero, try switching networks or restarting your wallet.

If your wallet cannot connect to the RPC, test the endpoint with a simple curl request. A successful response returns the current block number. If the request fails, the endpoint may be temporarily unavailable or your network may be blocking it.

• Wrong network selected in wallet.
• Faucet transaction still pending.
• RPC endpoint unreachable or rate-limited.
• Wallet cache showing an outdated balance.

Example: check your balance with curl and viem

You can verify that your RPC endpoint works and that your testnet ETH arrived by querying the balance directly. The curl example below calls eth_getBalance on the OnFinality public endpoint. Replace the address with your own.

The JavaScript example uses viem to read the balance and chain ID. This is useful in scripts or CI checks.

• curl JSON-RPC request to eth_getBalance
• viem public client reading balance and chain ID

Operational checklist for testnet development

Testnet development has a few operational differences from mainnet. Faucet limits mean you should not rely on a single drip for large test suites. RPC endpoints may have different rate limits than mainnet. And testnet state can be reset or deprecated over time, so avoid hardcoding testnet addresses in production code.

Use environment variables for RPC URLs and chain IDs. Keep a fallback endpoint in case the primary one is unavailable. And document which faucet you used so teammates can reproduce your setup.

• Store RPC URLs and chain IDs in environment variables.
• Keep a fallback RPC endpoint for critical scripts.
• Do not hardcode testnet contract addresses in production.
• Record faucet sources and drip amounts for your team.

Frequently Asked Questions