I am working on a "recipient pays fees" implementation for RSK. I was was comparing wallet.calculateFee() to bitcoind's implementation because it already has the "recipient pays fees" feature. Then, I found this issue. This is not a "problem" for me right now, but I thought it would be a good idea to report it.
Yes, DEFAULT_TRANSACTION_MINFEE is a fee/kb, so we should update that too. On Mon, Feb 27, 2017 at 9:46 PM, Andreas Schildbach <[email protected]> wrote: > Out of curiosity, why this is this suddenly an issue for you? > > Also I wonder is Core's DEFAULT_TRANSACTION_MINFEE a fee per kb, or is > it an absolute value? > > > On 02/28/2017 12:13 AM, Oscar Guindzberg wrote: >> I am revisiting tx fees. >> >> I just read the discussion here: >> https://github.com/bitcoinj/bitcoinj/pull/1096 >> >> It looks bitcoin core kept at 1000 for a while: >> https://github.com/bitcoin/bitcoin/commit/6b0e622c25ddba656149de0f9f8b7f2a0aa0deba#diff-12635a58447c65585f51d32b7e04075bR45 >> >> It looks like we should revert >> REFERENCE_DEFAULT_MIN_TX_FEE to 1000 and MIN_NONDUST_OUTPUT to 546. >> >> >> >> > > > -- > You received this message because you are subscribed to the Google Groups > "bitcoinj" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- Oscar Guindzberg -- You received this message because you are subscribed to the Google Groups "bitcoinj" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
