Assess the impact of the client Kubo node acting as a peer
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 10/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- blockchain, rust
- Domain
- blockchain, networking
Research direction
This is an investigation with no code location named in the payload. Start by reading the Kubo documentation on the settings that control whether a node announces and serves downloaded blocks, then model download time under low-bandwidth, high-latency, short-lived clients. Done means a recommended default and a documented go or no-go decision on native client seeding, which a maintainer must make.
Written by the indexing model from the issue text.
Description
Why
A Kubo node used by a client announces and serves the blocks it has downloaded. Client machines have varying connectivity and short lifetimes, which adds uncertainty to the downloads of the other peers.
What
Assess the impact of client nodes acting as peers on the expected download time, recommend a default behavior, and decide whether the native seeding by the client is implemented.
How
- Evaluate the Kubo settings that control whether a node announces and serves the downloaded blocks
- Model the impact of a low bandwidth/high latency/short lived clients in the network on the global download time of the client
- Decide whether the native seeding by the client is implemented (go or no-go) (also consider impact of Leios)
- Dominant language
- Rust
- Stars
- 155
- Forks
- 52
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 37
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from IntersectMBO/mithril
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
IntersectMBO/mithril#1605 · 2 comments ·
Maintainers usually reply within 2 days
-
Publish a DNSLink record of the immutable archives IPNS name in the Mithril networks DNS zonesPossibly taken @jpraynaud claimed this 2 days ago. Openfeature :rocket:
IntersectMBO/mithril#3700 · 1 assignee ·
Maintainers usually reply within 2 days
-
feature :rocket:
Difficulty 4/5 3-5 days Newbie friendliness 25/100
IntersectMBO/mithril#3699 ·
Maintainers usually reply within 2 days
-
feature :rocket:
Difficulty 4/5 3-5 days Newbie friendliness 35/100
IntersectMBO/mithril#3698 ·
Maintainers usually reply within 2 days
-
Prototype the Cardano database snapshot and restoration with the Leios databasePossibly taken @jpraynaud claimed this 5 days ago. Openprototype :hammer_and_wrench:
IntersectMBO/mithril#3691 · 1 assignee ·
Maintainers usually reply within 2 days
All issues in IntersectMBO/mithril
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
storytold/photocraft#14822 ·
Maintainers usually reply within 1 day
-
bug css
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
dginev/latexml-oxide#853 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 2 days
-
[Bug] export_build_environment admits its output directory only after the export ran in the build computerPossibly taken @viniciusdsandrade claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day