Skip to content
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 Channel ID parametre to ForwardingHistoryRequest #5932

Open
ohenrik opened this issue Nov 4, 2021 · 2 comments · May be fixed by #9356
Open

Add Channel ID parametre to ForwardingHistoryRequest #5932

ohenrik opened this issue Nov 4, 2021 · 2 comments · May be fixed by #9356
Assignees
Labels
beginner Issues suitable for new developers enhancement Improvements to existing features / behaviour feature request Requests for new features good first issue Issues suitable for first time contributors to LND htlcswitch rpc Related to the RPC interface
Milestone

Comments

@ohenrik
Copy link

ohenrik commented Nov 4, 2021

It is currently impossible to request forwarding history for a single channel or a selection of channels.

I suggest adding IncomingChanID and OutgoingChanID (or IncomingChanIDs and OutgoingChanIDs) to ForwardingHistoryRequest.

@Roasbeef Roasbeef added beginner Issues suitable for new developers enhancement Improvements to existing features / behaviour feature request Requests for new features htlcswitch rpc Related to the RPC interface labels Nov 4, 2021
@ohenrik
Copy link
Author

ohenrik commented Nov 4, 2021

I'll try to implement this tomorrow :)

@funyug
Copy link
Contributor

funyug commented Dec 11, 2024

Hi, I would like to work on this.

@saubyk saubyk added this to the 0.20.0 milestone Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
beginner Issues suitable for new developers enhancement Improvements to existing features / behaviour feature request Requests for new features good first issue Issues suitable for first time contributors to LND htlcswitch rpc Related to the RPC interface
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants