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.
In addition to tagLowFees which adds a 'lowFees' attribute to transactions,
please add tagFeeDust which will add a 'isFeeDust' attribute to transactions.
tagFeeDust would do the following:
Determine the current fee levels.
Determine the type of wallet (single? x of y?)
Estimate the size of an input for the wallet type (148 bytes for single, 73 * m + 34 * n + 49 for m-of-n)
Multiply superEconomy fee by size estimate of 3.
If the value of the UTXO is less than the value from calculating step 4, show the user in Copay a message that says "This bitcoin is too small for current fee rates. Using it would cost more in fees than not using it at all. Please wait until fees go down to use."
The edge cases that could be problematic (since this is really an attribute to a utxo but we're sticking it on a transaction) is if two outputs of a single transaction are both sent to our wallet. Would such a transaction be treated as two "transactions" in BWS terms?
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.
In addition to tagLowFees which adds a 'lowFees' attribute to transactions,
please add tagFeeDust which will add a 'isFeeDust' attribute to transactions.
tagFeeDust would do the following:
The edge cases that could be problematic (since this is really an attribute to a utxo but we're sticking it on a transaction) is if two outputs of a single transaction are both sent to our wallet. Would such a transaction be treated as two "transactions" in BWS terms?
The text was updated successfully, but these errors were encountered: