Closed casey closed 7 months ago
See also #320 which suggests a type-level fix.
I think the type level fix is way better, although this could be merged in the mean time. Although it's only really useful if it makes it into a release sooner than the type level fix.
I'm going to merge this, its docs only and documents a know problem. FTR after recently being made a maintainer here in this crate I am going to attempt to put some work into the crate and get a bunch of things into a new release soon-ish. Merging this PR will be a test run of my permissions to do so.
BOOM!
Nice!
I think this is potentially a bit of a footgun and deserves some clarification.
fundrawtransaction
has two different ways to specify fee rate,fee_rate
, andfeeRate
. From the docs:This is extra confusing because the field in FundRawTransactionOptions is called
fee_rate
, but is serde renamed to camelCase, so becomesfeeRate
.This PR adds a comment to
FundRawTransactionOptions::fee_rate
clarifying that it's in kvB and not vB, and corresponds to thefeeRate
argument tofundrawtransaction
.I actually think it would it would probably be best if the rust field were renamed to
fee_rate_per_kvb
, and manually renamed tofeeRate
when serializing, but this is good quick fix.