Cannot sync chain behind NAT
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
Currently, if I'm behind a NAT, I cannot sync the chain. Two proposed solutions (ideally both):
1. Add UPnP support to open port 9999. I understand this adds code, what's the shortest possible implementation? I didn't find good Python libraries.
2. Refactor connections with peers to remain open. Haven't looked too much into this.
I think with a little TLC, TINY can be a top 10 coin on https://coinmarketcap.com/
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the peer connection and chain synchronization paths to understand why syncing fails behind NAT. Evaluate the two proposals in the issue—UPnP port 9999 support and keeping peer connections open; done means a node behind NAT can sync the chain reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100