You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.
So this is going through the transactions with outputs available in the current wallet that have 0 confirmations and checking if the feePerKb of the transaction containing that output is less than the feePerKb suggested by superEconomy rate.
If so, Copay will display "Amount too low to spend" under the assumption that "rather than trying to CPFP the feeRate, we would rather just tell the user it is too dangerous to use this utxo in their sending unless it is confirmed."
Two problems:
This error is inaccurate (It should be "This unconfirmed bitcoin is too dangerous to use yet. So you can not spend it yet. Please wait for confirmation from the Bitcoin network.")
It does not disappear after confirmations are gained. (Cached on the local wallet)
Perhaps this issue is better fixed client side... not sure.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
bitcore-wallet-service/lib/server.js
Line 2962 in d416284
So this is going through the transactions with outputs available in the current wallet that have 0 confirmations and checking if the feePerKb of the transaction containing that output is less than the feePerKb suggested by superEconomy rate.
If so, Copay will display "Amount too low to spend" under the assumption that "rather than trying to CPFP the feeRate, we would rather just tell the user it is too dangerous to use this utxo in their sending unless it is confirmed."
Two problems:
Perhaps this issue is better fixed client side... not sure.
The text was updated successfully, but these errors were encountered: