The fee you configure or specify on the command line is the unit used, so for instance probably if you had configured 1.0 instead of 0.0005 the transaction that ended up with 0.001 fee would instead have ended up with 2.0, the transaction that charged you 0.0015 would have cost 3.0 and so on.
Basically, and in theory, if the system determined there are enough penalties (coins only received recently, a send of 0.01 or less, a total transaction size measured in kilobytes...) to add up to three times MIN_TX_FEE, you get charged that many times whatever fee you had set.
Once upon a time someone got really weirded out by having the client say the fee would be 0.02, so they re-configured to make 0.02 the configured setting. The client then said it would be 0.04! So they configured to 0.04. The client duly claimed it would be 0.08! Etc.
-MarkM- (The CENTS thing confuses it further, of course...)
ahh I think I understand! I also found this on the wiki: -paytxfee=<amt> Fee per KB
added to transactions you send
I just removed the paytx parameter and now it is working correctly and it seems that the server always uses the 0.005 fee.
So is it right when I say:
- Without extra fee declaration the client sends ALWAYS the "hard coded" fee of 0.005 (v0.24)?
Because I never saw that the GUI wanted a higher fee than 0.005 (v0.24). But when I follow the transaction fee rules you said it could be that there is a higher fee - or only when paytx parameter is activated? (I wonder that it was only higher when I used the paytx so far) -> this is the only thing that confuses me right now. But god thanks it is working now