Skip to content

The Rust Implementation of the libp2p networking stack.

License

Notifications You must be signed in to change notification settings

umgefahren/rust-libp2p

This branch is 15 commits ahead of, 155 commits behind libp2p/rust-libp2p:master.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

7dd75a5 · Aug 5, 2024
Aug 5, 2024
Aug 3, 2024
Nov 20, 2023
Aug 3, 2024
Aug 3, 2024
Jun 12, 2024
Jul 30, 2024
Aug 3, 2024
Aug 3, 2024
Aug 3, 2024
Aug 4, 2024
Nov 28, 2023
Aug 3, 2024
Apr 27, 2024
Aug 3, 2024
Aug 3, 2024
Aug 3, 2024
Feb 10, 2023
Mar 13, 2023
Sep 4, 2022
Jan 30, 2023
Oct 26, 2023
Jun 30, 2023
Aug 4, 2024
Aug 3, 2024
Nov 24, 2020
Aug 2, 2024
Sep 18, 2023
Dec 19, 2023
Oct 16, 2023
Jun 7, 2024

Repository files navigation

Central repository for work on libp2p

dependency status Crates.io docs.rs docs.rs master

This repository is the central place for Rust development of the libp2p spec.

Getting started

Repository Structure

The main components of this repository are structured as follows:

  • core/: The implementation of libp2p-core with its Transport and StreamMuxer API on which almost all other crates depend.

  • transports/: Implementations of transport protocols (e.g. TCP) and protocol upgrades (e.g. for authenticated encryption, compression, ...) based on the libp2p-core Transport API.

  • muxers/: Implementations of the StreamMuxer interface of libp2p-core, e.g. (sub)stream multiplexing protocols on top of (typically TCP) connections. Multiplexing protocols are (mandatory) Transport upgrades.

  • swarm/: The implementation of libp2p-swarm building on libp2p-core with the central interfaces NetworkBehaviour and ConnectionHandler used to implement application protocols (see protocols/).

  • protocols/: Implementations of application protocols based on the libp2p-swarm APIs.

  • misc/: Utility libraries.

  • libp2p/examples/: Worked examples of built-in application protocols (see protocols/) with common Transport configurations.

Community Guidelines

The libp2p project operates under the IPFS Code of Conduct.

tl;dr

  • Be respectful.
  • We're here to help: [email protected]
  • Abusive behavior is never tolerated.
  • Violations of this code may result in swift and permanent expulsion from the IPFS [and libp2p] community.
  • "Too long, didn't read" is not a valid excuse for not knowing what is in this document.

Maintainers

(In alphabetical order.)

  • João Oliveira (@jxs)

Notable users

(open a pull request if you want your project to be added here)

  • COMIT - Bitcoin–Monero Cross-chain Atomic Swap.
  • Forest - An implementation of Filecoin written in Rust.
  • fuel-core - A Rust implementation of the Fuel protocol.
  • HotShot - Decentralized sequencer in Rust developed by Espresso Systems.
  • ipfs-embed - A small embeddable ipfs implementation used and maintained by Actyx.
  • Homestar - An InterPlanetary Virtual Machine (IPVM) implementation used and maintained by Fission.
  • beetle - Next-generation implementation of IPFS for Cloud & Mobile platforms.
  • Lighthouse - Ethereum consensus client in Rust.
  • Locutus - Global, observable, decentralized key-value store.
  • OpenMina - In-browser Mina Rust implementation.
  • rust-ipfs - IPFS implementation in Rust.
  • Safe Network - Safe Network implementation in Rust.
  • Starcoin - A smart contract blockchain network that scales by layering.
  • Subspace - Subspace Network reference implementation
  • Substrate - Framework for blockchain innovation, used by Polkadot.
  • Taple - Sustainable DLT for asset and process traceability by OpenCanarias.
  • Ceylon - A Multi-Agent System (MAS) Development Framwork.

About

The Rust Implementation of the libp2p networking stack.

Resources

License

Security policy

Stars

Watchers

Forks

Languages

  • Rust 99.6%
  • Other 0.4%