Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/pages/en/developing/supported-networks.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
\* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/).
\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).

- The hosted service and Subgraph Studio rely on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
- Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
- If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
- For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
Expand Down
9 changes: 1 addition & 8 deletions website/src/supportedNetworks.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -28,16 +28,12 @@ export async function getSupportedNetworks() {
return Array.from(SupportedNetworkMap.values()).flatMap((network) =>
Array.from(network.chains)
.map((chain) => {
const supportedOnHostedService = chain.productDeployStatus.hostedService === ChainProductStatus.ALLOWED
const supportedOnStudio = chain.productDeployStatus.studio === ChainProductStatus.ALLOWED
const integrationType = ['evm', 'near', 'cosmos', 'osmosis', 'ar'].includes(chain.network)
? chain.network
: 'substreams'

if (
!chain.graphCliName ||
(!supportedOnStudio && !supportedOnHostedService && integrationType !== 'substreams')
) {
if (!chain.graphCliName || (!supportedOnStudio && integrationType !== 'substreams')) {
return null as never // `as never` to work around the `.filter(Boolean)` below not narrowing the type
}

Expand All @@ -50,7 +46,6 @@ export async function getSupportedNetworks() {
cliName: chain.graphCliName,
chainId: chain.chainId,
testnet: chain.testnet,
supportedOnHostedService,
supportedOnStudio,
fullySupportedOnNetwork,
substreams: chain.substreams ?? [],
Expand All @@ -71,7 +66,6 @@ export function SupportedNetworksTable({ networks }: { networks: Awaited<ReturnT
<th>{t('supportedNetworks.network')}</th>
<th>{t('supportedNetworks.cliName')}</th>
<th align="center">{t('supportedNetworks.integrationType')}**</th>
<th align="center">{t('supportedNetworks.hostedService')}</th>
<th align="center">{t('supportedNetworks.subgraphStudio')}</th>
<th align="center">{t('supportedNetworks.decentralizedNetwork')}</th>
</tr>
Expand All @@ -82,7 +76,6 @@ export function SupportedNetworksTable({ networks }: { networks: Awaited<ReturnT
<CodeInline>{network.cliName}</CodeInline>
</td>
<td align="center">{network.integrationType}</td>
<td align="center">{network.supportedOnHostedService ? '✓' : null}</td>
<td align="center">
{network.supportedOnStudio ? '✓' : null}
{network.substreams.includes('studio') ? <sup>†</sup> : null}
Expand Down