Package Exports
- @libp2p/interfaces
- @libp2p/interfaces/connection
- @libp2p/interfaces/connection/status
- @libp2p/interfaces/content-routing
- @libp2p/interfaces/crypto
- @libp2p/interfaces/crypto/errors
- @libp2p/interfaces/dht
- @libp2p/interfaces/errors
- @libp2p/interfaces/keys
- @libp2p/interfaces/metrics
- @libp2p/interfaces/peer-discovery
- @libp2p/interfaces/peer-id
- @libp2p/interfaces/peer-routing
- @libp2p/interfaces/peer-store
- @libp2p/interfaces/pubsub
- @libp2p/interfaces/record
- @libp2p/interfaces/stream-muxer
- @libp2p/interfaces/topology
- @libp2p/interfaces/transport
- @libp2p/interfaces/value-store
Readme
libp2p-interfaces
Contains interfaces you can use to implement the various components of libp2p
Table of contents
Interfaces
- Connection
- Content Routing
- Crypto
- Peer Discovery
- Peer Routing
- Pubsub
- Record
- Stream Muxer
- Topology
- Transport
Origin Repositories
For posterity, here are links to the original repositories for each of the interfaces (if they had one).
Contribute
The libp2p implementation in JavaScript is a work in progress. As such, there are a few things you can do right now to help out:
- Go through the modules and check out existing issues. This would be especially useful for modules in active development. Some knowledge of IPFS/libp2p may be required, as well as the infrastructure behind it - for instance, you may need to read up on p2p and more complex operations like muxing to be able to help technically.
- Perform code reviews. More eyes will help a) speed the project along b) ensure quality and c) reduce possible future bugs.
- Add tests. There can never be enough tests.
License
Apache-2.0 or MIT © Protocol Labs