celestiaorg / celestiaorg/go-header
p2p: Parametrize topic ID
Open
kind:feat
p2p
- Dominant language
- Go
- Stars
- 21
- Forks
- 33
- Avg merge
- 5d 20h
- Merged PRs (30d)
- 7
Description
Currently, in the p2p layer, the topic ID is hardcoded as `header-sub`. We should make this configurable to accommodate use cases like https://github.com/rollkit/rollkit/issues/1020
Contributor guide
Research direction
Start by locating the p2p code where the topic ID `header-sub` is hardcoded and trace how that topic is used for header requests or synchronization. The work is done when callers can configure the topic ID, the existing default behavior remains available, and the relevant p2p tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100