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
I want to listen to multiple chains within a single graph node, and I noticed the description in the docker/Dockerfile file is as follows: # The etherum network(s) to connect to. Set this to a space-separated list of the networks where each entry has the form NAME:URL
ENV ethereum=""
This seems to imply support for multi-chain.But when I use multiple chains in docker/docker-compose.yml ethereum: 'mainnet:http://host.docker.internal:8545 polygon:http://host.docker.internal:8545'
The following error will occur.
I'm not sure if this is a bug or if multi-chain monitoring is currently not supported.
Relevant log output
graph-node-1 | Waiting for Postgres (postgres:5432)
graph-node-1 | error: unexpected argument 'polygon:http://host.docker.internal:8545' found
graph-node-1 |
graph-node-1 | Usage: graph-node [OPTIONS]
graph-node-1 |
graph-node-1 | For more information, try '--help
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
Tick this box if this bug is caused by a regression found in the latest release.
Tick this box if this bug is specific to the hosted service.
I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
Linux
The text was updated successfully, but these errors were encountered:
Bug report
I want to listen to multiple chains within a single graph node, and I noticed the description in the docker/Dockerfile file is as follows:
# The etherum network(s) to connect to. Set this to a space-separated list of the networks where each entry has the form NAME:URL
ENV ethereum=""
This seems to imply support for multi-chain.But when I use multiple chains in docker/docker-compose.yml
ethereum: 'mainnet:http://host.docker.internal:8545 polygon:http://host.docker.internal:8545'
The following error will occur.
I'm not sure if this is a bug or if multi-chain monitoring is currently not supported.
Relevant log output
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
OS information
Linux
The text was updated successfully, but these errors were encountered: