You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #888 we started exposing TransactionType for funding-related transactions. Here, we continue that work and also classify the remaining transaction types so they are shown in the payment store.
👋 Thanks for assigning @jkczyz as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.
The reason will be displayed to describe this comment to others. Learn more.
Yeah, we need to double-check whether we need to persist this. I think most channel-related transactions will be regenerated/rebroadcast after restart, but not sure if that would be the case for splice-related data?
On-chain payment records don't capture what a transaction was for -- a
channel open, splice, close, sweep, or a plain send. Record that
classification on each on-chain payment, derived from the type LDK
reports when broadcasting the transaction, so it survives restarts
alongside the payment.
The tag keeps only which channels a transaction relates to; amounts and
fees stay on the payment. Existing records keep decoding unchanged.
Compatible with the on-chain transaction classification proposed in lightningdevkit#791.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jkczyz added a commit
to jkczyz/ldk-node
that referenced
this pull request
Jun 26, 2026
On-chain payment records don't capture what a transaction was for -- a
channel open, splice, close, sweep, or a plain send. Record that
classification on each on-chain payment, derived from the type LDK
reports when broadcasting the transaction, so it survives restarts
alongside the payment.
The tag keeps only which channels a transaction relates to; amounts and
fees stay on the payment. Existing records keep decoding unchanged.
Compatible with the on-chain transaction classification proposed in lightningdevkit#791.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jkczyz added a commit
to jkczyz/ldk-node
that referenced
this pull request
Jun 26, 2026
On-chain payment records don't capture what a transaction was for -- a
channel open, splice, close, sweep, or a plain send. Record that
classification on each on-chain payment, derived from the type LDK
reports when broadcasting the transaction, so it survives restarts
alongside the payment.
The tag keeps only which channels a transaction relates to; amounts and
fees stay on the payment. Existing records keep decoding unchanged.
Compatible with the on-chain transaction classification proposed in lightningdevkit#791.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Avoid tagging ordinary wallet sends and rebroadcasts as LDK sweeps.
They should remain on-chain payments with no transaction type.
Co-Authored-By: HAL 9000
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes#447.
In #888 we started exposing
TransactionTypefor funding-related transactions. Here, we continue that work and also classify the remaining transaction types so they are shown in the payment store.