Skip to content
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

fee api is inconsistent #171

Closed
toddfries opened this issue Apr 11, 2016 · 2 comments
Closed

fee api is inconsistent #171

toddfries opened this issue Apr 11, 2016 · 2 comments
Labels

Comments

@toddfries
Copy link

getwalletfee
5000000
settxfee 2000000
true
getwalletfee
200000000000000
settxfee .02
true
getwalletfee
2000000

@raedah
Copy link
Contributor

raedah commented Apr 11, 2016

I think its also worth a reminder note here that 'help settxfee' describes this as 'the increment used each time more fee is required', as opposed to what most users would assume, that its setting the outgoing tx fee. The description leaves much to be desired, as I don't know under which conditions the increment will occur.

@jrick
Copy link
Member

jrick commented Apr 11, 2016

The required fee is a proportion based on the transaction size. For a 0.01 fee, that's actually 0.01/kB. If you only construct a 500 byte transaction, the required fee only needs to be 0.005. Constructing transactions larger than a kB will mean you must pay more than 0.01 in fees.

This value is also no longer used as an increment (it was in previous versions), so that help should be updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants