Gossip Message for indirect peers
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 366
- Forks
- 85
- Avg merge
- 2d 39m
- Merged PRs (30d)
- 6
Description
Hello,
Interested in libp2p projects, i was experimenting the gossipsub.. When host is directly connected to the other host then only i am able to receive the message from the peer.
If connection as follows
A -> B and B->C
and A and C are subscribed to a topic.
A sends a message to the topic, not receiving at C, until unless B also subscribes to the same topic.
condion is floodPublish false and gossipPeerScoreParam isDirect= false
Tried with floodPublish= true and is_direct = true also.
But result is the same.
Is there something i am missing?
Any leads will be highly appreciated.
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 reproducing the A–B–C topology with gossipsub, checking subscriptions and the floodPublish, gossipPeerScoreParam, and isDirect settings described in the report. Trace message propagation between indirect peers and compare it with the direct-peer case. Done means identifying why C does not receive A's message and documenting or fixing the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100