New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
expose feerate_per_kw
in ChannelDetails
#2094
Conversation
f5f774c
to
63d3be8
Compare
Codecov ReportPatch coverage:
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## main #2094 +/- ##
==========================================
+ Coverage 91.14% 91.25% +0.11%
==========================================
Files 101 101
Lines 48887 51613 +2726
Branches 48887 51613 +2726
==========================================
+ Hits 44557 47101 +2544
- Misses 4330 4512 +182
... and 9 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Would suggest to give the full unit in the field name, see below.
lightning/src/ln/channelmanager.rs
Outdated
@@ -1118,6 +1118,10 @@ pub struct ChannelDetails { | |||
/// inbound. This may be zero for inbound channels serialized with LDK versions prior to | |||
/// 0.0.113. | |||
pub user_channel_id: u128, | |||
/// The currently negotiated feerate per 1000-weight-unit applied to commitment and htlc txs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/// The currently negotiated feerate per 1000-weight-unit applied to commitment and htlc txs | |
/// The currently negotiated fee rate denominated in satoshi per 1000 weight units, which is applied to commitment and HTLC transactions. |
lightning/src/ln/channelmanager.rs
Outdated
/// The currently negotiated feerate per 1000-weight-unit applied to commitment and htlc txs | ||
/// | ||
/// This value will be `None` for objects serialized with LDK versions prior to 0.0.115. | ||
pub feerate_per_kw: Option<u32>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To avoid any uncertainty and to align this a bit more with the FeeEstimator
interface, could we name this feerate_sat_per_kw
or feerate_sat_per_1000_weight
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I prefer the latter. I find kw
a little confusing if it's been a while since I've looked at fee rate units.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, did just notice that feerate_per_kw
is used for HolderSignedTx, CommitmentTransaction, and in a few other function calls. It's not really related to this change but perhaps a global replacement makes sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mh, I'm not sure if this warrants a lot of git noise, so we may just want to change it here and in related parts of the public API to feerate_sat_per_kw
or similar.
lightning/src/ln/channelmanager.rs
Outdated
@@ -1260,6 +1264,7 @@ impl ChannelDetails { | |||
outbound_scid_alias: if channel.is_usable() { Some(channel.outbound_scid_alias()) } else { None }, | |||
inbound_scid_alias: channel.latest_inbound_scid_alias(), | |||
channel_value_satoshis: channel.get_value_satoshis(), | |||
feerate_per_kw: Some(channel.get_feerate()), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it would be to include a tiny refactor while you're here and rename Channel::get_feerate
to get_feerate_sat_per_kw
?
63d3be8
to
e26dc51
Compare
@@ -2208,6 +2208,7 @@ mod tests { | |||
inbound_htlc_minimum_msat: None, | |||
inbound_htlc_maximum_msat: None, | |||
config: None, | |||
feerate_sat_per_1000_weight: None |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Maybe very nit picky, but should it not be "sats"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so, as it's FeeEstimator::get_est_sat_per_1000_weight
already and the unit symbol is sat
(cf. https://bitcoin.design/guide/designing-products/units-and-symbols/).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right for unit symbol makes sense, also didn't remember existing usage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@johncantrell97 On that note, as you're already touching ChannelManager
, you could also rename the target_feerate_sats_per_1000_weight
argument of ChannelManager::close_channel_with_target_feerate
to target_feerate_sat_per_1000_weight
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused, it's plural, the design guide linked says explicitly plural is "sats"? Not like it matters tho.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh my, you're actually right. I read the guide and seem to have switched it around in my head. I still think units should be singular (you wouldn't use "USDs" or "BTCs"), but will now shut up and eat my words on the basis of the guide I linked to myself. 🤦♂️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i have no hard opinion on this to be honest ¯_(ツ)_/¯
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer sats
but am now seeing that it's indeed already mixed usage in the code base so maybe it's a future cleanup that is needed?
The field name just needs an update
|
renames Channel::get_feerate to get_feerate_sat_per_1000_weight
e26dc51
to
d76b43f
Compare
Wanted to be able to monitor this for channels with disconnected peers. Closes #2093