Update fee rate cache on startup and make sync interval configurable #102
Conversation
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
tnull
force-pushed
the
2023-05-fee-fix
branch
4 times, most recently
from
65bb071 to
af9028c
Compare
|
Rebased on #108. |
tnull
force-pushed
the
2023-05-fee-fix
branch
11 times, most recently
from
984d936 to
6b1f2ff
Compare
tnull
force-pushed
the
2023-05-fee-fix
branch
2 times, most recently
from
db655e8 to
5053096
Compare
tnull
force-pushed
the
2023-05-fee-fix
branch
5 times, most recently
from
c4f3fe4 to
575c9f7
Compare
tnull
changed the title
tnull
changed the title
tnull
force-pushed
the
2023-05-fee-fix
branch
2 times, most recently
from
0393a8f to
d218da2
Compare
|
Rebased on main. |
jkczyz
reviewed
Jun 1, 2023
We improve the docs, in particular mentioning now that users should always prefer background syncing over blocking sync if possible. Moreover, as we already have a current thread runtime setup for the BDK wallet, we now also use it to sync the LDK wallet. This is a good idea as we want to avoid calling `block_on` on our main runtime where possible, which is always in danger of (temporarily or permanently) blocking the world if something goes wrong.
So far we'd immediately start background syncing wallets and the fee cache upon `start()` which would work fine, except when these initial syncs failed, in which case we'd use our fallback fee. This might lead to being disconnected from peers as our fallback values are likely out of current fee ranges. To mitigate this we here simply enforce that an initial fee rate update in `start()` is successful. Additionally, we make the fee rate cache update interval configurable.
Squashed without further changes. |
jkczyz
approved these changes
Jun 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Based on #93.Based on #108.So far we'd immediately start background syncing upon
start()which would work fine, except when these initial syncs failed, in which case we'd use our fallback fee. This might lead to being disconnected from peers as our fallback values are likely out of current fee ranges.To mitigate this we here simply enforce that an initial update of our fee rate cache in
start()is successful and hence we'd at least once got a recent fee estimation update.Moreover, we make the background syncing intervals configurable, however enforcing a floor of 10 seconds.