Add queuing to Gossipsub
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 624
- Forks
- 256
- Avg merge
- 1d 34m
- Merged PRs (30d)
- 47
Description
Description
As discussed in https://github.com/libp2p/py-libp2p/discussions/719 Issue:1, we need to have Urgent, queuing, message splitting and a function equivalent to sendRPC of go-libp2p in py-libp2p's gossipsub.
Motivation
It will stabilize current gossipsub implementation by message splitting and queuing for retries and other important fallback on message failure.
Current Implementation
Currently, control messages are piggybacked and send to peers but queuing and message splitting is not present
Are you planning to do it yourself in a pull request ?
Yes
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 discussion 719 and tracing the current py-libp2p Gossipsub implementation where control messages are piggybacked. Compare the requested behavior with go-libp2p's sendRPC equivalent and define how queuing, message splitting, Urgent handling, and retry fallback should work. Done means these behaviors are implemented and validated for failed-message and control-message cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100