You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to this official blog article https://thegraph.com/blog/indexing-solana-substreams/ Solana should be accessible using the hosted service but I do not see any option to initialize one using the graph init command. I see multiple networks supported for substreams protocol but solana is missing.
Is it possible to create a hosted subgraph for Solana using substreams - as mentioned in the blog?
Initialize a new hosted subgraph with the command graph init --product hosted-service.
Select substreams as the protocol.
Enter any name.
See the list of "Substreams network" to choose from
Expected behavior
This list should contain an option for Solana network, but it doesn't
Which packages are impacted by your issue?
@graphprotocol/graph-cli
Describe the issue
According to this official blog article https://thegraph.com/blog/indexing-solana-substreams/ Solana should be accessible using the hosted service but I do not see any option to initialize one using the
graph init
command. I see multiple networks supported forsubstreams
protocol but solana is missing.Is it possible to create a hosted subgraph for Solana using substreams - as mentioned in the blog?
Reproduction
https://github.com/graphprotocol/graph-tooling
Steps to Reproduce the Bug or Issue
Initialize a new hosted subgraph with the command
graph init --product hosted-service
.Select
substreams
as the protocol.Enter any name.
See the list of "Substreams network" to choose from
Expected behavior
This list should contain an option for Solana network, but it doesn't
Screenshots or Videos
This is the list of substream networks I see:
Platform
@graphprotocol/graph-cli
version: 0.67.2Output of
graph --version
:@graphprotocol/graph-cli/0.67.2 darwin-arm64 node-v21.6.1
Subgraph Manifest
No response
Subgraph GraphQL Schema
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: