-
Notifications
You must be signed in to change notification settings - Fork 179
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
Feature request: provide tx fee in direct-send
api request
#1360
Comments
This sounds good idea, should not be hard, |
Good to know. Thanks for the heads-up. Pardon the question, how would one actually send a transaction with 1sats/vbyte? Setting the block target to a high value such as Edit: Okay, looking at the docs, it's sats/kilo-vbyte - now I understand. Thank you! |
Ah, yes, not sat/vB. |
Just a side note: we have a comment in the config about this, but don't set txfee to less than 1200 sats/kvb, because we randomize it 20% (and that is hardcoded currently, we don't let users change it). I'd keep a safety buffer a bit higher than that if it was me, I'm never comfortable being too close to the limit (but ymmv there!). |
Actually we do, for almost a year, since #1033 (v0.9.3). joinmarket-clientserver/jmclient/jmclient/configure.py Lines 282 to 286 in 044bef6
|
I know what you mean. Currently implementing adapting fee related configs in Jam and actively preventing setting it lower than 1000 sats/kilo-vbyte minus the lower max. randomization factor. |
Yes, even 0 sat fee transactions are valid, but with default settings Bitcoin Core will not relay anything below 1 sat/vB (1000 sat/kvB). |
Wouldn't it still be okay to set it to 1001 sats/kvb given that the value cannot go below |
Hmm.. just got this after a "direct-send" (4 inputs [one of them an expired fb], 1 output) with
But shortly afterwards - without changing anything:
First transaction (failed) is 646 bytes. 🤔
|
Ahh, yes, there are multiple situations where JM sometimes incorrectly calculates tx vsize. |
Any updates/estimates on this @kristapsk? Would greatly enhance the UX in Jam. Also nice to have for joinmarket-webui/jam#678 since no change output is created and it cannot be CPFPd. |
Would it be possible to provide the tx fee in sats/vbyte to the
SendDirectRequest
? Is this rather difficult to implement? I guess it can be done in a backward compatible way: Iftx_fee
prevent, use this a the miner fee, if notx_fee
is given is given, keep the current behaviour.What do you think? Is this a feature worth implementing?
The text was updated successfully, but these errors were encountered: