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

Update to go-libp2p 0.6.0 #6914

Merged
merged 1 commit into from Mar 10, 2020

Conversation

marten-seemann
Copy link
Member

This PR moves a bunch of code remove from go-libp2p-pnet to go-ipfs. This is necessary due to the change in the private network interface (see libp2p/go-libp2p#795).

@hsanjuan
Copy link
Contributor

This PR moves a bunch of code remove from go-libp2p-pnet to go-ipfs. This is necessary due to the change in the private network interface (see libp2p/go-libp2p#795).

This is just the part about parsing the 3-line private network key file right? Are we sure this was not used outside of IPFS? It is going to be hard for people to find it (and use it) if they were relying on it. Might consider keeping and marking as deprecated in libp2p land?

@Stebalien
Copy link
Member

@hsanjuan has a good point. We might as well keep the decoding code, at least, in go-libp2p-pnet so others can use it.

@bonedaddy
Copy link
Contributor

Please don't move deserialization here. This will give me another repository I need to fork and manage.

This is libp2p functionality, please have it stay as such.

core/node/libp2p/pnet.go Outdated Show resolved Hide resolved
@Stebalien Stebalien force-pushed the generalize-private-network branch 2 times, most recently from 0daef82 to 8d2bdfd Compare March 10, 2020 00:41
@Stebalien Stebalien changed the title move deserialization of private network keys here Update to go-libp2p 0.6.0 Mar 10, 2020
@Stebalien Stebalien merged commit 6ae79ef into ipfs:master Mar 10, 2020
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

Successfully merging this pull request may close these issues.

None yet

4 participants