Skip to content
This repository has been archived by the owner on Sep 8, 2020. It is now read-only.

Incorrect fee calculation for BTG, resulting in failed transaction #81

Open
rkistner opened this issue Jan 7, 2018 · 0 comments
Open

Comments

@rkistner
Copy link

rkistner commented Jan 7, 2018

When trying to send BTG, and selecting the default "High" transaction fees, the fees are still too low.

See example:

image

This results in an error like this, with no explanation:

image

The error in the network response is a 500 with this body:

{"error":"{\"result\":null,\"error\":{\"code\":-26,\"message\":\"66: min relay fee not met\"},\"id\":<filtered>}"}

Luckily this makes sense. So I just used a custom fee of 10 satoshis per byte, and then the transaction worked without issue.

Side note: The error dialog is also a big issue. Not giving any details makes the error quite scary when large amounts of money is involved, and the user doesn't know whether the transaction went through or not. Possibilities going through your head:

  • This is just a temporary error, I should try again.
  • Maybe it did actually work, and trying again will cause me to send double the amount.
  • Trying again gives the same error. Maybe my funds are somehow not accessible?
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant