-
Notifications
You must be signed in to change notification settings - Fork 54
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
Fee configuration is not saved #667
Comments
Hey @f321x, thanks for the report. 🙏
Unfortunately, it is not really a bug, but an existing (intentional?) "limitation" of JM. In the meantime, depending on your install method (i.e. the integration you are using - e.g. does not work on systems using the standalone docker image, like Umbrel/Citadel), you can adapt the Only thing we can currently do is to make users aware of the fact.
Also.. thought about adding "Adapt fee settings" as distinct step to the "cheatsheet".. do you think this is a good idea, till the ticket mentioned above is resolved? Do you have another idea, how this can be better communicated? |
Thx for the detailed explanation and quick action. Personally i wouldn't put it in the cheatsheet as it's a more advanced, optional setting and coinjoining works fine with the standard settings (maybe just a bit more expensive). I guess this would bloat the cheatsheet, making it more confusing for new users that need the cheatsheet. |
Expected behavior
Going to settings, setting fee rates for tx and collaborators, doing cj, coming back after a week, doing cj again and it uses the previously configured fees
Actual behavior
Configured fees are reset to their standard values again each time the user tries to do a cj
Steps to reproduce the problem
Specifications
Additional context
Maybe this is intended to not forget about too low tx fees but its somewhat annoying, at least the collaborator fees should be persistent
The text was updated successfully, but these errors were encountered: