NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io
crates.io, #2484 most downloaded on crates.io
Peer-to-peer networking library
Latest stable
0.57.1
Last release 1 months ago
15 Oct 2026
Release timing varies
gaps range from 9 days to 1.2 years
Nearly every release is documented
notes for 57 of the last 60 stable releases
2 versions withdrawn
withdrawn after publishing
8 years old
106 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
Publish libp2p-peer-store v0.1.0 and include it in libp2p v0.57.1 as a feature
Publish libp2p-peer-store v0.1.0 and include it in libp2p v0.57.1 as a feature
peer-store feature, re-exporting libp2p-peer-store as libp2p::peer_store.
See PR 6689.See individual changelogs for details.
See individual changelogs for details.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
See individual changelogs for details.
See individual changelogs for details.
Notably, we've removed support for async-std in all crates, as async-std has been discontinued. Users should switch to using tokio instead.
For now, we've kept the abstractions for supporting alternative runtimes, although not all parts may be public. Please open an issue if you are planning to support a custom runtime and run into any issues with that..
Thanks to everyone who contributed to the release!
Remove async-std support.
See PR 6074
Remove deprecated Transport::with_bandwidth_logging,
SwarmBuilder::with_bandwidth_logging and TransportExt.
See PR 5766.
Introduce libp2p-webrtc-websys behind webrtc-websys feature flag.
See PR 5819.
Introduce libp2p-peer-store.
See PR 5724.
Make the *-websys variants (libp2p-webrtc-websys, libp2p-websocket-websys, libp2p-webtransport-websys) only available on wasm32 target architecture.
See PR 5891.
Remove TCP from the async-std swarm builder, as async-std support was removed from libp2p-tcp transport.
See PR 5955
Remove QUIC from the async-std swarm builder, as async-std support was removed from libp2p-quic transport.
See PR 5954
Remove DNS from the async-std swarm builder, as async-std support was removed from libp2p-dns transport.
See PR 5959
See individual changelogs for details.
See individual changelogs for details.
Thanks everyone who contributed to it! :heart:
Raise MSRV to 1.83.0. See PR 5650.
Add with_connection_timeout on SwarmBuilder to allow configuration of the connection_timeout parameter.
See PR 5575.
Deprecate void crate.
See PR 5676.
Update default for idle-connection-timeout to 10s. See PR 4967.
Expose swarm builder phase errors. See PR 5726.
Deprecate ConnectionHandler::{InboundOpenInfo, OutboundOpenInfo} associated type.
Previously, users could tag pending sub streams with custom data and retrieve the data
after the substream has been negotiated.
But substreams themselves are completely interchangeable, users should instead track
additional data inside ConnectionHandler after negotiation.
See PR 5242.
<!-- Update to libp2p-core v0.43.0 -->
See individual changelogs for details.
See individual changelogs for details.
See individual changelogs for details.
See individual changelogs for details.
Thanks everyone who contributed to it! :heart:
Update individual crates.
libp2p-kad v0.46.0.libp2p-identify v0.45.0.Raise MSRV to 1.73. See PR 5266.
Implement refactored Transport.
See PR 4568.
Move address_translation from libp2p-core to libp2p-swarm and libp2p-identify. To now get
address translation behaviour, i.e. discovery of extern address (candidates) based on connecting
to other peers, one needs to use libp2p-identify now. This pertains to you if your nodes can be
behind NATs and they aren't aware of their true external address.
See PR 4568.
Use web-time instead of instant.
See PR 5347.
Remove redundant async signature from builder methods. See PR 5468.
See individual changelogs for details.
See individual changelogs for details.
SwarmBuilder::with_bandwidth_metrics after SwarmBuilder::with_websocket.
See PR 4937.See individual changelogs for details.
Some improvments we unfortunately cannot ship in a way that Rust considers a non-breaking change but with every release, we attempt to smoothen the wa…
The most ergonomic version of rust-libp2p yet!
We've been busy again, with over 250 PRs being merged into master since v0.52.0 (excluding dependency updates).
Numerous improvements landed as patch releases since the v0.52.0 release, for example a new, type-safe SwarmBuilder that also encompasses the most common transport protocols:
let mut swarm = libp2p::SwarmBuilder::with_new_identity()
.with_tokio()
.with_tcp(
tcp::Config::default().port_reuse(true).nodelay(true),
noise::Config::new,
yamux::Config::default,
)?
.with_quic()
.with_dns()?
.with_relay_client(noise::Config::new, yamux::Config::default)?
.with_behaviour(|keypair, relay_client| Behaviour {
relay_client,
ping: ping::Behaviour::default(),
dcutr: dcutr::Behaviour::new(keypair.public().to_peer_id()),
})?
.build();
The new builder makes heavy use of the type-system to guide you towards a correct composition of all transports. For example, it is important to compose the DNS transport as a wrapper around all other transports but before the relay transport. Luckily, you no longer need to worry about these details as the builder takes care of that for you! Have a look yourself if you dare here but be warned, the internals are a bit wild :)
Some more features that we were able to ship in v0.52.X patch-releases include:
We always try to ship as many features as possible in a backwards-compatible way to get them to you faster. Often times, these come with deprecations to give you a heads-up about what will change in a future version. We advise updating to each intermediate version rather than skipping directly to the most recent one, to avoid missing any crucial deprecation warnings. We highly recommend you stay up-to-date with the latest version to make upgrades as smooth as possible.
Some improvments we unfortunately cannot ship in a way that Rust considers a non-breaking change but with every release, we attempt to smoothen the way for future upgrades.
#[non_exhaustive] on key enumsWe've identified that adding a new "message" to the ToSwarm enum is a common cause for breaking changes. This enum is used by plugins (i.e. NetworkBehaviours) to communicate with the Swarm. Similarly, the FromSwarm enum is used to inform plugins about state changes. By adding #[non_exhaustive] to these and other enums we enable future additions to be non-breaking changes.
For example, we plan to allow NetworkBehaviours to share addresses of peers they've discovered with each other. Previously, we had to queue this feature until the next breaking change whereas now, we can simply ship it as soon as it is ready!
Thanks to @dhuseby for getting the ball rolling on this one. See PR 4581 for details.
Prior to this release, a protocol (i.e. ConnectionHandler) had to diligently track streams and other state to correctly compute the KeepAlive for the connection. A bug in this computation sometimes caused the connection to be shut down, despite it still being in use by the protocol. Earlier this year, I thought "there is gotta be a better way" and drafted up some ideas. Eventually @mxinden and myself hashed out the key-points around being smart in regards to keeping connections alive:
ping can opt out of this with Stream::ignore_for_keep_alive().ConnectionHandler::connection_keep_alive only comes into effect once a connection would be shut down.
This allows protocols like Circuit Relay V2 to keep the connection alive despite there not being any streams.The nice benefit for you as a user is that connections are shut down more aggressivley, minimizing system resource use. Should you want to keep idle connections alive nonetheless, you can configure an additional delay using libp2p::swarm::Config::with_idle_connection_timeout.
This also makes wiritng your own protocols simpler.
The tracking issue for this effort was #4306 if you wanted to have a closer look. Special thanks to @leonzchang for landing many small PRs that made this possible!
ConnectionHandler::Error!Talking about closing of connections, say goodbye to ConnectionHandler::Error and its related components. It took many months of careful planning, numerous discussions, failed attempts and s-e-v-e-r-a-l refactorings but we finally delete ConnectionHandler::Error with this release.
There's lots to be excited about with this change; let me explain. Deleting ConnectionHandler::Error also means:
SwarmEvent.
No more SwarmEvent<MyBehaviourEvent, Either<Either<Either<Either<Either<io::Error, Void>, io::Error>, io::Error>, Void>, io::Error>, StreamUpgradeError<Void>>, Void>
Just:SwarmEvent<MyBehaviourEvent>
Isn't that neat? :tada:ConnectionHandlerEvent::Close is gone too and together with it, a type parameter on its definition!FromSwarm also as a type-parameter removed which makes it easier and more concise to reference!ConnectionHandler could simply close an entire connection at any point, despite the connection still being in use by other protocols. (Remember that protocols are multiplexed over a single connection.) For example, an error while making a reservation with a relay would lead to the entire relayed connection being closed, even though other protocols might still have been using it.This means more reliable connections and protocol executions as no one is pulling the rug out from underneath your protocol's legs as they run across the wire :running:
tracingProtocols don't actually have legs, Thomas.
That is true. But if we imagine for a moment that they do, using the latest migration to tracing we can now watch them!
I am not sure if @eserilev knew what they were signing up for when they suggested to tackle #1533 back in August. A lot of impressive work and pretty much exactly three months later though, we merged #4282 which:
log to tracingEnough talking, here is a screenshot:
Here we can see what one particular call to Connection::poll actually did. We can see how much time is spent in the respective identify and ping handlers as well as interaction with the stream multiplexer.
We put some consideration in to which spans might be useful but we are excited to hear from users how useful they are and what else might need instrumentation.
PollParameters has been removedA relict from earlier designs of rust-libp2p is finally gone too: PollParameters. The NetworkBehaviour::poll function now just takes a &mut Context as you'd expect it to, without any additional clutter. All features of PollParameters have previously already been deprecated and alternatives were offered in terms of events.
If you enforce no warnings in your codebase, you should be able to just delete that (unused) parameter from the function.
This release would not have been possible without the contributions of many people. Thank you to (in alphabetical order):
As always, a detailed log of changes for every release can be found in our repository: CHANGELOG.md. If you are struggling with an upgrade, feel free to tag Max (@mxinden) or myself (@thomaseizinger) in a PR and we'll try to help.
Happy coding!
libp2p-wasm-ext.
Users should use libp2p-websocket-websys instead.
See PR 4694.libp2p-deflate.
See issue 4522 for details.
See PR 4729.development_transport.
Use libp2p::SwarmBuilder instead.
See PR 4732.SwarmBuilder::with_bandwidth_metrics exposing Prometheus bandwidth metrics per transport protocol stack and direction (in-/ outbound).
Deprecate Transport::with_bandwidth_logging and SwarmBuilder::with_bandwidth_logging in favor of the new SwarmBuilder::with_bandwidth_metrics.
See PR 4727.See individual changelogs for details.
See individual changelogs for details.
Introduce libp2p::websocket_websys module behind websocket-websys feature flag.
This supersedes the existing libp2p::wasm_ext module which is now deprecated.
See PR 3679.
Introduce a new libp2p::SwarmBuilder in favor of the now deprecated libp2p::swarm::SwarmBuilder.
See libp2p::SwarmBuilder docs on how to use the new builder.
Also see PR 4120.
Update libp2p-identity version to 0.2.6.
Under the hood, we feature-flagged libp2p-identity's rand dependency but it is enabled by default when using libp2p.
See PR 4349.
See individual changelogs for details.
See individual changelogs for details.
See individual changelogs for details.
See individual changelogs for details.
See individual changelogs for details.
libp2p-webtransport-websys providing WebTransport for WASM environments.
See PR 4015.Supporting additional patterns introduced significant complexity to the codebase. We decided to deprecate and remove them. This significantly reduced…
Let's get the biggest one out the way first, I promise the other points are easier explained but equally exciting. The tl;dr is: Healthier Kademlia routing tables and an improved developer experience.
If you don't know about Kademlia's client/server mode, checkout the specs.
With the v0.52 release, rust-libp2p automatically configures Kademlia in client or server mode depending on our external addresses. If we have a confirmed, external address, we will operate in server-mode, otherwise client-mode. This is entirely configuration-free (yay!) although follow-up work is under-way to allow setting this manually in certain situations: #4074.
We can now do the following:
ConnectionEvent::LocalProtocolsChange.libp2p-identify picks up this change and pushes it to all connected remote nodes.To implement this, several other features/issues had to be fixed. If you are interested in the details, read on:
Simplify the scoring mechanism of external addresses: #3954
As a consequence, the observed address reported by identify is no longer considered an external address but just an address candidate. Checkout the changelog-entry for a way of restoring the old behaviour.
Changes to the supported protocols are now detected at runtime and communicated to all protocols: #3651.
Previously, a protocol could retrieve the supported protocols via PollParameters::supported_protocols. This list however was computed at start-up and was static. Now, ConnectionEvent has two new variants:
pub enum ConnectionEvent<'a> {
// existing variants omitted ...
/// The local [`ConnectionHandler`] added or removed support for one or more protocols.
LocalProtocolsChange(ProtocolsChange<'a>),
/// The remote [`ConnectionHandler`] now supports a different set of protocols.
RemoteProtocolsChange(ProtocolsChange<'a>),
}
pub enum ProtocolsChange<'a> {
Added(ProtocolsAdded<'a>),
Removed(ProtocolsRemoved<'a>),
}
ProtocolsAdded and ProtocolsRemoved are iterators over a (new) type called StreamProtocol.
Protocols are now enforced to be valid UTF-8 strings: #3746.
This was always the case in the specs but the rust-libp2p implementation was lagging behind here and improperly represented them as bytes internally.
Local changes to our protocols (i.e. a node going from Kademlia server to client mode) are now immediately pushed to the remote via the /ipfs/id/push/1.0.0 protocol: #3980.
Not only does this work out-of-the-box and thus improves the developer experience of rust-libp2p, it should also result in a much more useful and up-to-date routing table for all nodes on a Kademlia DHT.
/p2p multiaddressesThe /p2p protocol of multiaddresses specifies the identity of a peer in the form of a PeerId such as 12D3KooWETLZBFBfkzvH3BQEtA1TJZPmjb4a18ss5TpwNU7DHDX6. Yet for the longest time, the type-definition of the /p2p protocol looked like this:
pub enum Protocol<'a> {
// omitted other variants ...
P2p(Multihash),
}
Every PeerId is a valid Multihash but not vice-versa. Dang! That is a lot of "impossible" errors that the type-system should avoid.
Thanks to a lot of work, it now looks like this:
pub enum Protocol<'a> {
// omitted other variants ...
P2p(PeerId),
}
Naming is hard and humans are creatures of habit. Thus, once familiar with certain names, it is often hard to see how they make absolutely no sense at all to newcomers.
In the v0.52 release we renamed several associated types and enums which hopefully make the message-passing system implemented in rust-libp2p easier to grasp.
A quick recap:
NetworkBehaviour represent a protocol's state across all peers and connections.ConnectionHandler represents a protocol's state for a single connection to a peer.NetworkBehaviours are composed into a tree using #[derive(NetworkBehaviour)] and run inside a SwarmNetworkBehaviours can emit events to the Swarm. This used to be called OutEvent. Now, its aptly named ToSwarm:
pub trait NetworkBehaviour {
type ToSwarm;
// functions and other types omitted ...
}
Returning one of these events was previously done with a NetworkBehaviourAction::GenerateEvent, a type-name so long you were grateful for autocomplete. These actions are essentially commands that are issued to the swarm. What could possibly be a good name for that? I present:
pub enum ToSwarm<TOutEvent, TInEvent> {
GenerateEvent(TOutEvent),
// other variants omitted ..
}
We followed the same strategy for ConnectionHandler. A ConnectionHandler can receive messages from a NetworkBehaviour via ToSwarm::NotifyHandler (gosh, that was so much easier to write, why didn't we do this earlier?) and send message to its NetworkBehaviour. The associated types defining these messages are now called ToBehaviour and FromBehaviour, representing where the message is going / coming from. Previously, they carried the generic names InEvent and OutEvent which had me utterly confused when I first started working on rust-libp2p.
To wrap it all up, the ConnectionHandlerEvent::Custom variant is now called ConnectionHandlerEvent::NotifyBehaviour, making it clear what happens to types returned here.
Oh, isn't this one of my favourites!
Ever wondered why ConnectionHandlerUpgrErr had what felt like 10 layers of nested enums? So did we and went ahead and fixed this in #3882.
This is what it looked like before:
pub enum ConnectionHandlerUpgrErr<TUpgrErr> {
Timeout,
Timer,
Upgrade(UpgradeError<TUpgrErr>),
}
pub enum UpgradeError<E> {
Select(NegotiationError),
Apply(E),
}
pub enum NegotiationError {
ProtocolError(ProtocolError),
Failed,
}
pub enum ProtocolError {
IoError(io::Error),
InvalidMessage,
InvalidProtocol,
TooManyProtocols,
}
Now, it looks like this:
pub enum StreamUpgradeError<TUpgrErr> {
Timeout,
Apply(TUpgrErr),
NegotiationFailed,
Io(io::Error),
}
But that is not it!
Previously, we would give you one of these ConnectionHandlerUpgrErr when an inbound stream failed. But, what exactly does ProtocolError::InvalidMessage for example mean for an inbound stream? How would we even figure out, which protocol (read ConnectionHandler) this should be dispatched to if we failed to negotiate the protocols?
Well, you might have guessed it. It is impossible to dispatch this to the correct one, so we just informed all protocols. But that was pretty useless. If we don't know, which stream a protocol belongs to, we shouldn't just inform all of them. Thus, in #3605 we stopped this which removes several "impossible" error paths.
Since its introduction, the libp2p-noise crate supported a wide range of handshake patterns. The libp2p specs however only documents the XX handshake: libp2p/specs/noise.
Supporting additional patterns introduced significant complexity to the codebase. We decided to deprecate and remove them. This significantly reduced the complexity of the libp2p-noise implementation (-1000 LoC!). Additionally, it allowed us to finally adopt the naming conventions we have been pursuing across the workspace for libp2p-noise.
Using the noise handshake is now as simple as:
let config = libp2p::noise::Config::new(&keypair).unwrap();
A simple, yet impactful contribution was made by @dgarus in #3952:
libp2p::request_response::cbor::Behaviour<Req, Res>libp2p::request_response::json::Behaviour<Req, Res>These two, new type-aliases come with a pre-configured CBOR/JSON codec and only need to be parameterised by the Req and Res types. The only requirement is that the types implement serde::{Serialize,Deserialize}. Defining a request-response protocol has never been easier in rust-libp2p!
As with any code that serializes data structures, be aware that any changes to it can easily be breaking and thus not backwards-compatible with older versions.
Despite still being in alpha, our QUIC implementation can now establish direct connections across certain NATs, i.e. hole-punching! This was contributed by @arpankapoor in #3964.
You don't need to configure anything special besides the dcutr behaviour. See the dcutr-example in our repository for details.
A big thanks to all people that contributed to this release. In alphabetical order:
Well done for making it to the end!
As always, a detailed log of changes for every release can be found in our repository: CHANGELOG.md. If you are struggling with an upgrade, feel free to tag Max (@mxinden) or myself (@thomaseizinger) in a PR and we'll try to help.
Happy coding!
Raise MSRV to 1.65. See PR 3715.
Protocol names are now required to be valid UTF8 strings.
We delete the ProtocolName trait from libp2p::core and replace it with a requirement for AsRef<str>.
At the same time, we introduce StreamProtocol, a newtype in libp2p::swarm.
This newtype enforces additional variants like a leading forward-slash.
We encourage users to use StreamProtocol when implementing UpgradeInfo.
See PR 3746.
Rename NetworkBehaviour::OutEvent to NetworkBehaviour::ToSwarm, ConnectionHandler::InEvent to ConnectionHandler::FromBehaviour, ConnectionHandler::OutEvent to ConnectionHandler::ToBehaviour. See PR 3848.
Remove deprecated mplex module.
You can still depend on libp2p-mplex directly but we strongly encourage to migrate to yamux.
This also removes mplex from the development_transport and tokio_development_transport functions.
See PR 3920.
Remove libp2p-perf protocol. To use libp2p-perf one needs to import it directly.
See PR 3990.
Remove libp2p-quic and libp2p-webrtc protocols.
These are in alpha status and should be depended on directly.
See PR 4041.
Nothing published for this version
See individual changelogs for details.
See individual changelogs for details.
mplex feature.
The recommended baseline stream multiplexer is yamux.
See PR 3689.See individual changelogs for details.
See individual changelogs for details.
Introduce libp2p::connection_limits module.
See PR 3386.
Deprecate the quic and webrtc feature.
These two crates are only in alpha state.
To properly communicate this to users, we want them to add the dependency directly which makes the alpha version visible.
See PR 3580.
Introduce libp2p::allow_block_list module and deprecate libp2p::Swarm::ban_peer_id.
See PR 3590.
Introduce libp2p::perf module.
See PR 3693.
See individual changelogs for details.
See individual changelogs for details.
Depend on libp2p-tls v0.1.0.
Introduce ed25519 feature.
For backwards-compatibility, the ed25519 identity keys are still available without activating this feature.
However, going forward, you should explicitly activate it to avoid compile errors going forward.
See PR 3350.
Large release. See individual changelogs for details.
Large release. See individual changelogs for details.
Thanks to the many folks involved!
Enable NetworkBehaviours to manage connections.
This deprecates NetworkBehaviour::new_handler and NetworkBehaviour::addresses_of_peer.
Due to limitations in the Rust compiler, these deprecations may not show up for you, nevertheless they will be removed in a future release.
See libp2p-swarm's CHANGELOG for details.
Count bandwidth at the application level. Previously BandwidthLogging would implement Transport and now implements StreamMuxer (PR 3180).
BandwidthLogging::new now requires a 2nd argument: Arc<BandwidthSinks>BandwidthFutureBandwidthConnecLogging to InstrumentedStreamRemove SimpleProtocol due to being unused. See libp2p::core::upgrade for alternatives. See PR 3191.
Bump MSRV to 1.65.0.
Update individual crates.
Update to libp2p-dcutr v0.9.0.
Update to libp2p-ping v0.42.0.
Update to libp2p-request-response v0.24.0.
Update to libp2p-kad v0.43.0.
Update to libp2p-floodsub v0.42.0.
Update to libp2p-autonat v0.10.0.
Update to libp2p-relay v0.15.0.
Update to libp2p-identify v0.42.0.
Update to libp2p-rendezvous v0.12.0.
Update to libp2p-metrics v0.12.0.
Update to libp2p-swarm v0.42.0.
Update to libp2p-mdns v0.43.0.
Update to libp2p-gossipsub v0.44.0.
Update to libp2p-yamux v0.43.0.
Update to libp2p-mplex v0.39.0.
Update to libp2p-wasm-ext v0.39.0.
Update to libp2p-plaintext v0.39.0.
Update to libp2p-noise v0.42.0.
Update to libp2p-core v0.39.0.
Nothing published for this version
> This is a large release. After > 4 years, rust-libp2p ships with an [(alpha) QUIC
This is a large release. After > 4 years, rust-libp2p ships with an (alpha) QUIC implementation. The necessary TLS logic is extracted into its own crate, and can thus be used detached from QUIC, e.g. on top of TCP as an alternative to Noise. In addition to these two transports, this release adds a third, namely WebRTC (browser-to-server). But that is definitely not it. See below for the many other changes packed into this release.
See individual changelogs for details.
Thanks to the many folks involved!
This is a large release. After > 4 years, rust-libp2p ships with an (alpha) QUIC implementation. The necessary TLS logic is extracted into its own crate, and can thus be used detached from QUIC, e.g. on top of TCP as an alternative to Noise. In addition to these two transports, this release adds a third, namely WebRTC (browser-to-server). But that is definitely not it. See below for the many other changes packed into this release.
libp2p-tls v0.1.0-alpha. See PR 2945.libp2p-quic v0.7.0-alpha. See PR 2289.libp2p-webrtc v0.4.0-alpha. See PR 2289.tcp-tokio, mdns-tokio, dns-tokio, tcp-async-io, mdns-async-io, dns-async-std.
See PR 3001.NetworkBehaviour macro export from root crate in favor of re-exported macro from libp2p::swarm.
Change your import from libp2p::NetworkBehaviour to libp2p::swarm::NetworkBehaviour. See PR 3055.NetworkBehaviour macro behind macros feature flag. See PR 3055.libp2p-autonat v0.89.0.libp2p-core v0.38.0.libp2p-dcutr v0.8.0.libp2p-deflate v0.38.0.libp2p-dns v0.38.0.libp2p-floodsub v0.41.0.libp2p-gossipsub v0.43.0.libp2p-identify v0.41.0.libp2p-kad v0.42.0.libp2p-mdns v0.42.0.libp2p-metrics v0.11.0.libp2p-mplex v0.38.0.libp2p-noise v0.41.0.libp2p-ping v0.41.0.libp2p-plaintext v0.38.0.libp2p-pnet v0.22.2.libp2p-relay v0.14.0.libp2p-rendezvous v0.11.0.libp2p-request-response v0.23.0.libp2p-swarm v0.41.0.libp2p-tcp v0.38.0.libp2p-uds v0.37.0.libp2p-wasm-ext v0.38.0.libp2p-websocket v0.40.0.libp2p-yamux v0.42.0.This is a large release with a couple of breaking changes. As always, please read the changelogs.
This is a large release with a couple of breaking changes. As always, please read the changelogs.
Feel free to tag us (maintainers) on your upgrade pull request for a review or general help.
Thanks to the many folks involved!
Remove default features. You need to enable required features explicitly now. As a quick workaround, you may want to use the
new full feature which activates all features. See PR 2918.
Introduce tokio and async-std features and deprecate the following ones:
tcp-tokio in favor of tcp + tokiomdns-tokio in favor of mdns + tokiodns-tokio in favor of dns + tokiotcp-async-io in favor of tcp + async-stdmdns-async-io in favor of mdns + async-stddns-async-std in favor of dns + async-stdSee PR 2962.
Update individual crates.
libp2p-autonat v0.8.0.libp2p-core v0.37.0.libp2p-dcutr v0.7.0.libp2p-deflate v0.37.0.libp2p-dns v0.37.0.libp2p-floodsub v0.40.0.libp2p-gossipsub v0.42.0.libp2p-identify v0.40.0.libp2p-kad v0.41.0.libp2p-mdns v0.41.0.libp2p-metrics v0.10.0.libp2p-mplex v0.37.0.libp2p-noise v0.40.0.libp2p-ping v0.40.0.libp2p-plaintext v0.37.0.libp2p-relay v0.13.0.libp2p-rendezvous v0.10.0.libp2p-request-response v0.22.0.libp2p-swarm-derive v0.30.1.libp2p-swarm v0.40.0.libp2p-tcp v0.37.0.libp2p-uds v0.36.0.libp2p-wasm-ext v0.37.0.libp2p-websocket v0.39.0.libp2p-yamux v0.41.0.> Remove deprecated NetworkBehaviourEventProcess. See [libp2p-swarm v0.38.0 changelog entry] for migration path.
Most notable changes:
Remove deprecated
NetworkBehaviourEventProcess. See libp2p-swarm v0.38.0 changelog entry for migration path.
Make RSA keypair support optional. To enable RSA support,
rsafeature should be enabled. See PR 2860.
Allow users to choose between async-io and tokio runtime in the mdns protocol implementation.
async-iois a default feature, with an additionaltokiofeature (see PR 2748)
For all other changes, see individual changelogs for details.
Thanks to the many folks involved!
Update to libp2p-core v0.36.0.
Update to libp2p-swarm-derive v0.30.0.
Update to libp2p-dcutr v0.6.0.
Update to libp2p-rendezvous v0.9.0.
Update to libp2p-ping v0.39.0.
Update to libp2p-identify v0.39.0.
Update to libp2p-floodsub v0.39.0.
Update to libp2p-relay v0.12.0.
Update to libp2p-metrics v0.9.0.
Update to libp2p-kad v0.40.0.
Update to libp2p-autonat v0.7.0.
Update to libp2p-request-response v0.21.0.
Most notable change is the deprecation of NetworkBehaviourEventProcess. See corresponding changelog entry on how to migrate.
Most notable change is the deprecation of NetworkBehaviourEventProcess. See corresponding changelog entry on how to migrate.
Also rust-libp2p v0.47.0 updates to prost v0.11.0 which no longer installs the protoc Protobuf compiler. Thus to build rust-libp2p you will need protoc installed locally. On CI you can use the arduino/setup-protoc GitHub action:
- name: Install Protoc
uses: arduino/setup-protoc@v1
For all other changes, see individual changelogs for details.
Update to libp2p-dcutr v0.5.0.
Update to libp2p-derive v0.29.0.
Update to libp2p-rendezvous v0.8.0.
Update to libp2p-ping v0.38.0.
Update to libp2p-identify v0.38.0.
Update to libp2p-floodsub v0.38.0.
Update to libp2p-relay v0.11.0.
Update to libp2p-metrics v0.8.0.
Update to libp2p-kad v0.39.0.
Update to libp2p-autonat v0.6.0.
Update to libp2p-request-response v0.20.0.
Update to libp2p-swarm v0.38.0.
See individual changelogs for details.
See individual changelogs for details.
Small on the surface, though containing many internal refactorings. Shout out to @elenaf9 and @thomaseizinger!
Small on the surface, though containing many internal refactorings. Shout out to @elenaf9 and @thomaseizinger!
See individual changelogs for details.
1.56.1 to 1.60.0 . See PR 2646.libp2p-autonat v0.5.0.libp2p-core v0.34.0.libp2p-dcutr v0.4.0.libp2p-floodsub v0.37.0.libp2p-identify v0.37.0.libp2p-kad v0.38.0.libp2p-metrics v0.7.0.libp2p-mplex v0.34.0.libp2p-noise v0.37.0.libp2p-ping v0.37.0.libp2p-plaintext v0.34.0.libp2p-relay v0.10.0.libp2p-rendezvous v0.7.0.libp2p-request-response v0.19.0.libp2p-swarm v0.37.0.libp2p-wasm-ext v0.34.0.libp2p-yamux v0.38.0.libp2p-uds v0.33.0.See individual changelogs for details.
See individual changelogs for details.
libp2p-dcutr v0.3.1.libp2p-identify v0.36.1.libp2p-kad v0.37.1.libp2p-relay v0.9.1.libp2p-swarm v0.36.1.Medium size release. See individual changelogs for details.
Medium size release. See individual changelogs for details.
libp2p-plaintext v0.33.0.libp2p-noise v0.36.0.libp2p-wasm-ext v0.33.0.libp2p-yamux v0.37.0.libp2p-mplex v0.33.0.libp2p-dcutr v0.3.0.libp2p-rendezvous v0.6.0.libp2p-ping v0.36.0.libp2p-identify v0.36.0.libp2p-floodsub v0.36.0.libp2p-relay v0.9.0.libp2p-metrics v0.6.0.libp2p-kad v0.37.0.libp2p-autonat v0.4.0.libp2p-request-response v0.18.0.libp2p-swarm v0.36.0.libp2p-core v0.33.0.Small release. See individual changelogs for details.
Small release. See individual changelogs for details.
libp2p-dcutr v0.2.0.libp2p-dns v0.32.1.libp2p-rendezvous v0.5.0.libp2p-ping v0.35.0.libp2p-identify v0.35.0.libp2p-floodsub v0.35.0.libp2p-relay v0.8.0.libp2p-metrics v0.5.0.libp2p-kad v0.36.0.libp2p-autonat v0.3.0.libp2p-request-response v0.17.0.libp2p-swarm v0.35.0.Medium size release, containing many internal refactorings as well as the last missing piece of basic hole punching, namely libp2p-dcutr. To try out h
Medium size release, containing many internal refactorings as well as the last missing piece of basic hole punching, namely libp2p-dcutr. To try out hole punching yourself, follow the tutorial.
Most notable breaking changes:
Fold
libp2p-core'sNetworkintoSwarm. See [PR 2492].
Along with this change, many types are now exposed through libp2p-swarm instead of libp2p-core. When in doubt, change libp2p::core:: to libp2p::swarm::.
Merge NetworkBehaviour's inject_* paired methods (see PR 2445).
- Rename
ProtocolsHandlertoConnectionHandler. Upgrade should be as simple as renaming all occurences ofProtocolsHandlertoConnectionHandlerwith your favorite text manipulation tool across your codebase. See [PR 2527].
See individual changelogs for details.
Update individual crates.
libp2p-autonat v0.2.0.libp2p-core v0.32.0.libp2p-deflate v0.32.0.libp2p-dns v0.32.0.libp2p-floodsub v0.34.0.libp2p-gossipsub v0.36.0.libp2p-identify v0.34.0.libp2p-kad v0.35.0.libp2p-mdns v0.35.0.libp2p-metrics v0.4.0.libp2p-mplex v0.32.0.libp2p-noise v0.35.0.libp2p-ping v0.34.0.libp2p-plaintext v0.32.0.libp2p-relay v0.7.0.libp2p-rendezvous v0.4.0.libp2p-request-response v0.16.0.libp2p-swarm v0.34.0.libp2p-derive v0.27.0.libp2p-tcp v0.32.0.libp2p-uds v0.32.0.libp2p-wasm-ext v0.32.0.libp2p-websocket v0.34.0.libp2p-yamux v0.36.0.Update to parking_lot v0.12.0. See PR 2463.
Drop support for gossipsub in the wasm32-unknown-unknown target (see PR 2506).
See individual changelogs for details.
See individual changelogs for details.
See individual changelogs for details.
See individual changelogs for details.
Larger release, among many other things adding most of the components required for hole-punching.
Larger release, among many other things adding most of the components required for hole-punching.
See individual changelogs for details.
Update individual crates.
libp2p-autonat
libp2p-core
libp2p-deflate
libp2p-dns
libp2p-floodsub
libp2p-gossipsub
libp2p-identify
libp2p-kad
libp2p-mdns (breaking compatibility with previous versions)
libp2p-metrics
libp2p-mplex
libp2p-noise
libp2p-ping
libp2p-plaintext
libp2p-relay
libp2p-rendezvous
libp2p-request-response
libp2p-swarm-derive
libp2p-swarm
libp2p-tcp
libp2p-uds
libp2p-wasm-ext
libp2p-websocket
libp2p-yamux
Migrate to Rust edition 2021 (see PR 2339).
Nothing published for this version
See https://github.com/libp2p/rust-libp2p/pull/2427.
See https://github.com/libp2p/rust-libp2p/pull/2427.
Small release most notably improving WASM support.
Small release most notably improving WASM support.
See individual changelogs for details.
libp2p-floodsublibp2p-gossipsublibp2p-identifylibp2p-kadlibp2p-mdnslibp2p-metricslibp2p-pinglibp2p-relaylibp2p-rendezvouslibp2p-request-responselibp2p-swarm-derivelibp2p-swarmlibp2p-websocketwasm-bindgen feature to futures-timer, instant, parking_lot, getrandom/js and rand/wasm-bindgen.See individual changelogs for details.
See individual changelogs for details.
This is a large release consisting of many small changes. As always, please raise any questions you might have here on this GitHub repository. In addition, feel free to tag @mxinden on the pull request updating your project to v0.40.0 for review.
Update individual crates.
libp2p-corelibp2p-deflatelibp2p-dnslibp2p-floodsublibp2p-gossipsublibp2p-identifylibp2p-kadlibp2p-mdnslibp2p-mplexlibp2p-noiselibp2p-pinglibp2p-plaintextlibp2p-relaylibp2p-request-responselibp2p-swarmlibp2p-tcplibp2p-udslibp2p-wasm-extlibp2p-websocketlibp2p-yamuxRe-export the wasm-bindgen feature from parking_lot, so
libp2p users can opt-in to that crate's Wasm support. See PR 2180.
Add libp2p-metrics.
Nothing published for this version
Nothing published for this version
Nothing published for this version
See individual changelogs for details.
See individual changelogs for details.
- Update individual crates. - libp2p-core - libp2p-deflate - libp2p-dns - libp2p-floodsub - libp2p-gossipsub - libp2p-identify - libp2p-kad - libp2p-m
libp2p-corelibp2p-deflatelibp2p-dnslibp2p-floodsublibp2p-gossipsublibp2p-identifylibp2p-kadlibp2p-mdnslibp2p-mplexlibp2p-noiselibp2p-pinglibp2p-plaintextlibp2p-relaylibp2p-request-responselibp2p-swarmlibp2p-tcplibp2p-udslibp2p-wasm-extlibp2p-websocketlibp2p-yamuxSee individual changelogs for details.
See individual changelogs for details.
libp2p-corelibp2p-gossipsublibp2p-noiselibp2p-pnetlibp2p-wasm-extSee individual changelogs for details.
See individual changelogs for details.
Drop support for wasm32-unknown-unknown in favor of wasm32-unknown-emscripten and wasm32-wasi PR 2038.
Update individual crates.
libp2p-corelibp2p-dnslibp2p-floodsublibp2p-gossipsublibp2p-kadlibp2p-mdnslibp2p-pinglibp2p-relaylibp2p-request-responselibp2p-swarmlibp2p-wasm-extlibp2p-yamuxDrop support for wasm32-unknown-unknown in favor of
wasm32-unknown-emscripten and wasm32-wasi PR
2038.
See individual changelogs for details.
See individual changelogs for details.
Consolidate top-level utility functions for constructing development
transports. There is now just development_transport() (available with default features)
and tokio_development_transport() (available when the corresponding tokio features are enabled).
Furthermore, these are now async fns. The minor variations that also included pnet
support have been removed.
PR 1927
Update libp2p crates.
Do not leak default features from libp2p crates. PR 1986.
Add libp2p-relay to libp2p facade crate.
Update libp2p-yamux to latest patch version.
libp2p-yamux to latest patch version.Use libp2p-swarm-derive, the former libp2p-core-derive.
Use libp2p-swarm-derive, the former libp2p-core-derive.
Update libp2p-deflate, libp2p-gossipsub, libp2p-mdns, libp2p-request-response,
libp2p-swarm and libp2p-tcp.
Update libp2p-core and all dependent crates.
Update libp2p-core and all dependent crates.
The tcp-async-std feature is now tcp-async-io, still
enabled by default.
Update libp2p-core and all dependent crates.
libp2p-core and all dependent crates.- Update libp2p-websocket.
libp2p-websocket.Update minimum patch version of libp2p-websocket.
libp2p-websocket.Update libp2p-request-response.
Update libp2p-request-response.
Update to libp2p-mdns-0.26.
Update libp2p-websocket minimum patch version.
Bump minimum libp2p-core patch version.
libp2p-core patch version.Bump minimum libp2p-tcp patch version.
libp2p-tcp patch version.Update multistream-select and all dependent crates.
multistream-select and all dependent crates.- Update libp2p-plaintext.
libp2p-plaintext.Rust-libp2p versions in combination with `multihash` `< v0.11.3` are vulnerable to DoS attacks. Given that e.g. `PeerId::from_bytes` is called with un…
Among other changes, this release adds a requirement across all crates for multihash >= v0.11.3. Rust-libp2p versions in combination with multihash < v0.11.3 are vulnerable to DoS attacks. Given that e.g. PeerId::from_bytes is called with unsanitized data from possibly untrusted sources this call can panic with multihash < v0.11.3 see RustSec for details.
In case you run libp2p in untrusted environments please either (a) update to libp2p v0.30.0 or (b) make sure to run with multihash >=v0.11.3 via your downstream Cargo.lock file.
As always all other contained changes are listed in our CHANGELOG.md.
libp2p-mdns, libp2p-tcp and libp2p-uds as well as libp2p-core
and all its dependers.- Update libp2p-core.
libp2p-core.Update libp2p-core, libp2p-floodsub, libp2p-gossipsub, libp2p-mplex, libp2p-noise, libp2p-plaintext, libp2p-pnet, libp2p-request-response, libp2p-swar
libp2p-core, libp2p-floodsub, libp2p-gossipsub, libp2p-mplex,
libp2p-noise, libp2p-plaintext, libp2p-pnet, libp2p-request-response,
libp2p-swarm, libp2p-tcp, libp2p-websocket and parity-multiaddr.One column per quarter.