-
Notifications
You must be signed in to change notification settings - Fork 57
chore: bump rust-dashcore to the merged sync fixes, minus the sweep-event chain #4459
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
romchornyi
wants to merge
1
commit into
v4.2-dev
Choose a base branch
from
chore/bump-rust-dashcore-sync-fixes
base: v4.2-dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+31
−31
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 Blocking: Historical filter rescan permits peer-driven memory and bandwidth exhaustion
The newly pinned revision includes rust-dashcore commit 2dc97c57 (#866), which was absent from the previous pin. Its
rescan_committed_rangeloads history in 5,000-filter chunks but inserts every match from the wallet birth height throughbatch_start - 1into oneBTreeMap; it does not drain matches until the entire range has been scanned.queue_new_script_matchesthen duplicates that chain-length state into the tracker and aBlocksNeededevent, andBlocksManagerqueues every missing block for download. This is reachable for Platform recovery wallets becausebirth_height_override = Some(0)explicitly enables scans from genesis. The filter-header manager accepts peer-provided CFHeaders, computes their self-consistent chain, and stores it without an independently authenticated checkpoint, while filters are only checked against that same peer-provided chain. An eclipsing compact-filter peer can therefore construct historical filters that avoid the current watch set but match a receive script that a later valid payment causes gap-limit maintenance to derive. At the current multi-million-block chain length, the backward sweep can exhaust mobile memory before emitting its event; if it survives, it schedules millions of full-block reads or downloads. Preserve the historical rescan cursor and process a bounded number of matches per iteration, with an explicit cap or recovery policy for implausibly high match rates, or repin without #866 until that upstream fix is available.source: ['codex']