client/net: Use litep2p as the default network backend #8461

lexnv · 2025-05-07T12:01:03Z

Litep2p Becomes the Default Network Backend

This PR finalizes the litep2p integration and makes it the default network backend for substrate-based chains.

Litep2p Improvements

After the stabilization, a forum post will follow with up to date information and more accurate measurements of the live impact of litep2p.

CPU Usage Reduction

Litep2p consumes roughly 2x less CPU than the libp2p alternative. This frees up resources for other usecases (subsystems) and enables running nodes on more cost-efficient hardware.

This metric has been collected by the networking::libp2p-node metric of a live Kusama validator. This represents the CPU time spent on polling the networking task. Litep2p CPU consumption is on the left, using roughtly 1.3x CPUs, while libp2p on the right uses roughly 2.9-3x CPUs:

This metric has been collected by the NodeExporter of a live Kusama validator. Litep2p CPU consumption is on the left, using roughtly 230 CPU units, while libp2p on the right uses roughly 350 CPU units. This makes litep2p ~1.52 times more effiecient:

DHT Improvements and Authority Discovery

Litep2p is able to discover peers faster via the Kademlia protocol than libp2p. This behavior manifests in faster discovery times for validators. For context, libp2p discovers 1K DHT records (authority records) in approximately 10 minutes, while litep2p discovers them in just 2.5 minutes (for more info see #7077 (comment)).

This will improve issues we've seen with libp2p that causes validators to not receive rewards:

Inconsistent Era Points Due to Networking Issues — Resolved After Bootnode Restart #8548

Stable Sync Peers

Litep2p presents a more stable peer count in comparison with the libp2p backend. This ensures we can sync up faster than libp2p to the tip of the chain. In an older experiment, litep2p syncs to the tip of the chain in 526s, compared to 803s for libp2p. The stability of connections shows improvements for other protocols as well:

The previous image shows on the left the litep2p version and on the right the libp2p version.

Revert Kusama Enablement

This PR reverts #7866. Litep2p is now enabled by default, we don't need to selectively enable it on different chains.

Litep2p 0.9.5

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)

Fix peerset reserve only mode

This has been move in PR: #8650 for ease of reviewing.
The PR rejects non-reserved peers in the reserved-only mode of the litep2p notification peerset.

This reverts commit bcc272a. Signed-off-by: Alexandru Vasile <[email protected]>

Signed-off-by: Alexandru Vasile <[email protected]>

The test is failing too shortly in the overloaded CI. ``` output: 2025-05-16 16:02:40 polkadot-omni-node ... 2025-05-16 16:02:49 [Parachain] 🏆 Imported #3 (0xf558…5881 → 0x3909…8e9c) // final log line ``` It is clear 10 seconds are not enough for this test and will randomly pass if the CI is not overloaded. Signed-off-by: Alexandru Vasile <[email protected]>

Signed-off-by: Alexandru Vasile <[email protected]>

This reverts commit 6310cd5.

paritytech-release-backport-bot · 2025-06-03T11:36:00Z

Created backport PR for stable2409:

[stable2409] Backport #8461 #8729 with remaining conflicts!

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-8461-to-stable2409
git worktree add --checkout .worktree/backport-8461-to-stable2409 backport-8461-to-stable2409
cd .worktree/backport-8461-to-stable2409
git reset --hard HEAD^
git cherry-pick -x f6d18b73c4138cd834c6979be6eed291e63c6f17
git push --force-with-lease

paritytech-release-backport-bot · 2025-06-03T11:36:07Z

Created backport PR for stable2503:

[stable2503] Backport #8461: Use litep2p as the default network backend #8730 with remaining conflicts!

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-8461-to-stable2503
git worktree add --checkout .worktree/backport-8461-to-stable2503 backport-8461-to-stable2503
cd .worktree/backport-8461-to-stable2503
git reset --hard HEAD^
git cherry-pick -x f6d18b73c4138cd834c6979be6eed291e63c6f17
git push --force-with-lease

paritytech-release-backport-bot · 2025-06-03T13:41:47Z

Created backport PR for stable2412:

[stable2412] Backport #8461: Use litep2p as the default network backend #8733 with remaining conflicts!

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-8461-to-stable2412
git worktree add --checkout .worktree/backport-8461-to-stable2412 backport-8461-to-stable2412
cd .worktree/backport-8461-to-stable2412
git reset --hard HEAD^
git cherry-pick -x f6d18b73c4138cd834c6979be6eed291e63c6f17
git push --force-with-lease

paritytech-release-backport-bot · 2025-06-03T13:41:51Z

Git push to origin failed for stable2503 with exitcode 1

…8650) This PR rejects non-reserved peers in the reserved-only mode of the litep2p notification peerset. Previously, litep2p ignored completely the reserved-only state while accepting inbound connections. However, it handled it properly during the slot allocation phase. - the main changes are in the `report_inbound_substream` function, which now propagated a `Rejected` response to litep2p on the reserved-only state - in response, litep2p should never open an inbound substream after receiving the rejected response - the state of peers is not advanced while in `Disconnected` or `Backoff` states - the opening state is moved to `Cancelled` - for consistency purposes (and fuzzing purposes), the `report_substream_opened` is more robustly handling the `Disconnected` state - while at it have replaced a panic with `debug_assert` and an instant reject ## Testing Done - started 2 nodes in Kusama and Polkadot with litep2p - added the `reserved_only_rejects_non_reserved_peers` test to ensure litep2p handles peers properly from different states This PR has been extracted from #8461 to ease the review process cc @paritytech/networking --------- Signed-off-by: Alexandru Vasile <[email protected]> Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Dmitry Markin <[email protected]> (cherry picked from commit e82b4db)

* master: omni-node: fix `benchmark pallet` to work with `--runtime` (#8594) Handle and suppress "New unknown `FromSwarm` libp2p event" warning (#8731) Implement detailed logging for XCM failures (#8724) [pallet-revive] contract's nonce starts at 1 (#8734) sync/fix: Clear gap sync on known imported blocks (#8445) [PoP] Add personhood tracking pallets (#8164) client/net: Use litep2p as the default network backend (#8461) Unflake `returns_status_for_pruned_blocks` (#8709) [AHM] Report the weights of epmb pallet to expose kusama and polkadot weights (#8704) Remove all XCM dependencies from `pallet-revive` (#8584) Docker master image tag fix (#8711) Record ed as part of the storage deposit (#8718) [pallet-revive] update dry-run logic (#8662) feat: add collator peer ID to ParachainInherentData (#8708) Nest errors in pallet-xcm (#7730) pallet-assets ERC20 precompile (#8554) Broker: Introduce min price + adjust renewals to lower market. (#8630) [AHM] Staking async fixes for XCM and election planning (#8422) Staking (EPMB): Add defensive error handling to voter snapshot creation and solution verification (#8687)

…nd (#8730) Backport #8461 into `stable2503` from lexnv. See the [documentation](https://github.com/paritytech/polkadot-sdk/blob/master/docs/BACKPORT.md) on how to use this bot.  --------- Signed-off-by: Alexandru Vasile <[email protected]> Co-authored-by: Alexandru Vasile <[email protected]> Co-authored-by: Alexandru Vasile <[email protected]> Co-authored-by: Egor_P <[email protected]>

…nd (#8733) Backport #8461 into `stable2412` from lexnv. See the [documentation](https://github.com/paritytech/polkadot-sdk/blob/master/docs/BACKPORT.md) on how to use this bot.  --------- Signed-off-by: Alexandru Vasile <[email protected]> Co-authored-by: Alexandru Vasile <[email protected]> Co-authored-by: Alexandru Vasile <[email protected]>

…8650) This PR rejects non-reserved peers in the reserved-only mode of the litep2p notification peerset. Previously, litep2p ignored completely the reserved-only state while accepting inbound connections. However, it handled it properly during the slot allocation phase. - the main changes are in the `report_inbound_substream` function, which now propagated a `Rejected` response to litep2p on the reserved-only state - in response, litep2p should never open an inbound substream after receiving the rejected response - the state of peers is not advanced while in `Disconnected` or `Backoff` states - the opening state is moved to `Cancelled` - for consistency purposes (and fuzzing purposes), the `report_substream_opened` is more robustly handling the `Disconnected` state - while at it have replaced a panic with `debug_assert` and an instant reject ## Testing Done - started 2 nodes in Kusama and Polkadot with litep2p - added the `reserved_only_rejects_non_reserved_peers` test to ensure litep2p handles peers properly from different states This PR has been extracted from #8461 to ease the review process cc @paritytech/networking --------- Signed-off-by: Alexandru Vasile <[email protected]> Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Dmitry Markin <[email protected]>

# Litep2p Becomes the Default Network Backend This PR finalizes the [litep2p](https://github.com/paritytech/litep2p) integration and makes it the default network backend for substrate-based chains. ## Litep2p Improvements After the stabilization, a forum post will follow with up to date information and more accurate measurements of the live impact of litep2p. ### CPU Usage Reduction **Litep2p consumes roughly 2x less CPU than the libp2p alternative**. This frees up resources for other usecases (subsystems) and enables running nodes on more cost-efficient hardware. This metric has been collected by the `networking::libp2p-node` metric of a live Kusama validator. This represents the CPU time spent on polling the networking task. Litep2p CPU consumption is on the left, using roughtly 1.3x CPUs, while libp2p on the right uses roughly 2.9-3x CPUs: ![Screenshot 2025-05-26 at 15 23 22](https://github.com/user-attachments/assets/17bf1ed8-b887-423e-b131-f0bbf146919e) This metric has been collected by the NodeExporter of a live Kusama validator. Litep2p CPU consumption is on the left, using roughtly 230 CPU units, while libp2p on the right uses roughly 350 CPU units. This makes litep2p ~1.52 times more effiecient: ![Screenshot 2025-05-26 at 15 24 33](https://github.com/user-attachments/assets/8923cb56-241d-4e1d-9593-33c5def2ff4d) ### DHT Improvements and Authority Discovery Litep2p is able to discover peers faster via the Kademlia protocol than libp2p. This behavior manifests in faster discovery times for validators. For context, libp2p discovers 1K DHT records (authority records) in approximately 10 minutes, while litep2p discovers them in just 2.5 minutes (for more info see #7077 (comment)). This will improve issues we've seen with libp2p that causes validators to not receive rewards: - #8548 ### Stable Sync Peers Litep2p presents a more stable peer count in comparison with the libp2p backend. This ensures we can sync up faster than libp2p to the tip of the chain. In an older experiment, litep2p syncs to the tip of the chain in 526s, compared to 803s for libp2p. The stability of connections shows improvements for other protocols as well: ![Screenshot 2025-05-26 at 15 01 59](https://github.com/user-attachments/assets/ac3607ba-a551-49e5-9a50-f5150a6b619f) The previous image shows on the left the litep2p version and on the right the libp2p version. ### Revert Kusama Enablement This PR reverts #7866. Litep2p is now enabled by default, we don't need to selectively enable it on different chains. ### Litep2p 0.9.5 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](paritytech/litep2p#395)) - websocket: Fix connection stability on decrypt messages ([#393](paritytech/litep2p#393)) Changed: - crypto/noise: Show peerIDs that fail to decode ([#392](paritytech/litep2p#392)) - cargo: Bump yamux to 0.13.5 and tokio to 1.45.0 ([#396](paritytech/litep2p#396)) - ci: Enforce and apply clippy rules ([#388](paritytech/litep2p#388)) - build(deps): bump ring from 0.16.20 to 0.17.14 ([#389](paritytech/litep2p#389)) - Update hickory-resolver 0.24.2 -> 0.25.2 ([#386](paritytech/litep2p#386)) ### Fix peerset reserve only mode This has been move in PR: #8650 for ease of reviewing. The PR rejects non-reserved peers in the reserved-only mode of the litep2p notification peerset. --------- Signed-off-by: Alexandru Vasile <[email protected]>

Polkadot-Forum · 2025-07-11T13:28:12Z

This pull request has been mentioned on Polkadot Forum. There might be relevant details there:

https://forum.polkadot.network/t/announcing-the-stabilization-of-the-litep2p-network-backend/13712/1

…e2412-6` instead of volatile branch to track `polkadot-sdk`) The latest release tag for `stable2412` is `polkadot-stable2412-7`. Testing has shown that updating to this version causes frequent errors in RPC calls from light clients (`smoldot`) and existing client SDK code. This may be because this version uses `litep2p` as the default library for `substrate`. watch this: paritytech/polkadot-sdk#8461

…work backend (paritytech#8730) Backport paritytech#8461 into `stable2503` from lexnv. See the [documentation](https://github.com/paritytech/polkadot-sdk/blob/master/docs/BACKPORT.md) on how to use this bot.  --------- Signed-off-by: Alexandru Vasile <[email protected]> Co-authored-by: Alexandru Vasile <[email protected]> Co-authored-by: Alexandru Vasile <[email protected]> Co-authored-by: Egor_P <[email protected]>

…e2412-6` instead of volatile branch to track `polkadot-sdk`) The latest release tag for `stable2412` is `polkadot-stable2412-7`. Testing has shown that updating to this version causes frequent errors in RPC calls from light clients (`smoldot`) and existing client SDK code. This may be because this version uses `litep2p` as the default library for `substrate`. watch this: paritytech/polkadot-sdk#8461

…8650) This PR rejects non-reserved peers in the reserved-only mode of the litep2p notification peerset. Previously, litep2p ignored completely the reserved-only state while accepting inbound connections. However, it handled it properly during the slot allocation phase. - the main changes are in the `report_inbound_substream` function, which now propagated a `Rejected` response to litep2p on the reserved-only state - in response, litep2p should never open an inbound substream after receiving the rejected response - the state of peers is not advanced while in `Disconnected` or `Backoff` states - the opening state is moved to `Cancelled` - for consistency purposes (and fuzzing purposes), the `report_substream_opened` is more robustly handling the `Disconnected` state - while at it have replaced a panic with `debug_assert` and an instant reject ## Testing Done - started 2 nodes in Kusama and Polkadot with litep2p - added the `reserved_only_rejects_non_reserved_peers` test to ensure litep2p handles peers properly from different states This PR has been extracted from #8461 to ease the review process cc @paritytech/networking --------- Signed-off-by: Alexandru Vasile <[email protected]> Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Dmitry Markin <[email protected]>

# Litep2p Becomes the Default Network Backend This PR finalizes the [litep2p](https://github.com/paritytech/litep2p) integration and makes it the default network backend for substrate-based chains. ## Litep2p Improvements After the stabilization, a forum post will follow with up to date information and more accurate measurements of the live impact of litep2p. ### CPU Usage Reduction **Litep2p consumes roughly 2x less CPU than the libp2p alternative**. This frees up resources for other usecases (subsystems) and enables running nodes on more cost-efficient hardware. This metric has been collected by the `networking::libp2p-node` metric of a live Kusama validator. This represents the CPU time spent on polling the networking task. Litep2p CPU consumption is on the left, using roughtly 1.3x CPUs, while libp2p on the right uses roughly 2.9-3x CPUs: ![Screenshot 2025-05-26 at 15 23 22](https://github.com/user-attachments/assets/17bf1ed8-b887-423e-b131-f0bbf146919e) This metric has been collected by the NodeExporter of a live Kusama validator. Litep2p CPU consumption is on the left, using roughtly 230 CPU units, while libp2p on the right uses roughly 350 CPU units. This makes litep2p ~1.52 times more effiecient: ![Screenshot 2025-05-26 at 15 24 33](https://github.com/user-attachments/assets/8923cb56-241d-4e1d-9593-33c5def2ff4d) ### DHT Improvements and Authority Discovery Litep2p is able to discover peers faster via the Kademlia protocol than libp2p. This behavior manifests in faster discovery times for validators. For context, libp2p discovers 1K DHT records (authority records) in approximately 10 minutes, while litep2p discovers them in just 2.5 minutes (for more info see #7077 (comment)). This will improve issues we've seen with libp2p that causes validators to not receive rewards: - #8548 ### Stable Sync Peers Litep2p presents a more stable peer count in comparison with the libp2p backend. This ensures we can sync up faster than libp2p to the tip of the chain. In an older experiment, litep2p syncs to the tip of the chain in 526s, compared to 803s for libp2p. The stability of connections shows improvements for other protocols as well: ![Screenshot 2025-05-26 at 15 01 59](https://github.com/user-attachments/assets/ac3607ba-a551-49e5-9a50-f5150a6b619f) The previous image shows on the left the litep2p version and on the right the libp2p version. ### Revert Kusama Enablement This PR reverts #7866. Litep2p is now enabled by default, we don't need to selectively enable it on different chains. ### Litep2p 0.9.5 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](paritytech/litep2p#395)) - websocket: Fix connection stability on decrypt messages ([#393](paritytech/litep2p#393)) Changed: - crypto/noise: Show peerIDs that fail to decode ([#392](paritytech/litep2p#392)) - cargo: Bump yamux to 0.13.5 and tokio to 1.45.0 ([#396](paritytech/litep2p#396)) - ci: Enforce and apply clippy rules ([#388](paritytech/litep2p#388)) - build(deps): bump ring from 0.16.20 to 0.17.14 ([#389](paritytech/litep2p#389)) - Update hickory-resolver 0.24.2 -> 0.25.2 ([#386](paritytech/litep2p#386)) ### Fix peerset reserve only mode This has been move in PR: #8650 for ease of reviewing. The PR rejects non-reserved peers in the reserved-only mode of the litep2p notification peerset. --------- Signed-off-by: Alexandru Vasile <[email protected]>

…e2412-6` instead of volatile branch to track `polkadot-sdk`) The latest release tag for `stable2412` is `polkadot-stable2412-7`. Testing has shown that updating to this version causes frequent errors in RPC calls from light clients (`smoldot`) and existing client SDK code. This may be because this version uses `litep2p` as the default library for `substrate`. watch this: paritytech/polkadot-sdk#8461

lexnv added 3 commits May 7, 2025 14:52

Revert "network: Make litep2p the default backend in Kusama (#7866)"

4154014

This reverts commit bcc272a. Signed-off-by: Alexandru Vasile <[email protected]>

client/net: Use litep2p as the default network backend

414c539

Signed-off-by: Alexandru Vasile <[email protected]>

client/net: Add extra comments for the libp2p components

76b0d03

Signed-off-by: Alexandru Vasile <[email protected]>

lexnv self-assigned this May 7, 2025

lexnv and others added 5 commits May 7, 2025 15:15

cumulus: Fix build for unwrap of net backend

1bfef62

Signed-off-by: Alexandru Vasile <[email protected]>

tests: Repalce in memory transports with TCP for litep2p

b915b35

Signed-off-by: Alexandru Vasile <[email protected]>

cumulus/tests: Listen on 127.0.0.1

e1e5edc

Signed-off-by: Alexandru Vasile <[email protected]>

Merge branch 'master' into lexnv/litep2p-default

fab613f

Merge branch 'master' into lexnv/litep2p-default

521330d

lexnv mentioned this pull request May 16, 2025

websocket: Fix connection stability on decrypt messages paritytech/litep2p#393

Merged

lexnv added 4 commits May 16, 2025 15:08

cargo: Use litep2p from gitbranch to include ws stability fix

18fa8eb

Signed-off-by: Alexandru Vasile <[email protected]>

Merge remote-tracking branch 'origin/master' into lexnv/litep2p-default

b9e1753

Add prdoc

45621d7

Signed-off-by: Alexandru Vasile <[email protected]>

cargo: Update once-cell to 1.21.3

5b20453

Signed-off-by: Alexandru Vasile <[email protected]>

lexnv added T0-node This PR/Issue is related to the topic “node”. A4-backport-stable2409 A4-backport-stable2503 Pull request must be backported to the stable2503 release branch labels May 16, 2025

lexnv added 13 commits May 16, 2025 20:08

prdoc: Remove tabs and use spaces

0af8bf5

Signed-off-by: Alexandru Vasile <[email protected]>

zombinet/polkadot/0014: Align log lines between backends to fix test

85396af

Signed-off-by: Alexandru Vasile <[email protected]>

litep2p/discovery: Enable random walks only on network configs

6310cd5

Signed-off-by: Alexandru Vasile <[email protected]>

net/config: Reimplement default on NetworkBackendType

12ebb14

Signed-off-by: Alexandru Vasile <[email protected]>

Merge remote-tracking branch 'origin/master' into lexnv/litep2p-default

734db07

litep2p/peerset: Reject substreams on reserved-only states

f19326c

Signed-off-by: Alexandru Vasile <[email protected]>

litep2p/peerset: Handle disconnected states properly

410946f

Signed-off-by: Alexandru Vasile <[email protected]>

litep2p/peerset: Ensure transitions keep previous slot allocations

956d5e9

Signed-off-by: Alexandru Vasile <[email protected]>

litep2p/peerset: Derive debug and add extra trace logs

97e57c6

Signed-off-by: Alexandru Vasile <[email protected]>

peerset/tests: Ensure reserved-only mode functions properly

0c6ced0

Signed-off-by: Alexandru Vasile <[email protected]>

litep2p/peerset: Simplify canceled state

289bdab

Signed-off-by: Alexandru Vasile <[email protected]>

Revert "litep2p/discovery: Enable random walks only on network configs"

47f3dbd

This reverts commit 6310cd5.

paritytech-release-backport-bot bot mentioned this pull request Jun 3, 2025

[stable2503] Backport #8461: Use litep2p as the default network backend #8730

Merged

lexnv added A4-backport-stable2412 and removed A4-backport-stable2409 labels Jun 3, 2025

paritytech-release-backport-bot bot mentioned this pull request Jun 3, 2025

[stable2412] Backport #8461: Use litep2p as the default network backend #8733

Merged

lexnv mentioned this pull request Jun 20, 2025

polkadot: average finality increased from 4 to about 8 blocks. #8915

Closed

0xbillw mentioned this pull request Jul 17, 2025

Polkadot-sdk LTS stable2412 update polkadot-evm/frontier#1714

Merged

lexnv mentioned this pull request Jul 31, 2025

lexnv/evidence: Retain at rank I polkadot-fellows/Evaluations#186

Merged

3 tasks

github-actions bot mentioned this pull request Oct 24, 2025

Update polkadot-sdk from stable2503 to stable2506 moondance-labs/tanssi#1340

Closed

ipapandinas mentioned this pull request Dec 12, 2025

chore: Update to PolkadotSDK release stable2503 AstarNetwork/Astar#1571

Draft

2 tasks

RomarQ mentioned this pull request Dec 17, 2025

Use the selected backend worker (Libp2p vs Litep2p) moonbeam-foundation/moonbeam#3595

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

client/net: Use litep2p as the default network backend #8461

client/net: Use litep2p as the default network backend #8461

Uh oh!

lexnv commented May 7, 2025 •

edited

Loading

Uh oh!

paritytech-release-backport-bot bot commented Jun 3, 2025

Uh oh!

paritytech-release-backport-bot bot commented Jun 3, 2025

Uh oh!

paritytech-release-backport-bot bot commented Jun 3, 2025

Uh oh!

paritytech-release-backport-bot bot commented Jun 3, 2025

Uh oh!

Polkadot-Forum commented Jul 11, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

client/net: Use litep2p as the default network backend #8461

client/net: Use litep2p as the default network backend #8461

Uh oh!

Conversation

lexnv commented May 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Litep2p Becomes the Default Network Backend

Litep2p Improvements

CPU Usage Reduction

DHT Improvements and Authority Discovery

Stable Sync Peers

Revert Kusama Enablement

Litep2p 0.9.5

Fix peerset reserve only mode

Uh oh!

paritytech-release-backport-bot bot commented Jun 3, 2025

Uh oh!

paritytech-release-backport-bot bot commented Jun 3, 2025

Uh oh!

paritytech-release-backport-bot bot commented Jun 3, 2025

Uh oh!

paritytech-release-backport-bot bot commented Jun 3, 2025

Uh oh!

Polkadot-Forum commented Jul 11, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

lexnv commented May 7, 2025 •

edited

Loading