Make a more informed choice.

Compare what projects do, what’s available, and the evidence behind each profile. Select up to three.

CompareThe Graph ↗QuickNode ↗KronoScan ↗
PurposeThe Graph appears in Arc’s data-indexer documentation with subgraph and Substreams references. It is relevant to applications that need a reusable query model over contract events. Check whether the specific deployment is hosted, decentralized or self-operated and how indexing lag is exposed.Quicknode provides network access for Arc applications. The official network reference lists its Arc mainnet and testnet endpoints. Choose a production plan around traffic, history and subscriptions, and keep your application able to distinguish an RPC failure from a failed onchain transaction.Named hackathon submission; no production status established.
Best suited to
  • Queryable contract data
  • Application RPC access
  • Infrastructure redundancy planning
Read the profile and provider documentation for fit.
CategoryData & oraclesData & oraclesDeveloper tools
AvailabilityNot establishedAnnouncedPrototype
EvidencePlatform documentedLaunch namedPrototype only
Role on ArcArc relationship documented by the linked primary reference; individual service availability is described separately.Named in Circle launch materials. The release mixes live, onboarding and exploratory relationships; per-product availability needs verification.Named hackathon submission; no production status established.
Access requirementsCheck provider termsCheck provider termsCheck provider terms
Watch points
  • An ecosystem listing does not prove that a suitable public subgraph already exists.
  • Public endpoint access and paid service commitments are separate.
  • A timeout does not tell you whether a submitted transaction was mined.
No specific watch points recorded. Check the source material.
Reviewed2026-09-242026-09-242026-09-17
Sources2 sources ↗3 sources ↗1 sources ↗