Category

Developer Infrastructure on Arc · 27

The layer a team assembles before it ships anything, and the best-documented category on Arc, because Circle publishes named vendor lists in Arc's own developer documentation for node providers, data indexers, oracles, account abstraction and compliance.

That documentation is the primary source for most entries here, and it carries an important limit each entry states: being listed in Arc's docs means Circle names the vendor for Arc, not that a mainnet deployment or a commercial partnership exists. Arc has no mainnet until 16 September 2026, and the node-provider endpoints published as of 2 September 2026 are testnet. Role here is Serves, so on-chain checks apply only where a provider deploys its own contracts on Arc.

Filters
#ProjectWhat it builds on ArcRoleStatusLinksChecked

Questions

Why do most entries here have no on-chain checks?

On-chain checks only apply to projects that deploy contracts or issue assets. For a service provider they would be meaningless, so nothing is shown. That is not a deficiency.

What makes an infrastructure entry Live?

The service is publicly usable against Arc on the date we checked, with a source we can link — documentation, a status page, or the endpoint itself.

Does paying change where a project appears?

No. Paid entries are labelled Listing, sit in the same ranked order as everything else, and use rel="sponsored". Payment never affects status, flags, evidence or the Editor's Index.