Add recommended feerate flow in peer manager#745
Merged
Conversation
This recommended feerate relies on mempool.space estimation for an half-hour target, but falls back to the peer funding feerate if mempool.space is unavailable.
Member
Author
|
@robbiehanson Context is #743, which was an Android issue but may affect iOS as well, it's worth looking into. |
robbiehanson
approved these changes
Sep 18, 2025
Contributor
|
iOS uses it's own custom MempoolMonitor. But I should copy what you did with the fallback values. |
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
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.
This recommended feerate relies on mempool.space estimation for the half-hour target, with a fallback to the peer funding feerate if mempool.space is unavailable. This is more robust than just relying on mempool.space, and the peer funding feerate is much more pertinent than a static hard-coded fallback.