Skip to content

fix: reverse swap double broadcast#486

Merged
michael1011 merged 1 commit into
masterfrom
fix/reverse-swap-double-broadcast
Jun 30, 2025
Merged

fix: reverse swap double broadcast#486
michael1011 merged 1 commit into
masterfrom
fix/reverse-swap-double-broadcast

Conversation

@jackstar12

@jackstar12 jackstar12 commented Jun 30, 2025

Copy link
Copy Markdown
Member

if a swap accepts zero-conf and goes into transaction.confirmed before
the invoice is being settled, the client tries to broadcast again,
leading to an insufficient replacement error

Summary by CodeRabbit

  • Bug Fixes
    • Improved handling of reverse swap status updates to prevent redundant processing when a claim transaction has already been broadcast.

if a swap accepts zero-conf and goes into transaction.confirmed before
the invoice is being settled, the client tries to broadcast again,
leading to an insufficient replacement error
@coderabbitai

coderabbitai Bot commented Jun 30, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

A conditional check was introduced in the handleReverseSwapStatus method to determine if the ClaimTransactionId is already set when the status is boltz.TransactionConfirmed. If it is, the method skips updating the lockup transaction ID and constructing the claim transaction, thus avoiding redundant processing.

Changes

File(s) Change Summary
internal/nursery/reverse.go Added a conditional check in handleReverseSwapStatus to skip claim transaction logic if already set.

Poem

A check in the code, a pause in the flow,
No double claims now, just onward we go!
If the claim is already written,
The swap's next steps are smitten.
With tidy logic, the nursery's bright—
Less work for bunnies, and all feels right! 🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@jackstar12 jackstar12 requested a review from michael1011 June 30, 2025 13:57
@michael1011

Copy link
Copy Markdown
Member

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jun 30, 2025

Copy link
Copy Markdown
Contributor
✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
internal/nursery/reverse.go (1)

163-166: LGTM! Effective fix for double broadcast prevention.

The conditional check correctly prevents redundant claim transaction processing when the transaction has already been broadcast during the TransactionMempool phase. This addresses the "insufficient replacement" error described in the PR objectives.

The logic is sound:

  • Early exit before database operations and transaction construction
  • Proper placement at the beginning of the TransactionConfirmed case
  • Clear comment explaining the rationale

Consider adding a debug log statement to improve troubleshooting:

 // already broadcasted on transaction.mempool
 if reverseSwap.ClaimTransactionId != "" {
+    logger.Debugf("Skipping claim transaction construction for Reverse Swap %s - already broadcast", reverseSwap.Id)
     break
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d4acf18 and 5f66aee.

📒 Files selected for processing (1)
  • internal/nursery/reverse.go (1 hunks)

@michael1011 michael1011 merged commit 4edb60d into master Jun 30, 2025
3 checks passed
@michael1011 michael1011 deleted the fix/reverse-swap-double-broadcast branch June 30, 2025 14:35
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.

2 participants