Make a more informed choice.

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

CompareQuickNode ↗Pimlico ↗Wormhole ↗
PurposeQuicknode 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.Pimlico is listed in Arc’s account-abstraction documentation as bundler and paymaster infrastructure. It fits applications that need sponsored or programmable smart-account transactions. Check the account implementation, EntryPoint version and sponsorship rules together before choosing a provider.Wormhole provides crosschain infrastructure and appears in Arc’s ecosystem directory. Determine the exact message or asset route, contract addresses and trust assumptions before integrating; the directory listing alone does not confirm each Wormhole product on Arc.
Best suited to
  • Application RPC access
  • Infrastructure redundancy planning
  • Gas sponsorship architecture
  • ERC-4337 smart-account integrations
  • Comparing crosschain infrastructure
CategoryData & oraclesData & oraclesBridges & messaging
AvailabilityAnnouncedNot establishedNot established
EvidenceLaunch namedDirectory onlyDirectory only
Role on ArcNamed in Circle launch materials. The release mixes live, onboarding and exploratory relationships; per-product availability needs verification.Listed by Arc; a specific production deployment is not established by the directory.Arc relationship documented by the linked primary reference; individual service availability is described separately.
Access requirementsCheck provider termsCheck provider termsCheck provider terms
Watch points
  • Public endpoint access and paid service commitments are separate.
  • A timeout does not tell you whether a submitted transaction was mined.
  • Bundler support and a funded sponsorship policy are separate requirements.
  • Set limits that protect the sponsor from arbitrary calls.
  • Message delivery, asset wrapping and native issuance are different mechanisms.
Reviewed2026-09-242026-09-242026-09-24
Sources3 sources ↗2 sources ↗2 sources ↗