Concordium / Concordium/concordium-node
Cleanup obsolete code regarding how a node holds its peers
- Dominant language
- Haskell
- Stars
- 108
- Forks
- 24
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 9
Description
**Task description**
Currently the node holds its peers in `Buckets` which is always hardcoded to be of size 1 and there is no way to profit from this type. As a consequence of this, the code is not as straightforward as it could've been, thus it's harder to understand what is going on.
The `Buckets` type should be removed and replaced with a simpler approach focusing on what is required right now, and not at some point in the future.
Contributor guide
Research direction
Search the repository for the `Buckets` type and its usages, then read the node code that stores and accesses peers. Replace the hardcoded single-bucket approach with a simpler representation focused on the current peer requirements, and verify that existing peer-related behavior and tests still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- blockchain, distributed-systems, networking
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100