-
Notifications
You must be signed in to change notification settings - Fork 35
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
add inbound fees fields to channel event #164
add inbound fees fields to channel event #164
Conversation
c58b42b
to
9d6f4d0
Compare
I was thinking about calling this source_discount rather than inbound_fee to give more clarity towards what it is typically doing, reducing the outbound fee rate based on the source |
I know LND also calls it inbound fees, so it's nice to be consistent with the naming, so other devs directly understand that we're talking about the same thing, instead of having to figure out it source_discount and inbound fees are the same. |
I don't think it would be the same because I'd flip the sign on it, although I have to play with it to know Consistency with naming isn't a goal of the arguments generally |
I'm playing around with this on the other APIs, just a heads up not 100% settled on naming but I can adjust it |
OK what I settled on is:
|
LND already gives the negative values, do you want to make them positive? |
And I tested this and I see that the inbound fees are coming in like numbers, not strings:
|
Yeah I saw that too, I pushed some changes for the existing inbound fees that should show the transform |
ff81ea4
to
d5ecb6c
Compare
@@ -117,16 +119,28 @@ module.exports = update => { | |||
|
|||
const txId = !!transactionId.equals(emptyTxId) ? null : transactionId; | |||
|
|||
const { | |||
disabled, |
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 the other variables need to change
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.
can consolidate around the new format like in getchannel
d5ecb6c
to
01fce0f
Compare
Adds needed fields to be compatible with the new fields added in this PR:
lightningnetwork/lnd#8723
Will change from draft to ready for review whenever the LND PR gets merged