You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: This feature must be hidden behind a version flag as it will only be available with backend version >= 0.9.11.
As a user, I want to specify a custom tx fee when creating a single transaction, so I not have to edit the config values on a per transaction basis. This can be done by adding a custom tx input field, prefilled with the config value, to the send options on non-collaborative sends.
Later, this functionality can be used when creating/unlocking/renewing fidelity bonds (#678).
The text was updated successfully, but these errors were encountered:
From Jam UX perspective, if custom fee can be specified for direct-send, wouldn't you like to have it also for /wallet/{walletname}/taker/coinjoin? Implementation should not be hard, scripts/sendpayment.py already support it for both coinjoin and non-coinjoin sends.
From Jam UX perspective, if custom fee can be specified for direct-send, wouldn't you like to have it also for /wallet/{walletname}/taker/coinjoin? Implementation should not be hard, scripts/sendpayment.py already support it for both coinjoin and non-coinjoin sends.
Since JoinMarket-Org/joinmarket-clientserver#1597 it is possible to specify the txfee directly on direct-send operations.
Note: This feature must be hidden behind a version flag as it will only be available with backend version >= 0.9.11.
As a user, I want to specify a custom tx fee when creating a single transaction, so I not have to edit the config values on a per transaction basis. This can be done by adding a custom tx input field, prefilled with the config value, to the send options on non-collaborative sends.
Later, this functionality can be used when creating/unlocking/renewing fidelity bonds (#678).
The text was updated successfully, but these errors were encountered: