Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

error while requesting fraud proofs, protocols not supported #3

Open
gupadhyaya opened this issue May 23, 2023 · 1 comment
Open

error while requesting fraud proofs, protocols not supported #3

gupadhyaya opened this issue May 23, 2023 · 1 comment

Comments

@gupadhyaya
Copy link
Contributor

When nodes are started sequentially with peers configured, the fraud service expects the seed nodes to be already started, otherwise will result in the following error.

2023-05-16T19:56:05.315-0500 ERROR fraudserv fraudserv/sync.go:74 error while requesting fraud proofs {"err": "protocols not supported: [/state-fraud/fraud/v0.0.1]", "peer": "12D3KooWJXHwdV5dfhneCJYpkFRcoSZsVBK13Dzz2C1CsC2TyZMh"}

rollkit/rollkit#945

@gupadhyaya
Copy link
Contributor Author

google gave some clues, but does not seem to be the case. for instance: libp2p/go-libp2p-examples#87, mentions that host has to call SetStreamHandler and then you can perform NewStream. But, this is already happening in the service.go.

similar answer: https://discuss.libp2p.io/t/protocol-not-supported-while-using-host-newstream/1032

my best guess is that when creating NewStream the peerid pointing to the peer must also be available in the network. This is not the case when we start the node 1-by-1, hence it throws error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant