Question: Routing enabled based on protocol?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
For my application I currently disabled routing. From vaguely following development of libp2p I see that routing will be enabled by default in the future, and that important things like udp Nat hole-punching will use routing. So it is best to enabled routing. However, my apllication sends huge amount of data between peers, which my bootstrap server nodes should not handle. So the question is: Can we disable routing for certain protocols? E.g. all data heavy protocols work only with direct p2p connections?
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 reviewing how routing, protocol handling, UDP NAT hole-punching, bootstrap server nodes, and direct peer-to-peer connections relate in this Go libp2p repository. The issue names no files, tests, or entry points, so the required design and completion criteria need clarification before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100