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

[feature]: sweep: batch inputs with similar deadlines #8818

Open
morehouse opened this issue Jun 7, 2024 · 1 comment
Open

[feature]: sweep: batch inputs with similar deadlines #8818

morehouse opened this issue Jun 7, 2024 · 1 comment
Labels
enhancement Improvements to existing features / behaviour fees Related to the fees paid for transactions (both LN and funding/commitment transactions) utxo sweeping

Comments

@morehouse
Copy link
Collaborator

Currently the sweeper will only batch inputs that have the exact same deadline. This is reasonable for shorter deadlines, where a single block difference in deadline calls for significantly different fees.

But for no-deadline sweeps, an artificial deadline of 1008 blocks is used, which causes later no-deadline sweeps to have a different deadline and be batched separately. As discussed in #8751 (comment), we could save on fees if all no-deadline sweeps could be batched together.

@morehouse morehouse added enhancement Improvements to existing features / behaviour fees Related to the fees paid for transactions (both LN and funding/commitment transactions) utxo sweeping labels Jun 7, 2024
@warioishere
Copy link

warioishere commented Jun 9, 2024

I would also appreciate that, Why sweeper batch window duration can be kept example just for non time sensitive sweeps? I loved this option to use for non time sensitive sweeps.

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 fees Related to the fees paid for transactions (both LN and funding/commitment transactions) utxo sweeping
Projects
None yet
Development

No branches or pull requests

2 participants