Company
One chain, served properly.
ArcRPC is infrastructure for Arc, Circle's Layer-1 for stablecoin settlement. Not a multi-chain platform that added chain 5042 to a list.
Why one chain
A generic provider has to be right about eighty chains at once. That is how published Arc documentation from established vendors ends up stating the wrong native decimal count, omitting the arc_* namespace, and advertising mempool products the network blocks.
Being wrong about one chain is a support ticket. On a settlement chain it is a reconciliation break, and the customer finds it in a month-end close rather than in a dashboard.
How we operate
We run our own full and archive nodes in every core region, bootstrapped from Arc snapshots on the published minimum spec. The node build we serve from is public, and you can assert it yourself with arc_getVersion before you trust a response.
The method matrix comes from probes against production nodes every six hours, with the run timestamp attached. When a method changes behaviour, the table changes before you find out in production.
Principles
How decisions get made here.
Publish the number
Rate limits, getLogs ranges, latency percentiles, uptime and prices are on the site. An unpublished figure is a claim, not a commitment.
Correctness at the endpoint
A warning in a doc page is not a safeguard. Decimal handling, the fee floor and transfer de-duplication are enforced where the request is served.
No feature gate on accuracy
arc_* methods, archive, decimal-safe balances and the floor guard are on the lowest plan. Plans sell throughput and controls.
Say what is missing
SOC 2 Type II is not finished, gRPC is not shipped, and Arc Privacy Sector is not live on the network. All three are marked roadmap wherever they appear.
Own the incident
Every incident gets a public entry with duration, blast radius and the fix, including the ones nobody noticed.
Portable by default
Standard JSON-RPC, standard tooling, exportable data. The helpers are convenience, never lock-in.
Evidence
Every number on this site, and where it comes from.
A measured claim names its method. A target says it is a target. Nothing here is a round number chosen because it reads well.
| Claim | Kind | Evidence |
|---|---|---|
| 99.99% uptime SLA | commitment | Contractual on Enterprise with service credits. Measured per region, method published on the status page. |
| p50 11ms in us-east-1 | measured | In-region eth_getBlockByNumber, 7 day trailing, republished monthly. |
| 6 core regions, 6 edge regions | measured | Region list with tier and archive availability is published in full. |
| Archive billed at request parity | commitment | One unit per call at any block age. Stated in the pricing table. |
| SOC 2 Type II | target | Type I in progress, Type II targeted Q2 2027. Marked roadmap everywhere it appears. |
| Live-tested method matrix | measured | Probed against production nodes every six hours, run timestamp published with the table. |
Security
Posture, controls and disclosure.
Attestation
RoadmapSOC 2 Type I engagement is in progress and Type II is targeted for Q2 2027. Annual third-party penetration test, quarterly internal review. TLS 1.3 everywhere, keys encrypted at rest, and no customer private keys held at any time. We never take custody of funds and never ask for a signing key.
Controls
Least-privilege access with hardware-key enforced SSO for staff, full audit logging on the control plane, separated production and corporate networks, and reviewed deploys. Subprocessor list, architecture diagram and test summaries are available under NDA.
Disclosure goes to [email protected]. Acknowledgement within 24 hours, triage within 3 business days, and no legal action against good-faith research.
Bring the workload that has to balance.
Reconciliation that has to tie out, settlement that has to prove, throughput that has to hold under close.