Set a maximum address record size of 4KiB in 5h3 peerstore (generate/consume)
Open
Nobody has claimed this yet.
kind/enhancement
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
Both in records we produce and records we consume. This will allow over 100 addresses + signatures etc, which is already overkill. We should consider reducing this to 1KiB in the future.
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 locating the 5h3 peerstore code that generates and consumes address records, then inspect how record sizes are currently handled. The change is complete when both produced and consumed records enforce a maximum size of 4KiB, with tests covering the limit.
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