Arc RPC & WebSocket
Standard Ethereum JSON-RPC against Arc, the Circle Layer 1 where gas is paid in USDC, including the chain-specific arc namespace.
- Standard Ethereum JSON-RPC methods
- eth_subscribe: newHeads · logs · pending
- The arc namespace for chain certificates
- debug and trace namespaces on request
- Shared or single-tenant deployment
- Interface
- Ethereum JSON-RPC over HTTP and WebSocket
- Subscriptions
- newHeads · logs · newPendingTransactions
- Chain ID
- 5042 (mainnet)
- Gas token
- USDC
- Execution
- Reth
- Consensus
- Malachite BFT
- Namespaces
- eth · net · web3 · txpool · debug · trace · arc
- Archive
- available
- Auth
- token, provisioned per subscription
- Rate limits
- quoted per subscription
- Free trial
- up to 24h, no card
Is WebSocket billed separately?
No. It is the same node and the same credentials, approached from the other side - RPC is you asking, WebSocket is the node telling you - so it is one subscription, not two line items. A backend polling eth_getLogs every second is doing by hand what one logs subscription does by itself, at a fraction of the request budget.
What is Arc?
A Layer 1 built by Circle for stablecoin finance - payments, foreign exchange and tokenized assets. Its distinguishing feature is that USDC is the native gas token, so a transaction is priced in the same unit as the value it moves. Execution is Reth, so it is EVM-compatible, and consensus is Malachite BFT with sub-second blocks and deterministic finality.
What is the USDC decimals trap on Arc?
The single most common integration bug on this chain. USDC wears two hats: as native gas it follows the 18-decimal convention that msg.value and eth_getBalance expect, and as an ERC-20 it keeps its usual 6 decimals in balanceOf. The two differ by a factor of 10^12. Mixing them silently produces numbers that are a trillion times wrong.
Do my existing Ethereum tools work?
Mostly, with three differences worth knowing. There is no observable public mempool, so anything that watches pending transactions sees nothing. EIP-155 replay protection is mandatory. And transfers can revert at protocol level under compliance rules rather than for the usual gas or balance reasons.
Do I need archive access on Arc?
More often than on other chains, and it catches people out. Nodes keep the standard recent-block window, but blocks land roughly every half second, so that window covers about a minute rather than the twenty-five you would get on Ethereum. In practice almost any historical query is an archive query.
How is Arc RPC priced and provisioned?
It is not on sale yet - shared Arc RPC is in build. A dedicated single-tenant Arc node is a different matter: that we deploy to order, usually within 48 hours, quoted per deployment. Tell us on Telegram which of the two you want. Billing, when it opens, is the same as everything else here: crypto-only, monthly and prepaid.
Get Arc RPC & WebSocket.
Set up over Telegram with an engineer — endpoint, token, tuning.