feat: rate limit inbound streams per protocol per connection
Open
Nobody has claimed this yet.
need/triage
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 546
- Avg merge
- 8h 18m
- Merged PRs (30d)
- 16
Description
As discussed in https://github.com/libp2p/js-libp2p/issues/1469 we would like to allow consumers to to rate limit the inbound streams to prevent other malicious nodes from spamming it with identify/push for example.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the discussion in issue #1469 and tracing the inbound stream handling entry point in js-libp2p. Determine how consumers should configure limits per protocol and connection, and how repeated identify/push streams should be rejected or throttled. Done means the requested per-protocol, per-connection inbound rate limit is available to consumers and its behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100