0ff8d82193
We now have constructors that take an arbitrary size fee rate (`Amount`). The `from_sat_per_foo` constructors can be made infallible by taking a `u32` instead of `u64`. This makes the API more ergonomic but limits the fee rate to just under 42 BTC which is plenty. Note we just delete the `from_sat_per_vb_u32` function because it is unreleased, in the past we had `from_sat_per_vb_unchecked` so we could put that back in if we wanted to be a bit more kind to downstream. Can be done later, we likely want to go over the public API before release and add a few things back in that we forgot to deprecate or could not for some reason during dev. Fuzz with a new function that consumes a `u32`. |
||
|---|---|---|
| .. | ||
| deser_net_msg.rs | ||
| deserialize_address.rs | ||
| deserialize_block.rs | ||
| deserialize_prefilled_transaction.rs | ||
| deserialize_psbt.rs | ||
| deserialize_script.rs | ||
| deserialize_transaction.rs | ||
| deserialize_witness.rs | ||
| outpoint_string.rs | ||
| p2p_address_roundtrip.rs | ||
| script_bytes_to_asm_fmt.rs | ||