Currently, the HOPR Association manages multiple subgraphs that index data from various blockchains, notably Ethereum Mainnet and the Gnosis chain. However, several subgraphs still reside on the hosted service, serving as fallback data sources for dApps and snapshot voting strategies.
The following subgraphs have not yet been migrated and published in the decentralized graph network:
Additionally, all the subgraphs deployed in the decentralized graph network should be migrated from Ethereum mainnet to Arbitrum in order to save costs on re-publishing upgrades:
Once migrated to Arbitrum, subgraphs' production query endpoints change to https://gateway-arbitrum.network.thegraph.com/api/[api-key]/subgraphs/id/[subgraph-id]
As CT and products use variouis subgraphs, we need to coordinate the update:
[x] Association initiate transactions on mainnet to upgrade all the subgraphs
[x] CT app prepare PRs to update relevant subgraph endpoints. Consider using development endpoints as backup to reduce downtime during migration.
[x] PRODs prepare PRs to update relevant subgraph endpoints. Consider using development endpoints as backup to reduce downtime during migration.
[x] Association execute txns
Node running
As staking dApps continue to allow staking accounts to claim rewards after seasons end, the respective subgraphs must actively feed data to these web applications. However, given the relatively low activity level and the decentralized subgraph's economic model, which does not naturally incentivize neutral indexers to index low-usage subgraphs, it's advisable for the association to run at least one graph node to index these subgraphs.
Moreover, heavily utilized subgraphs such as "hopr-nodes-dufour", "hopr-channels," and "HOPR Stake all seasons" are vital for StakingHub and Cover traffic. Therefore, the HOPR Association should consider running a graph node for these subgraphs.
Migration
Currently, the HOPR Association manages multiple subgraphs that index data from various blockchains, notably Ethereum Mainnet and the Gnosis chain. However, several subgraphs still reside on the hosted service, serving as fallback data sources for dApps and snapshot voting strategies.
The following subgraphs have not yet been migrated and published in the decentralized graph network:
Additionally, all the subgraphs deployed in the decentralized graph network should be migrated from Ethereum mainnet to Arbitrum in order to save costs on re-publishing upgrades:
Once migrated to Arbitrum, subgraphs' production query endpoints change to
https://gateway-arbitrum.network.thegraph.com/api/[api-key]/subgraphs/id/[subgraph-id]As CT and products use variouis subgraphs, we need to coordinate the update:
Node running
As staking dApps continue to allow staking accounts to claim rewards after seasons end, the respective subgraphs must actively feed data to these web applications. However, given the relatively low activity level and the decentralized subgraph's economic model, which does not naturally incentivize neutral indexers to index low-usage subgraphs, it's advisable for the association to run at least one graph node to index these subgraphs.
Moreover, heavily utilized subgraphs such as "hopr-nodes-dufour", "hopr-channels," and "HOPR Stake all seasons" are vital for StakingHub and Cover traffic. Therefore, the HOPR Association should consider running a graph node for these subgraphs.