Roadmap: Erigon Nitro archive on mainnet
When Erigon Nitro for Arbitrum One reaches production stability (expected in the 2026 window per ecosystem
releases), etox plans to migrate from pruned Nitro to an archive layout so debug_traceTransaction
and friends behave across full history — matching what we already deliver on Ethereum via Reth. Until then,
treat Arbitrum trace as “hot data” friendly and validate block depth in staging.
Endpoint: arb.etox.io
Authenticated requests use the same API-key-first path pattern as Ethereum. WebSocket RPC is available under
the /ws/ prefix for subscriptions that Nitro supports. Rate limits and CU weights are enforced per
key at the gateway, with Arbitrum-specific methods such as arb_getL1BlockNumber listed in our
documentation.
Why Arbitrum teams evaluate etox
- Transparent bare-metal footprint instead of anonymous shared pools
- Aligned Pro pricing ($49/mo) with published CU tables
- Honest comparison vs providers that omit Arbitrum trace — see vs Competitor 1
Related chains
Pair Arbitrum with our Ethereum archive RPC for L1 anchor reads, add Base for OP Stack traffic on the same gateway pattern, and watch Polygon as we bring that endpoint online behind the same control plane.