-
Notifications
You must be signed in to change notification settings - Fork 119
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
Full-featured identify
implementation
#358
Comments
What do you mean with that? That we are able to send local multiaddresses to remote peers when in the identify stage, or we send our view of their peer address when in the identify stage? |
@ShadowJonathan resolving this following the semantics here: https://github.com/libp2p/go-libp2p/blob/master/p2p/protocol/identify/id.go#L307-L309 |
Should just be an easy fix if the client can grab the current connecting peer's multiaddr |
Hey @pacrob , can you please assign me this issue? |
@vipulnayyar Are you still working on this? otherwise I would like to work on this issue |
Hey @acul71 , please feel free to work on this issue. |
We should reach feature-parity w/ the Go implementation of
identify
.Some things missing:
The text was updated successfully, but these errors were encountered: