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

bookkeeper, meet splicing #7533

Merged

Conversation

niftynei
Copy link
Contributor

@niftynei niftynei commented Aug 6, 2024

update the coin-movment notifications and the bookkeeper respectively so that splices are properly accounted for (quite literally).

Prior to this we haven't been logging the spend of the funding output for splices (they're simply not recorded).

Will update with a PR built on #6980 which includes tests for these.

@niftynei niftynei added this to the v24.08 milestone Aug 6, 2024
@niftynei niftynei force-pushed the nifty/bkpr_splice_one branch 2 times, most recently from f4c7ffd to a6c5443 Compare August 6, 2024 06:55
@niftynei niftynei requested a review from cdecker as a code owner August 6, 2024 06:55
@niftynei niftynei force-pushed the nifty/bkpr_splice_one branch from a6c5443 to 3ccfb9c Compare August 6, 2024 06:56
Copy link
Collaborator

@ddustin ddustin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK

struct amount_msat orig_our_msats,
struct amount_sat orig_funding_sats,
struct bitcoin_outpoint *funding,
u32 blockheight, struct bitcoin_txid *txid, const struct channel_inflight *inflight)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: newlines

@niftynei niftynei force-pushed the nifty/bkpr_splice_one branch 2 times, most recently from ba32cf8 to 61996dd Compare August 7, 2024 00:07
We weren't properly notifying that a channel output has been spent in
the case of it being spent in a splice. This fixes the notification side
of the equation, however there's still some issues remaining for the
bookkeeper side (to come).

Changelog-Fixed: We now send a `coin_movement` notification for splice confirmations of channel funding outpoint spends.
We do some fancy accounting for channel closures; since we're tagging
splice txs as closes we need to mark them as splices so we can treat them
as any other 'normal' on chain event.
@niftynei niftynei force-pushed the nifty/bkpr_splice_one branch from 61996dd to 69bd5a9 Compare August 8, 2024 16:52
@ShahanaFarooqui ShahanaFarooqui merged commit 46dcc6e into ElementsProject:master Aug 8, 2024
37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants