Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

BSC subgraph with callHandler cause error #3517

Closed
jiriano opened this issue Apr 30, 2022 · 4 comments
Closed

BSC subgraph with callHandler cause error #3517

jiriano opened this issue Apr 30, 2022 · 4 comments

Comments

@jiriano
Copy link

jiriano commented Apr 30, 2022

Do you want to request a feature or report a bug? Bug

I try to deploy a subgraph on the BSC chain and face this error:

Failed to start subgraph, code: SubgraphStartFailure, error: expected triggers adapter that matches deployment QmS58kNTGg4VYPNMEH53JymEKjcrUtCzRQmNS3pkNMTJMD[279681] with required capabilities: traces: A matching Ethereum network with NodeCapabilities { archive: false, traces: true } was not found.

When I deploy this subgraph to mainnet or change a subgraph by deleting the callHandler everything works fine.

@itsjerryokolo
Copy link
Contributor

CallHandlers require tracing, which isn't available on BSC. It's isn't a graph-node issue.

@jiriano
Copy link
Author

jiriano commented May 1, 2022

@itsjerryokolo
Thanks for your response.
Do you know which repository is appropriate to request this feature?

@itsjerryokolo
Copy link
Contributor

That's something that needs to be enabled from Binance. The graph-node connects to the RPC endpoint they provide.

@azf20
Copy link
Contributor

azf20 commented May 3, 2022

Thanks so much @itsjerryokolo ! Closing for now

@azf20 azf20 closed this as completed May 3, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants