Arc RPC endpoints for stablecoin payments

Arc RPC is the API your application uses to read Arc blockchain data, call smart contracts, and submit signed transactions. Arc is Circle’s EVM-compatible Layer 1 for stablecoin applications, with USDC used for network fees. Chainstack provides managed access to Arc Mainnet and Arc Testnet through Arc JSON-RPC endpoints.

Create a free Chainstack account, create a project, and deploy an Arc Global Node on mainnet or testnet. Open Access and credentials to copy your HTTPS and WebSocket URLs. The Developer plan includes 3 million request units per month, up to 25 requests per second, and one node. No credit card is required.

Arc Mainnet uses chain ID 5042. Arc Testnet uses 5042002. Both use USDC as the native gas currency. Configure your wallet or library for the same network as your RPC endpoint. See the Arc tooling guide for network settings.

Arc uses USDC for gas. The native USDC balance returned by eth_getBalance uses 18 decimals, while the ERC-20 USDC balance returned by balanceOf uses 6 decimals. These are two interfaces to the same underlying balance, so convert the units before comparing values. See Arc’s EVM differences.

Yes. Arc supports Ethereum JSON-RPC methods such as eth_call, eth_getBalance, eth_getLogs, and eth_sendRawTransaction. Connect ethers.js, viem, or web3.py to your Arc endpoint using the correct chain ID and USDC native-currency settings. Follow the Arc integration examples and check Arc-specific EVM behavior when building transaction logic.

Chainstack Arc endpoints support WebSocket subscriptions for new blocks and contract logs. Arc does not expose pending-transaction subscriptions: eth_subscribe("newPendingTransactions") and eth_newPendingTransactionFilter are disabled by the network. Build payment confirmation around transaction receipts and block inclusion. See Arc method availability.

Yes. Chainstack provides Arc archive access and Debug & Trace APIs from the Growth plan. Query historical balances and contract state, replay execution, and investigate reverted transactions. Archive requests consume 2 request units; full requests consume 1. Check Arc methods for supported calls and pricing for plan features.

Optimized submission routes signed Arc mainnet transactions through a private, optimized path designed to reduce inclusion delays. It uses your existing HTTPS or WebSocket endpoint and is available on Arc Global Nodes on every plan, including Developer. Manage it from your node’s Add-ons tab. See optimized submission for activation and fallback behavior.

A Global Node provides geo-balanced RPC access through a shared infrastructure service. A Dedicated Node provides isolated compute and storage for your deployment, with full or archive configurations. Dedicated Nodes are available from the Pro plan, with infrastructure billed separately. Compare the node options and pricing for your workload.

Yes. Chainstack Self-Hosted currently lists Arc Testnet support using paired execution and consensus clients. Deploy a non-validator full node on infrastructure you control, with monitoring, automated updates, and self-healing operations. Check supported clients and protocols and follow the installation guide.

Use the official Circle faucet and select Arc Testnet to request test tokens for development. Connect your application to an Arc Testnet RPC endpoint with chain ID 5042002. Testnet USDC has no monetary value and cannot pay mainnet transaction fees.