Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.arc.network/llms.txt

Use this file to discover all available pages before exploring further.

Arc follows a phased deployment model, progressively expanding network access and decentralization. The Public Testnet is the current active network, and developer access is permissionless at every phase: you can deploy contracts and send transactions without approval.

​
Deployment phases

PhaseStatusDescription
DevnetInternalInternal protocol testing — Circle’s development network for protocol iteration. Not publicly accessible.
Private TestnetCompleteInvitation-only testnet used for early integration testing with select partners.
Public TestnetLiveMirrors mainnet behavior without using real assets. Permissionless testnet (chain ID 5042002) available to all developers.
Private MainnetUpcomingProduction network where real value flows. Initial launch with approximately 20 permissioned validators and limited access.
Public MainnetUpcomingFull public mainnet with open access for all users and applications.
For connection details, see RPC endpoints. To explore testnet activity, visit testnet.arcscan.app.

​
Testnet performance

The Public Testnet has demonstrated production-grade performance since launch. The following metrics are from the Q1 2026 monthly review.
MetricValue
Uptime100%
Average block time~0.48 s
Transactions~30.7M
Unique wallets916K
Block explorertestnet.arcscan.app

​
Validator model at launch

Arc launches with a permissioned Proof-of-Authority (PoA) validator set — a consensus model in which a fixed group of known, vetted institutions produce and validate blocks, rather than anonymous participants staking tokens. Approximately 20 SOC 2-certified validators operate across multiple global regions, each bound by uptime SLAs and compliance obligations. Block production rotates among validators to ensure fairness and liveness. For full details on the validator set, see Consensus layer.

​
Future evolution

Arc may transition from Proof-of-Authority to a permissioned Proof-of-Stake (PoS) model — a consensus mechanism where validators lock tokens as collateral rather than relying solely on institutional selection. This broadens validator participation while maintaining the compliance requirements and institutional accountability that define the network. See the consensus layer roadmap for details.