libp2p / libp2p/go-libp2p-pubsub
Fix gossipsub subscription filter bug
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 364
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
As discussed [here](https://discuss.libp2p.io/t/filtering-nodes-that-we-gossip-to/1012/21), there is a bug in the gossipsub implementation that causes messages to be sent in certain cases to peers even if those peers should be blocked by subscription filters.
Contributor guide
No contributing guide indexed for this repository
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 linked discussion and tracing the gossipsub subscription-filtering path in the repository. Reproduce the cases where messages reach peers that should be blocked, then verify that filtered peers no longer receive those messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100