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
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"}
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.
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.
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
The text was updated successfully, but these errors were encountered: