Summary
Arc Testnet's actual chain ID is 5042002 (0x4cef52). However, some tooling references, third-party integrations, and older documentation list 1516 as the Arc Testnet chain ID. This inconsistency causes wallet configuration failures and confusing debugging sessions.
Reproduction
curl -X POST https://rpc.testnet.arc.network \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
# Returns: {"result":"0x4cef52"} = 5042002
The actual chain ID returned by the node is unambiguously 5042002. Any documentation or tooling listing 1516 is incorrect.
Observed Instances
- Some third-party chain registry entries reference
1516 for Arc
- Some community-written guides and tutorials use
1516
- MetaMask users who follow outdated guides fail to connect because wallet rejects the wrong chain ID
Impact
- Wallet connection failures for developers following older guides
- Time wasted debugging what appears to be an RPC connectivity issue but is actually a chain ID mismatch
- Inconsistent network entries in users' MetaMask installations
Suggested Fix
- Ensure all official documentation consistently uses
5042002 / 0x4cef52
- Add a prominent note in the network configuration docs clarifying that
1516 is incorrect
- Submit a PR to ethereum-lists/chains to ensure the canonical chain registry has the correct ID — this is what most wallets and tooling query automatically
Correct Configuration
Network name: Arc Testnet
Chain ID: 5042002 (0x4cef52)
RPC URL: https://rpc.testnet.arc.network
Currency symbol: USDC
Block explorer: https://testnet.arcscan.app
Summary
Arc Testnet's actual chain ID is
5042002(0x4cef52). However, some tooling references, third-party integrations, and older documentation list1516as the Arc Testnet chain ID. This inconsistency causes wallet configuration failures and confusing debugging sessions.Reproduction
The actual chain ID returned by the node is unambiguously
5042002. Any documentation or tooling listing1516is incorrect.Observed Instances
1516for Arc1516Impact
Suggested Fix
5042002/0x4cef521516is incorrectCorrect Configuration