Open robby-d opened 10 years ago
Another bug I'am not able to reproduce.. Can you please provide me an example of tx_hash where this bug occurs ?
Still happening.
Still happening, but now with a twist - see https://github.com/CounterpartyXCP/counterparty-lib/issues/935
It seems it calculates the maximum amount too simplistically.
Can we replace Max with a "Set your own Tx Fee amount(which would accept up to 10,000 satoshis) and then calculate Max as
(Balance - CustomTxFee)`?
Or calculate the maximum properly, but that seems harder since the fee info is wrong to begin with. I wonder if this problem may be caused by the fixed tx fee setting that prevents CW to calculate the proper transaction fee.
I was able to send BTC from Joe's wallet: I used debug tools to find the required amount and then set that tx fee in the wallet. This can't work on Counterwallet as the error never appears in debug Console.
bitcore-lib-v0.13.5-patched.min.js:5 Uncaught rmessage: "Fee is too small: expected more than 8000 but got 2000 Use Transaction#uncheckedSerialize if you want to skip security checks. See http://bitcore.io/guide/transaction.html#Serialization for more info."stack: "Fee is too small: expected more than 8000 but got 2000↵
The reason it's not readily reproduceable is that it probably requires a specific set of UTXOs.
e.g. you choose Max, then send the transaction, and you're left with 0.0001 in your account