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 estimates in coin control often lower than actual fees #344

Open
mdpfeiffer opened this issue Nov 6, 2015 · 9 comments
Open

fee estimates in coin control often lower than actual fees #344

mdpfeiffer opened this issue Nov 6, 2015 · 9 comments
Labels

Comments

@mdpfeiffer
Copy link

In Coin Control, the estimates for transfer fees are frequently lower than the actual transfer fees for transactions involving multiple inputs.

@IngCr3at1on
Copy link
Contributor

Yeah being an "estimate" that doesn't surprise me. The proper fee is still displayed in the fee confirmation dialogue.

@MitchellCash
Copy link
Contributor

As stated it is just an estimate so I'm not too worried about this and the fee confirmation dialogue will give you the correct fee prior to sending.

@IngCr3at1on
Copy link
Contributor

Closing this per reasons mentioned above.

@mdpfeiffer
Copy link
Author

I get that it's an estimate. But it doesn't say that it's an estimate. Would a different label help?

@IngCr3at1on
Copy link
Contributor

@mdpfeiffer approximate fee and estimated fee both seem rather long, thoughts?

@IngCr3at1on IngCr3at1on reopened this Jan 29, 2016
@MitchellCash
Copy link
Contributor

Agreed. Approximate Fee and Estimated Fee I think would look to long in the Coin Control.

I would propose using ~, like:

Fee: ~0.001000 XPY

@AtomSmasher00
Copy link

There is no warning that your transaction will fail to send when the fee is larger than the estimate and you are trying to send the full amount of all inputs.

Could there be an option for the total to be automatically adjusted to account for the increased fee, and ask to confirm? And/or, can it give the exact fee so one can adjust the transaction manually?

@IngCr3at1on
Copy link
Contributor

@broyhill adjusting the transaction creates a loop in the create cycle that I'm not sure I'm comfortable with and the error that you get is clear enough to me that I personally don't think a warning is necessary (others may disagree).

The same problem of looping occurs when trying to calculate the proper fee because it can't be calculated until creating the transaction which would basically mean creating the transaction and throwing it out; it's a waste of resources imho.

I like that idea @MitchellCash

@AtomSmasher00
Copy link

The issue is, what is the exact fee? I don't want a warning, I want it to say "Sorry, the required fee is X." The error is just not clear enough.

I can say I have used the wallet extensively, and sometimes I still have to guess (lowering the total to send), and end up with .001, .002 amounts left in an input. Or, I have to attempt the transaction several times until I get the fee high enough / total low enough.

I suppose one could just set a higher fee and eliminate the guesswork... but it's kind of the principle of it to me.

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