Skip to content

Check if a batch is expected for commitment_signed #3852

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jkczyz
Copy link
Contributor

@jkczyz jkczyz commented Jun 12, 2025

When receiving a commitment_signed message, if there are any pending splices then we are expected to receive the message as a part of a batch. Otherwise, the spec dictates that we should send an error and fail the channel.

@ldk-reviews-bot
Copy link

ldk-reviews-bot commented Jun 12, 2025

👋 Thanks for assigning @wpaulino 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.

@jkczyz
Copy link
Contributor Author

jkczyz commented Jun 12, 2025

This was caught by @wpaulino post-merge of #3793.

@jkczyz jkczyz requested a review from wpaulino June 12, 2025 17:01
@ldk-reviews-bot
Copy link

👋 The first review has been submitted!

Do you think this PR is ready for a second reviewer? If so, click here to assign a second reviewer.

jkczyz added 2 commits June 13, 2025 11:39
When receiving a commitment_signed message, if there are any pending
splices then we are expected to receive the message as a part of a
batch. Otherwise, the spec dictates that we should send an error and
fail the channel.
@jkczyz jkczyz force-pushed the 2025-06-start-batch-fix branch from 93e32d0 to d016801 Compare June 13, 2025 16:47
@jkczyz
Copy link
Contributor Author

jkczyz commented Jun 13, 2025

Rebased and added a commit removing #[rustfmt::skip] here and related code, where there isn't much changing / shouldn't be very controversial.

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

Successfully merging this pull request may close these issues.

3 participants