Skip to content

50% OFF your first payment. Limited time!

Claim your 50% Discount
LiveArc Mainnet · chain 5042

The Arc-nativeRPC and data platform.

Parity with the four providers Arc lists, on every line item that matters. Plus the Arc-specific correctness none of them has shipped: two USDC decimal interfaces handled at the endpoint, settlement proofs from the commit certificate, and one de-duplicated transfer feed.

99.99%
uptime SLA
11ms
p50, us-east-1
0.5s
arc block time
Finality proof, one call
bash
curl https://rpc.arcrpc.com/v1/$KEY \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,
       "method":"arc_getCertificate",
       "params":["latest"]}'

Same call shape on Arc Testnet, chain 5042002. Archive is on by default and billed at the same rate as a call against the tip.

Why this exists

Arc is not a generic EVM chain, and most providers serve it as one.

Published documentation from established vendors states the wrong native decimal count, omits the arc_* namespace, and advertises mempool products the network blocks at the protocol level. Each of these is a place a payment rail gets a number wrong.

  1. 01

    USDC has two decimal interfaces over one balance

    Native USDC is 18 decimals, the ERC-20 interface at 0x3600…0000 is 6. They are the same balance. A zero balanceOf does not mean an empty account, because the ERC-20 view truncates sub-USDC fractions. Mixing them is off by a factor of 10¹².

  2. 02

    The mempool is closed

    eth_newPendingTransactionFilter and eth_subscribe("newPendingTransactions") return -32001. eth_getBlockByNumber("pending") and eth_getTransactionBySenderAndNonce return null, which fails quietly. txpool_* still works for pool inspection.

  3. 03

    Transactions under 20 Gwei are dropped silently

    A transaction with maxFeePerGas below the base fee floor never enters a block and never produces a receipt or an error. It simply never existed.

  4. 04

    One transfer emits two logs

    An ERC-20 transfer() emits a 6 decimal Transfer from the token contract and an 18 decimal EIP-7708 Transfer from the system emitter. A plain native send emits only the system log. Gas deductions emit no log at all.

  5. 05

    Finality is deterministic

    A block is either absent or irreversible. There are no reorgs, no confirmation depth and no uncles, so an indexer needs no rollback path and a webhook is safe at one confirmation.

  6. 06

    History starts about a minute behind the tip

    At half-second blocks, the usual 127-block archive boundary is roughly sixty seconds old, so almost every historical read is an archive read.

  7. 07

    Timestamps are non-decreasing, not increasing

    Sub-second blocks share a block.timestamp. The ordering key is (blockNumber, logIndex), never the timestamp.

  8. 08

    A transfer can revert with a full balance

    Transfers to the zero address, burns, transfers to a self-destructed account, transfers to a precompile, and any transfer touching a blocklisted address all revert. The revert still consumes gas.

Core RPC

Full parity, both networks, no feature asterisks.

Everything expected from a tier-one provider, serving Arc mainnet and testnet under the same SLA.

Arc Mainnet JSON-RPC

Chain 5042 over HTTPS and WSS.

Arc Testnet JSON-RPC

Chain 5042002 over HTTPS and WSS.

Archive, unpruned

Genesis-snapshot archive on both networks, billed at request parity.

debug_* and trace_*

Four usable debug tracers and all nine trace methods.

arc_* namespace

arc_getVersion and arc_getCertificate, documented and load tested.

Admin API

Programmatic endpoint creation, scoping and rotation.

Method matrix

59 methods serve data. 7 are blocked or answer null, and we publish which, because a method that quietly returns null is worse than one that errors. Probed against production nodes every six hours. Last run 2026-09-16 04:00 UTC.

NetworkChainArchive
Arc Mainnet5042Unpruned
Arc Testnet5042002Unpruned

Arc-native

Six capabilities nobody else on Arc serves.

Each one exists because a default EVM assumption is wrong here, and somebody's reconciliation depends on the difference.

Decimal-safe USDC balances

Native 18, ERC-20 6 and display value in one response.

Gas floor guard and USD oracle

Sub-floor transactions rejected instead of dropped, fees quoted in dollars.

Settlement Proof API

Cached BFT commit certificates with an offline verifier.

Unified USDC transfer feed

Both emitters merged and de-duplicated, with Memo, blocklist and CCTP legs.

Compliance pre-flight

simulateTransfer against live blocklist state.

Finality-aware webhooks

Signed delivery, safe at one confirmation.

What we do not serve

The limits, on the marketing page.

Two of these are ours to finish. Three are Arc's, and no provider can serve them, whatever a comparison table says.

SOC 2 Type II

Roadmap

Independent attestation of the control set.

Type I engagement in progress. Type II targeted Q2 2027.

gRPC transport

Roadmap

Binary transport for high-throughput indexers.

Targeted Q1 2027. JSON-RPC and the stream API cover the same data today.

Arc Privacy Sector support

Roadmap

Reads against confidential execution state.

APS is on Arc’s own roadmap and is not live on the network, so nobody can serve it yet.

Pending transaction streaming

Not possible on Arc

Subscribing to transactions before inclusion.

Arc disables pending-transaction visibility at the protocol level and returns -32001. No provider can offer this.

Reorg handling

Not possible on Arc

Rollback and confirmation-depth logic.

Arc finalises on commit, so there is nothing to roll back. Any product built on reorgs is selling a problem Arc does not have.

Who it is for

Teams moving real money on Arc.

Wallets

One USDC balance row, correct at both decimal scales, with a finality-aware activity feed.

Exchanges

Deposit detection with no double counting and no confirmation buffer.

PSPs

Memo-tagged settlement, compliance pre-flight, archive-grade reconciliation.

Treasury and FX

CCTP-correlated crosschain flows and StableFX-aware decoding.

Institutions

Signed settlement proofs, residency, dedicated capacity, an SLA with credits.

Indexers

Trace access, stream backfill and a signed gap report per range.

Point your existing Arc code at a better endpoint.

Keys for both networks issue in under a minute, on one bill. Talk to us for dedicated capacity, residency or a signed SLA, and a solutions engineer answers.