I'm not sure exactly what the problem is. If you want to not ensure the minimum fee then have a look at Context.ensureMinRequiredFee (or SendRequest.ensureMinRequiredFee for one-time use).
On 05/07/2016 04:10 PM, Anton wrote: > Thanks! I'm testing it now and everything seems to work great but what's > the new correct way to handle fees? > What I mean is my wallet offers a "base fee" of 10000 sat/kb and a > "priority fee" which is dynamic but is usually about 20000 sat/kb at > this time. When calculated for a typical tx of ~250 bytes "base fee" and > often even "priority fee" fall below min of 5000 sat/tx which is not > very competitive. I suppose I should do something about it but not sure > just bumping rate by, say, a factor of 4 is the best idea. > > -- > 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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout. -- 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.
