Author

Topic: sendfrom and transaction fees (Read 892 times)

member
Activity: 74
Merit: 10
July 27, 2011, 07:18:08 AM
#5
thanks for the heads up.  I was confused why I only sometimes get this fee.
newbie
Activity: 42
Merit: 0
July 26, 2011, 06:29:57 PM
#4
"new" coins are coins are you just got from someone.
the fees are in place so no one can flood the network with penny transactions.


"old" coins are coins that's usually have 10+ Confirmations

newbie
Activity: 56
Merit: 0
July 26, 2011, 06:23:19 PM
#3
How "new" is "new" - or how "old" do they need to be so they're not "new" anymore?
newbie
Activity: 42
Merit: 0
July 26, 2011, 06:15:56 PM
#2
it charges a fee when you are sending "new" coins
TT
member
Activity: 77
Merit: 10
July 18, 2011, 12:28:06 AM
#1
I've noticed that if I've set transaction fees to 0.00 in my preferences and config file, when I try to send
bitcoin via the GUI, it sometimes prompts me if I want to pay a transaction fee of .0005 and sometimes
doesn't prompt me and sends with no transaction fee. I have the following questions:

1) Why does it only prompt me sometimes and on what does this depend?

2) I've noticed that when I make the call to sendfrom via the JSON-RPC API, I don't get prompted. It will just
assume I want to pay the .0005 transaction fee. Is there a way to get notified of this from the API before
committing to sending? Is it capped at .0005? Could it ever be higher than that? Is there a way to override
the GUI preferences and the config file settings and choose a specific transaction fee via the API and have
the call fail with an appropriate error message if the transaction fee is too low?
Jump to: