Author

Topic: What is happening with my btc-qt client? Fee isn't right (Read 557 times)

legendary
Activity: 2954
Merit: 4158
WARNING: doing this is likely to result in a fee that is going to end up being very "low" compared to recommended fees. For example, for your transaction 26433 / 258 bytes = 102 sats/byte Undecided

Thanks.

So, for the bytes, what would be best minimum for a transaction to go through? Example: Above transaction.
For the fees, a transaction should have 360 satoshi/BYTE (0.00000360) for it to be confirmed ASAP. If you want to cheat abit, you can go down to about 330satoshi/byte(0.00000330) and it should still go through fine, albeit with a longer waiting time. *If you want the above settings, you have to put 0.0036BTC/kb or 0.0033BTC/kb.

As always, I recommend using the dynamic fee slider. It does everything for you and you don't have to input the fees manually.
HCP
legendary
Activity: 2086
Merit: 4314
Firstly, try here: http://www.mocacinno.com/page/feeestimate

You can also get recommendations here: https://bitcoinfees.21.co/
and here: https://btc.com/stats/unconfirmed-tx

350 * 258 = 90,300 sats... or 0.00090300 btc

It all comes down to how long you want to wait for confirmation... At this moment in time, a fee of 400+ is a good chance for confirmation within an hour. A fee of 300+ sats/byte is good chance to get confirmed within a day (if not a few hours) whereas a fee of 102 sats/byte "may" get confirmed in a week or 2... or never.

You can always roll the dice and try and send with low fee and use the ViaBTC TX accelerator, but that is very busy these days. Tongue
hero member
Activity: 563
Merit: 500
WARNING: doing this is likely to result in a fee that is going to end up being very "low" compared to recommended fees. For example, for your transaction 26433 / 258 bytes = 102 sats/byte Undecided

Thanks.

So, for the bytes, what would be best minimum for a transaction to go through? Example: Above transaction.
HCP
legendary
Activity: 2086
Merit: 4314
What exactly are you trying to achieve? Are you trying to send a "fixed" amount with a "fixed" fee? Huh

Anyway, you have specified 0.00026433 BTC per kb... your transaction is 0.258 kb as noted in the confirmation dialog.

0.00026433 BTC/kb * 0.258 kb = 0.00006819 BTC which is exactly what the app said it was going to add.

Not quite sure where you got "0.00001759302 BTC" from? I don't see that value shown anywhere in your post? Huh

Looking at your screenshot, it seems you have a total balance of 0.00128033 and you're trying to send out 0.00101600 and use the remainder (0.00026433 as the fee). Your best option is to go into "Settings" -> "Options" -> "Wallet" and then make sure that "Enable coin control features" is checked. (You may need to restart the app)



Once that is switched on, when you go to send... click the "inputs" button...




then select all the inputs... and click OK. Then you should find that the "total at least" option becomes available which will let you specify a "fixed" fee.




WARNING: doing this is likely to result in a fee that is going to end up being very "low" compared to recommended fees. For example, for your transaction 26433 / 258 bytes = 102 sats/byte Undecided
legendary
Activity: 4326
Merit: 3041
Vile Vixen and Miss Bitcointalk 2021-2023
The fee you entered is per kilobyte (and it clearly says so), and the option to enter an absolute fee is only available when using coin control, since it's otherwise impossible to know what fee is appropriate. It's not entirely clear to me what else you're expecting.
hero member
Activity: 563
Merit: 500
I think what is going on. The fee is suppose to be 0.00102453 BTC In order to get that screen window to show a fee of 0.00026433 BTC per kb?

Or am I wrong?
hero member
Activity: 563
Merit: 500
Fucking bitcoin clients wants to send out a fee of 0.00001759302 BTC and not what I fucking inputted which is 0.00026433 BTC
hero member
Activity: 563
Merit: 500
Total: 0.00128033 BTC
Sending amount: 0.00101600 BTC
Fee:0.00026433 BTC

Bitcoin client is alternating the fee and alternating the sending amount.

Please help.
Jump to: