Subscribe to specfic event kinds

[benthecarman]

We currently only allow for subscribing to all events. We should also allow to subscribing to smaller subsets like just payments events or just channel events, etc

[JemimahEkong]

Can I work on this? Kindly assign this issue to me.

I recently participated in the Hack4Freedom hackathon and I'm looking to continue building and growing within the Bitcoin open-source ecosystem. I'd love to take on this issue.

My approach would be to first review the current subscription flow and identify how event subscriptions are registered and dispatched. Then I'd extend the subscription mechanism to support filtering by event categories (e.g., payment events, channel events, etc.) while maintaining backward compatibility with the existing "subscribe to all events" behavior. Finally, I'd add the necessary tests and documentation to ensure the new functionality works as expected and is easy for developers to use.

[benthecarman]

Can I work on this? Kindly assign this issue to me.

I recently participated in the Hack4Freedom hackathon and I'm looking to continue building and growing within the Bitcoin open-source ecosystem. I'd love to take on this issue.

My approach would be to first review the current subscription flow and identify how event subscriptions are registered and dispatched. Then I'd extend the subscription mechanism to support filtering by event categories (e.g., payment events, channel events, etc.) while maintaining backward compatibility with the existing "subscribe to all events" behavior. Finally, I'd add the necessary tests and documentation to ensure the new functionality works as expected and is easy for developers to use.

go for it!

[JemimahEkong]

Alright

…

On Thu, Jun 4, 2026 at 7:44 PM benthecarman ***@***.***> wrote: *benthecarman* left a comment (lightningdevkit/ldk-server#225) <#225 (comment)> Can I work on this? Kindly assign this issue to me. I recently participated in the Hack4Freedom hackathon and I'm looking to continue building and growing within the Bitcoin open-source ecosystem. I'd love to take on this issue. My approach would be to first review the current subscription flow and identify how event subscriptions are registered and dispatched. Then I'd extend the subscription mechanism to support filtering by event categories (e.g., payment events, channel events, etc.) while maintaining backward compatibility with the existing "subscribe to all events" behavior. Finally, I'd add the necessary tests and documentation to ensure the new functionality works as expected and is easy for developers to use. go for it! — Reply to this email directly, view it on GitHub <#225?email_source=notifications&email_token=BLUYM7UIA4F3J7ZKHWPANO346G7SVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGUYTCOBXHE22M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4625118795>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BLUYM7VOFUZOAD544TWELT346G7SVAVCNFSM6AAAAACZUWMBQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DMMRVGEYTQNZZGU> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BLUYM7WSYNSOOOLEP45OCYL46G7SVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGUYTCOBXHE22M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/BLUYM7SDIDGWFJPS7UFL7IL46G7SVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRSGUYTCOBXHE22M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you commented.Message ID: ***@***.***>