-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Somehow combine go-libp2p-crypto and go-libp2p-peer #484
Comments
(and libp2p/specs#111 can be fixed, for now, by just getting rid of peer-id inlining and re-introducing it when we add the correct field to the key protobuf). |
I am in favour of having a meta-package for this; crypto is useful outside the concept of peer. |
@Stebalien agree it'd be good start to consolidating repos. I don't suppose we'd entertain the idea of moving both peer and crypto to somewhere more central, though? go-libp2p wouldn't be that place, because clients can instantiate libp2p without importing go-libp2p (ironically), i.e. if they're using BlankHost. In our current layout, that central place could be go-libp2p-host. You really cannot have libp2p without importing
If somebody really wants to use |
I'm going to take a stab at making a |
Is there any changes to the implementation or a decision made about this issue? |
All core interface libraries have been merged into |
Peer IDs and keys are closely tied together. Unfortunately, they currently live in two separate packages. My current thinking is either:
My motivation is fixing libp2p/specs#111. We need to be bale to deterministically derive peer IDs from keys. That means keys nee to remember their multihash. However, that's a peer-ID concern which doesn't really fit in the current go-libp2p-crypto package.
@raulk this is related to your monorepo suggestion and, IMO, a good start. We could also combine these packages with a few others if we have some other "core" concepts.
Note: fixing libp2p/specs#111 is a rather high priority so I don't want to block it on reworking all of our dependencies.
The text was updated successfully, but these errors were encountered: