-
Notifications
You must be signed in to change notification settings - Fork 19
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
[BUG] Bitcoin sending doesn't work #3480
Comments
@AntonioVentilii any feedback regarding this - I think a small fix in the frontend is needed for serialization |
Hi @DeLemonCH , thanks a lot for reporting these issues! The serialization error has been identified and corrected, the fix will be available in the next release (v0.9.4). The other two points have also been noted and will be addressed soon. |
# Motivation The PR fixes one of the issues reported in #3480. Also, I noticed a few more places where the same kinda of error could have appeared.
Thank you! |
Hi @DeLemonCH . We filed the remaining 2 issues, and will add them into one of our next sprints. |
StefanBerger-DFINITY Merci! |
@DeLemonCH will address that asap. @DenysKarmazynDFINITY that should be in your todo list in the next few minutes |
The diff is 0.00002066, which is about the transaction fees of ~2 USD. |
@DeLemonCH sorry to bother again. But we are working on an improved flow that will show the expected fees, and then we will also provide a MAX button. |
Hi Stefan, yes I could send it with considering the fee in the full amount - though would have expected it to be taken from the transfer amount. |
…3755) # Motivation This PR fixes issue described [here](#3480 (comment)) - there was no check in the BTC send flow which makes sure that provided amount and related utxos fee do not exceed available balance. The component now checks `insufficientFundsForFee` case, disabled "send" button if it's true, as well as shows the following user message: <img width="627" alt="error" src="https://github.com/user-attachments/assets/6d7aa80c-261b-4ee7-a4db-31dfbd91d9a6">
Several bugs:
The text was updated successfully, but these errors were encountered: