-
Notifications
You must be signed in to change notification settings - Fork 877
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
floodsub example: cannot dial with peer id specified #471
Comments
@tomaka : I just discussed this a little with @Stebalien. His view is that in the future we want to only support Either way, though, we think it's a bug not to support multiaddrs longer than Thoughts? |
This is more of a limitation of the In substrate we indeed check the peer ID, however we don't put it as part of the multiaddress. |
I'm playing with the
floodsub
example. Separately, I have a go-libp2p node listening on 127.0.0.1:9876, which subscribes to the same pubsub topic string as the floodsub example.When I dial without specifying the peer ID (
/ip4/127.0.0.1/tcp/9876
), it works:And the go-libp2p program listening on 9876 sees the inbound connection - yay!
But when I dial with the full multiaddr of the peer on 9876 (
/ip4/127.0.0.1/tcp/9876/ipfs/QmehVYruznbyDZuHBV4vEHESpDevMoAovET6aJ9oRuEzWa
), it fails like this:It's obviously choking on the "/ipfs/" part, but I can't figure out why. Specifying a peer id is a valid multiaddr. Maybe this is just not supported yet by rust-libp2p?
My Cargo.toml and full source used here are on a sub-directory in a WIP branch here: https://github.com/mgoelzer/libp2p-demo-go-js-rust/tree/rust-mvp/pubsub/rust
The text was updated successfully, but these errors were encountered: