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

sweep: group pinnable and non-pinnable inputs separately #9427

Open
morehouse opened this issue Jan 17, 2025 · 0 comments
Open

sweep: group pinnable and non-pinnable inputs separately #9427

morehouse opened this issue Jan 17, 2025 · 0 comments
Assignees
Labels
enhancement Improvements to existing features / behaviour security General label for issues/PRs related to the security of the software utxo sweeping
Milestone

Comments

@morehouse
Copy link
Collaborator

The sweeper currently has no concept of pinnable and unpinnable inputs, so HTLC-Timeout (pinnable) and HTLC-Success (not pinnable) inputs can be aggregated into the same transaction if they have the same deadline. As a result, the HTLC-Success inputs effectively become pinnable too.

Another example of this is expired anchors (pinnable) being aggregated with HTLC-Success (not pinnable), though this could also be solved by removing expired anchor sweeping.

I think @yyforyongyu's proposed "sweeper groups" would be all we need to properly implement this.

@morehouse morehouse added enhancement Improvements to existing features / behaviour security General label for issues/PRs related to the security of the software utxo sweeping labels Jan 17, 2025
@yyforyongyu yyforyongyu added this to the v0.19.0 milestone Jan 18, 2025
@yyforyongyu yyforyongyu self-assigned this Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvements to existing features / behaviour security General label for issues/PRs related to the security of the software utxo sweeping
Projects
None yet
Development

No branches or pull requests

2 participants