Make a more informed choice.

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

CompareThe Graph ↗LayerZero ↗Arc Network ↗
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.LayerZero builds technology that makes decentralization possible, scalable, and inevitable. Listed by Arc; a specific production deployment is not established by the directory.Arc is a Layer 1 for payments and financial applications. Its public mainnet uses chain ID 5042; the separate testnet uses 5042002. Start with the network reference when configuring a wallet or RPC. A chain connection alone says nothing about the availability, liquidity or access rules of an individual application.
Best suited to
  • Queryable contract data
Read the profile and provider documentation for fit.
  • Configuring an EVM wallet or application
  • Checking mainnet and testnet settings
CategoryData & oraclesBridges & messagingCore network
AvailabilityNot establishedNot establishedMainnet
EvidencePlatform documentedDirectory onlyPlatform documented
Role on ArcArc relationship documented by the linked primary reference; individual service availability is described separately.Listed by Arc; a specific production deployment is not established by the directory.Public EVM L1 launched September 16, 2026.
Access requirementsCheck provider termsCheck provider termsCheck provider terms
Watch points
  • An ecosystem listing does not prove that a suitable public subgraph already exists.
No specific watch points recorded. Check the source material.
  • Use the explorer that matches the transaction’s chain.
  • USDC is required for gas unless an application sponsors it.
Reviewed2026-09-242026-09-172026-09-24
Sources2 sources ↗1 sources ↗3 sources ↗