Skip to content

Releases: paritytech/litep2p

v0.11.1

28 Oct 13:47
v0.11.1
3f13b10

Choose a tag to compare

[0.11.1] - 2025-10-28

This release ensures that polling the yamux controller after an error does not lead to unexpected behavior.

Fixed

  • yamux/control: Ensure poll next inbound is not called after errors (#445)

v0.11.0

20 Oct 12:00
v0.11.0
8a02398

Choose a tag to compare

[0.11.0] - 2025-10-20

This release adds support for RSA remote network identity keys gated behind rsa feature. It also fixes mDNS initialization in the environment with no multicast addresses available and Bitswap compatibility with kubo IPFS client >= v0.37.0.

Added

  • Support RSA remote network identity keys (#423)

Fixed

  • bitswap: Reuse inbound substream for subsequent requests (#447)
  • mDNS: Do not fail initialization if the socket could not be created (#434)
  • Make RemotePublicKey public to enable signature verification (#435)
  • improve error handling in webRTC-related noise function (#377)

Changed

  • Upgrade rcgen 0.10.0 -> 0.14.5 (#450)
  • chore: update str0m dependency, update code based on breaking changes (#422)

v0.10.0

22 Jul 10:44
v0.10.0
a950f7a

Choose a tag to compare

[0.10.0] - 2025-07-22

This release adds the ability to use system DNS resolver and change Kademlia DNS memory store capacity. It also fixes the Bitswap protocol implementation and correctly handles the dropped notification substreams by unregistering them from the protocol list.

Added

  • kad: Expose memory store configuration (#407)
  • transport: Allow changing DNS resolver config (#384)

Fixed

  • notification: Unregister dropped protocols (#391)
  • bitswap: Fix protocol implementation (#402)
  • transport-manager: stricter supported multiaddress check (#403)

v0.9.5

10 Jun 14:53
v0.9.5
8a5420a

Choose a tag to compare

[0.9.5] - 2025-05-26

This release primarily focuses on strengthening the stability of the websocket transport. We've resolved an issue where higher-level buffering was causing the Noise protocol to fail when decoding messages.

We've also significantly improved connectivity between litep2p and Smoldot (the Substrate-based light client). Empty frames are now handled correctly, preventing handshake timeouts and ensuring smoother communication.

Finally, we've carried out several dependency updates to keep the library current with the latest versions of its underlying components.

Fixed

  • substream/fix: Allow empty payloads with 0-length frame (#395)
  • websocket: Fix connection stability on decrypt messages (#393)

Changed

  • crypto/noise: Show peerIDs that fail to decode (#392)
  • cargo: Bump yamux to 0.13.5 and tokio to 1.45.0 (#396)
  • ci: Enforce and apply clippy rules (#388)
  • build(deps): bump ring from 0.16.20 to 0.17.14 (#389)
  • Update hickory-resolver 0.24.2 -> 0.25.2 (#386)

v0.9.4

15 May 13:23
v0.9.4
6d61e2b

Choose a tag to compare

[0.9.4] - 2025-04-29

This release brings several improvements and fixes to litep2p, advancing its stability and readiness for production use.

Performance Improvements

This release addresses an issue where notification protocols failed to exit on handle drop, lowering CPU usage in scenarios like minimal-relay-chains from 7% to 0.1%.

Robustness Improvements

  • Kademlia:

    • Optimized address store by sorting addresses based on dialing score, bounding memory consumption and improving efficiency.
    • Limited FIND_NODE responses to the replication factor, reducing data stored in the routing table.
    • Address store improvements enhance robustness against routing table alterations.
  • Identify Codec:

    • Enhanced message decoding to manage malformed or unexpected messages gracefully.
  • Bitswap:

    • Introduced a write timeout for sending frames, preventing protocol hangs or delays.

Testing and Reliability

  • Fuzzing Harness: Added a fuzzing harness by SRLabs to uncover and resolve potential issues, improving code robustness. Thanks to @R9295 for the contribution!

  • Testing Enhancements: Improved notification state machine testing. Thanks to Dominique (@Imod7) for the contribution!

Dependency Management

  • Updated all dependencies for stable feature flags (default and "websocket") to their latest versions.

  • Reorganized dependencies under specific feature flags, shrinking the default feature set and avoiding exposure of outdated dependencies from experimental features.

Fixed

  • notifications: Exit protocols on handle drop to save up CPU of minimal-relay-chains (#376)
  • identify: Improve identify message decoding (#379)
  • crypto/noise: Set timeout limits for the noise handshake (#373)
  • kad: Improve robustness of addresses from the routing table (#369)
  • kad: Bound kademlia messages to the replication factor (#371)
  • codec: Decode smaller payloads for identity to None (#362)

Added

  • bitswap: Add write timeout for sending frames (#361)
  • notif/tests: check test state (#360)
  • SRLabs: Introduce simple fuzzing harness (#367)
  • SRLabs: Introduce Fuzzing Harness (#365)

Changed

  • features: Move quic related dependencies under feature flag (#359)
  • tests/substrate: Remove outdated substrate specific conformace testing (#370)
  • ci: Update stable dependencies (#375)
  • build(deps): bump hex-literal from 0.4.1 to 1.0.0 (#381)
  • build(deps): bump tokio from 1.44.1 to 1.44.2 in /fuzz/structure-aware (#378)
  • build(deps): bump Swatinem/rust-cache from 2.7.7 to 2.7.8 (#363)
  • build(deps): bump tokio from 1.43.0 to 1.43.1 (#368)
  • build(deps): bump openssl from 0.10.70 to 0.10.72 (#366)

v0.9.3

15 May 13:21
v0.9.3
28087ae

Choose a tag to compare

[0.9.3] - 2025-03-11

This release introduces an API for setting the maximum kademlia message size.

Changed

  • kad: Set upper limits for kademlia messages (#357)

v0.9.2

15 May 13:20
v0.9.2
22b19c8

Choose a tag to compare

[0.9.2] - 2025-03-10

This release downgrades a spamming log message to debug level and adds tests for the WebSocket stream implementation.

Thanks to @dharjeezy for contributing to this release by avoiding to clone the Kademlia peers when yielding the closest nodes!

Changed

  • manager: Downgrade refusing to add address log to debug (#355)
  • Clone only needed KademliaPeers when yielding closest nodes (#326)

Added

  • websocket/stream/tests: Add tests for the stream implementation (#329)

v0.9.1

20 Feb 10:13
v0.9.1
2a49fd0

Choose a tag to compare

[0.9.1] - 2025-01-19

This release enhances compatibility between litep2p and libp2p by using the latest Yamux upstream version. Additionally, it includes various improvements and fixes to boost the stability and performance of the WebSocket stream and the multistream-select protocol.

Changed

  • yamux: Switch to upstream implementation while keeping the controller API (#320)
  • req-resp: Replace SubstreamSet with FuturesStream (#321)
  • cargo: Bring up to date multiple dependencies (#324)
  • build(deps): bump hickory-proto from 0.24.1 to 0.24.3 (#323)
  • build(deps): bump openssl from 0.10.66 to 0.10.70 (#322)

Fixed

  • websocket/stream: Fix unexpected EOF on Poll::Pending state poisoning (#327)
  • websocket/stream: Avoid memory allocations on flushing (#325)
  • multistream-select: Enforce io::error instead of empty protocols (#318)
  • multistream: Do not wait for negotiation in poll_close (#319)

v0.9.0

17 Feb 14:42
v0.9.0
2412f3d

Choose a tag to compare

[0.9.0] - 2025-01-14

This release provides partial results to speed up GetRecord queries in the Kademlia protocol.

Changed

  • kad: Provide partial results to speedup GetRecord queries (#315)

v0.8.4

13 Dec 10:07
v0.8.4
ed801e4

Choose a tag to compare

[0.8.4] - 2024-12-12

This release aims to make the MDNS component more robust by fixing a bug that caused the MDNS service to fail to register opened substreams. Additionally, the release includes several improvements to the identify protocol, replacing FuturesUnordered with FuturesStream for better performance.

Fixed

  • mdns/fix: Failed to register opened substream (#301)

Changed

  • identify: Replace FuturesUnordered with FuturesStream (#302)
  • chore: Update hickory-resolver to version 0.24.2 (#304)
  • ci: Ensure cargo-machete is working with rust version from CI (#303)