We checked the sources for this guide on 24 Sept 2026. Use the linked sources for current availability, terms and network details. See subsequent updates
An ecosystem directory is a map of relationships. To decide whether an integration is usable, trace the claim to a specific product, network and date.
Use the evidence label as a starting point
| Evidence you found | What it establishes | What still needs checking |
|---|---|---|
| Official directory entry | The platform lists the organization | Product availability and exact integration |
| Launch announcement | A relationship was named at a particular time | Whether that product has shipped |
| Testnet demonstration | A described flow ran in a test environment | Production deployment, access and operations |
| Project-owned launch confirmation | The project says a defined product is live | Current access, liquidity, limits and observed behavior |
| Contract and technical documentation | A specific interface or deployment is documented | Whether your intended flow works with it |
Arc’s official directory is useful for discovery. It is paginated; a first-page scrape can miss providers later in the alphabet. A count of logos should not be presented as a count of production applications.
Ask a narrower question
“Is the project on Arc?” is often too broad. Ask whether a named product supports mainnet chain 5042, which operation it supports and who can access that operation. Record the answer separately from token support, validator participation and a company’s wider business.
For a concrete example, Uniswap’s announcement names its supported protocol versions and application surfaces. That is stronger product evidence than a directory logo. It still cannot tell you the execution price for a swap today.
Resolve contradictions without hiding them
Prefer the most specific current source, while retaining the older evidence and its date. During the September 24 review, Arc’s documentation index still contained a testnet-only sentence while the connection reference documented mainnet. Record that inconsistency; do not silently turn an index summary into the network’s current status.
Also verify where an official link actually lands. The reviewed Pulsar directory link returned a Solana product titled Shotgun. That supports flagging the application URL as unresolved, while the Arc partner article remains evidence of the Arc relationship.
Treat social posts as dated leads
A project’s official post can point to a release, but preserve its author, exact URL and publication date. If X blocks access, say so and use a readable primary announcement for the factual summary. Do not invent a quote, engagement count or posting date from a profile page.
For a correction to Arcwiki, include the affected profile, a precise claim, a primary source link and the date you checked it. A useful report says which product changed and what the source proves, so an editor can update the right field without upgrading every related claim.
Sources & references
Documents cited in this guide.