Repository navigation
Save max fee rate in receiver session context - #1033
Merged
arminsabouri merged 1 commit intoSep 3, 2025
Merged
Conversation
Collaborator
Pull Request Test Coverage Report for Build 17436370745Details
💛 - Coveralls |
Contributor
|
Thanks @arminsabouri |
Member
|
"Co-authored-by" is the syntax you want in a commit message |
arminsabouri
force-pushed
the
max-fee-rate-in-session-context
branch
from
September 2, 2025 19:11
4b468f8 to
c1c79df
Compare
Contributor
Author
|
Dart tests are problematic |
spacebear21
approved these changes
Sep 2, 2025
spacebear21
left a comment
Collaborator
There was a problem hiding this comment.
ACK c1c79df.
I think the spooky uniffi-dart error in CI is due to the return type in with_max_fee_rate containing bitcoin_ffi::error::FeeRateError.
arminsabouri
force-pushed
the
max-fee-rate-in-session-context
branch
from
September 3, 2025 14:11
c1c79df to
3f0c442
Compare
The reference implementation currently overrides the original max fee rate preference when resuming a session. This commit pins the max fee rate preference to the session by persisting it in the session context. When applying fees, if the applications’s fee rate preference has changed, the updated preference takes precedence. Co-authored-by: Johnosezele <johnosezele@gmail.com>
arminsabouri
force-pushed
the
max-fee-rate-in-session-context
branch
from
September 3, 2025 14:16
3f0c442 to
e53b00b
Compare
Contributor
Author
Ended up wrapping |
spacebear21
approved these changes
Sep 3, 2025
spacebear21
left a comment
Collaborator
There was a problem hiding this comment.
ACK, opened an issue here to track the underlying uniffi-dart issue.
This was referenced Sep 3, 2025
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.
The reference implementation currently overrides the original max fee rate preference when resuming a session. This commit pins the max fee rate preference to the session by persisting it in the session context. When applying fees, if the applications’s fee rate preference has changed, the updated preference takes precedence.
Pull Request Checklist
Please confirm the following before requesting review:
AI
in the body of this PR.
--
Closes http://github.com/payjoin/rust-payjoin/issues/897
Changes were picked off #934
cc @Johnosezele