libp2p / workspace-go-libp2p

workspace for go-libp2p contributors

libp2p is a modular networking framework bundled together as a full stack of protocols for peer-to-peer systems.

libp2p is the product of a long and arduous quest into the internet's network stack and all of the plentiful peer-to-peer protocols of the past. Building large-scale peer-to-peer systems has been complex and challenging in the last fifteen years, and libp2p is a way to fix that. It is a "network stack" -- a protocol suite -- that cleanly separates concerns and enables sophisticated applications to only use the protocols they need without giving up interoperability and upgradeability. libp2p grew out of IPFS but is built so that many people can use it for many different projects.

Learn more about libp2p at libp2p.io and docs.libp2p.io.

Specifications

View the formal specifications of libp2p on the specifications repository.

Implementations

Follow the latest libp2p implementations at libp2p.io/implementations.

• go-libp2p in Go
• js-libp2p in Javascript, for Node and the Browser
• rust-libp2p in Rust
• py-libp2p in Python
• cpp-libp2p in C++
• swift-libp2p in Swift
• nim-libp2p in Nim
• jvm-libp2p in Kotlin
• erlang-libp2p in Erlang
• zig-libp2p in Zig
• dotnet-libp2p in .NET

Community Discussion

Please visit our discussion forums at discuss.libp2p.io to get help, ask questions about the past, present, and future of libp2p, and more.

workspace-go-libp2p's Issues

After the repo consolidation, do we still need this repository?

@marten-seemann should we archive this repository?

Add go team to this repo

With write permissions, so I can push branches. (also the admin team with admin permissions.)

@raulk you're probably the owner?

Do we need a way to `go test` in all repositories?

During the OpenStream refactor, I found that it would be useful to have a way to run go test ./... in all repositories, in order to discover if the interface changes lead to unexpected build / test failures (yes, they did, a lot).

Would it make sense to add a command for this in workspace.sh? I could imagine two ways to do this:

1. Either add a workspace.sh test flag, that runs go test ./... in all repos.
2. Or add a workspace.sh exec <cmd>.

Any thoughts?