-
Notifications
You must be signed in to change notification settings - Fork 159
Derive shutdown scripts without blocking on wallet persistence #1011
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
jkczyz
wants to merge
9
commits into
lightningdevkit:main
Choose a base branch
from
jkczyz:2026-07-signer-blockon-deadlock
base: main
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.
Open
Changes from 2 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
273e4d0
Derive shutdown scripts without blocking on wallet persistence
jkczyz 1b27621
f - Pool pre-persisted addresses instead of deferring the reveal's pe…
jkczyz 338dc8f
f - Serve user-facing address requests from the address pool
jkczyz 6ed64e8
f - Abort in-flight address pool refills at shutdown
jkczyz 075a40c
f - Account for the address pool in full-scan stop gaps
jkczyz 97df7cf
f - Keep failed refills from durably revealing unrecorded indices
jkczyz 77164dc
f - Drop the address pool full-scan stop-gap extension
jkczyz 5fd08ef
f - Read the address pool record alongside the other startup reads
jkczyz a7c52af
f - Reinsert failed handouts into the address pool by index
jkczyz 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
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
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.
We need to parallelize the reads on startup.
IMO it would also preferable to keep up the pre-existing patterns of doing the
read_methods here in parallel, and then hand that in to initialize via anAddressPool::newor so rather than doing all/obfuscating in aninitialize_method.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.
🤖 Done. The record read now runs in the
tokio::join!with the other startup reads, its result is handed toWallet::new, which validates it inAddressPool::new, and the builder only blocks on the initial pool top-up. One side effect: a failed read now fails the build withReadFailedrather thanWalletSetupFailed.