mimblewimble/grin

Initial txhashset download (request it from a fast peer)

Open

#3,083 opened on 2019年10月4日

GitHub で見る
 (1 comment) (0 reactions) (0 assignees)Rust (4,876 stars) (991 forks)batch import
enhancementhelp wanted

説明

Related - #3082 (initial header sync)

If we track "fast" peers during the initial header sync it might make sense to use this information when deciding which peer to request the txhashset.zip from.

This zip file includes the full kernel set and the current UTXO set and is approx 425MB currently.

Right now we arbitrarily choose a random peer to download this zip file from and if we get a slow peer then the initial sync is painfully slow. If we uses some better heuristics we would be far more likely to get "lucky" and download it in a reasonable period of time (and reliably).

コントリビューターガイド

技術スタック
rust
領域
backendblockchainperformance
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Familiarity with Grin's peer trackingUnderstanding of initial header sync (issue #3082)Rust programming knowledge
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
45
調査方針
Examine the initial header sync implementation in `src/sync/header sync.rs` and how peers are tracked there. Look at the current peer selection logic for downloading txhashset.zip in `src/sync/body sync.rs`. Consider adding a field to track peer download speed and use that to select the fastest peer for the zip download, similar to how header sync tracks fast peers. Test the heuristic with different network conditions.
Initial txhashset download (request it from a fast peer) · mimblewimble/grin#3083 | Good First Issue