py-libp2p lacks resource management and is vulnerable to resource exhaustion attacks

Summary

Unlike go-libp2p v0.18.0+, py-libp2p does not implement a resource manager (rcmgr). This leaves it vulnerable to targeted resource exhaustion, such as:

1. Unlimited stream creation (e.g. via multistream-select)

2. Excessive memory use through malformed payloads

3. Sybil-based connection flooding

Expected behavior

Expected Behavior
1.Enforced limits on streams, connections, memory, and peers

2. Configurable (and optionally autoscaling) resource limits

3. Optional integration with metrics and peer blocking

Actual behavior

Actual Behavior
No resource manager in place

No limits or backpressure on connections/streams

No way to detect or block abusive peers

High DoS risk in adversarial environments

Relevant log output

Possible Solution

Enforced limits on streams, connections, memory, and peers
There is the similar problem
There is the similart fix logic

Environment

Would you like to work on fixing this bug ?

Maybe

Start by comparing py-libp2p's current connection and stream handling with the go-libp2p v0.18.0+ resource manager, the linked security advisory, and the referenced fix commit. Done means resource limits and backpressure cover streams, connections, memory, and peers, with the requested configurability and optional metrics or peer-blocking integration addressed.