Author

Topic: Transaction fee (Read 1576 times)

hero member
Activity: 588
Merit: 500
July 10, 2011, 02:41:08 PM
#4
I've paid 1.5% transaction fee just now instead 0.5% that my wallet was configured. Was sending 0.2 and fee was set for 0.001 but paid 0.003 instead. I have 0.3.24 client.

1. Why my config was ignored?
2. Don't you think that 1.5% is not so competitive?
3. How can I enforce my fees in future?

Change your fee back to the default 0.0005 (or something else). Make sure you are running the current release of Bitcoin. Better yet, set the fee to 0, and then Bitcoin will send your transactions with no fee, and prompt you if you create a transaction that actually needs a fee.

Stop getting tiny mining payouts. These increase the size of your transaction when you spend them, increasing the fees you must pay.
legendary
Activity: 1246
Merit: 1014
Strength in numbers
July 10, 2011, 05:19:14 AM
#3
I've paid 1.5% transaction fee just now instead 0.5% that my wallet was configured. Was sending 0.2 and fee was set for 0.001 but paid 0.003 instead. I have 0.3.24 client.

1. Why my config was ignored?
2. Don't you think that 1.5% is not so competitive?
3. How can I enforce my fees in future?

The software is not configured to pay a % fee. The various versions have diferent minimum fees, some none, some .01, the most recent I believe has .0005. That is less than 1 cent. Pretty competitive imo. Some tx will even be able to avoid the min. Large tx and old coins do not look like spam so the network will forward them even with no fee.
newbie
Activity: 59
Merit: 0
July 10, 2011, 05:11:08 AM
#2
That's because the fee is per kilobyte:
https://en.bitcoin.it/wiki/Transaction_fees
hero member
Activity: 558
Merit: 500
July 10, 2011, 05:01:22 AM
#1
I've paid 1.5% transaction fee just now instead 0.5% that my wallet was configured. Was sending 0.2 and fee was set for 0.001 but paid 0.003 instead. I have 0.3.24 client.

1. Why my config was ignored?
2. Don't you think that 1.5% is not so competitive?
3. How can I enforce my fees in future?
Jump to: