Skip to content

Add APIs to classify channel-related transaction types #3566

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

Open
tnull opened this issue Jan 28, 2025 · 3 comments
Open

Add APIs to classify channel-related transaction types #3566

tnull opened this issue Jan 28, 2025 · 3 comments
Labels

Comments

@tnull
Copy link
Contributor

tnull commented Jan 28, 2025

It would be great if we could add APIs that would allow the user to determine which 'type' of transaction any given transaction would be related to channel operation.

Especially when it comes to splicing it would be helpful if a user could check whether a particular Txid is 'known' to LDK and retrieve whether its a channel funding/channel close/splice in/splice out transaction.

@TheBlueMatt
Copy link
Collaborator

Hmm, I don't really think we can do this generically as a query - LDK doesn't keep around all the information that would be required to do this (and I don't think we want to change that). I'm curious what is missing from the current API to be able to handle this on the client end, though? Presumably the only transactions you care about will come back via SpendableOutput events, which can be tracked on the client end, though we'll have to figure out what this looks like with splicing indeed.

@wpaulino
Copy link
Contributor

wpaulino commented May 1, 2025

I'm not sure we'll be producing SpendableOutput events for splices, they might not even have an output that pays back to the user. We will have two splicing-related events though: one for once it's negotiated and another once it's locked. Those could help the user label transactions in their wallet on their own.

@TheBlueMatt
Copy link
Collaborator

TheBlueMatt commented May 1, 2025

Right, I was thinking we'd have a new event for splicing confirmations which could be used by clients, as you note.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants